Struct InjectionResponse 

pub struct InjectionResponse {
    pub success: bool,
    pub request_id: String,
    pub block_id: Option<String>,
    pub error: Option<String>,
    pub timestamp: u64,
    pub effective_tier: Option<String>,
    pub requires_stop: Option<bool>,
    pub channel_verified: Option<bool>,
    pub deferred: Option<bool>,
}

Response from a message injection attempt.

Fields

success: bool

request_id: String

block_id: Option<String>

error: Option<String>

timestamp: u64

effective_tier: Option<String>

Tier the handler actually applied (after keyword/network escalation). Consumed by the sender-echo path so it doesn’t re-derive escalation.

requires_stop: Option<bool>

Whether effective_tier == "sensitive" should actually STOP the receiver (vs. tag-only for a cryptographically verified sender) — see Handler::inject_message_inner’s requires_stop doc comment (SPEC_JEKT_SENSITIVE_TIER_VERIFIED_SENDER_NO_STOP_2026_08_17.md). Meaningless when effective_tier isn’t "sensitive". Threaded through so the sender-echo path (including forwarded cross-instance hops, which only see this struct’s serialized JSON, not the original Handler call) renders the same STOP-or-tag-only marker the receiver got, instead of re-deriving it from a narrower set of fields.

channel_verified: Option<bool>

The InjectionRequest::channel_verified verdict this delivery was judged on, echoed back so a FORWARDING instance can render the same TRUST= on the sender’s echoed marker that the receiver rendered (SPEC_JEKT_CROSS_CHANNEL_TRUST_2026_09_02.md Phase B, codex P2 on #3064). Only the receiving instance ever computes it — the forwarder holds the sender’s HMAC key and so skips cross-channel verification by design (§D2 step 2) — so without this the echo would show the sender-side view next to a receiver-side ESCALATE=. Same thread-it-through reasoning as requires_stop above. None off the channel tier or when nothing could be checked.

deferred: Option<bool>

Some(true): the target’s process is starting up, restarting or stopping, so the message is queued and reaches it once the process is up — accepted, not yet seen. Some(false): written to the agent now (mid-turn included). None where nothing structured was attempted (errors, PTY keystrokes, relay paths). Lets SendMessage tell its caller which happened instead of claiming “injected” for both.

Trait Implementations

impl Clone for InjectionResponse

fn clone(&self) -> InjectionResponse

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for InjectionResponse

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for InjectionResponse

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for InjectionResponse

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.