One session could inject a coordination notice into another, but three separate gates keep it dark.
A session_notice inbound message needs a remote env var, tengu_polished_lagoon, and a helper compiled to return false.
What's wrong with this entry?
A new inbound session_notice message would let one session inject a coordination notice into another as a turn element. Nothing can trigger it in this build: it needs the remote-session environment variable, the tengu_polished_lagoon flag (off unless the server says otherwise), and a helper compiled to always return false.
- Payloads are schema-validated for uuid, notice class and originating session id; oversize content is trimmed down to a byte budget with a visible truncation marker, and hooks get a pass at it.
- It is dropped with a warning on any transport that is not the remote one, and only accepted while permission mode is auto; otherwise it is left for redelivery.
- Redelivery is deduped through a new pending-delivery list in app state, and the ack is only sent once persistence is confirmed.
- Telemetry
ccr_session_noticesrecordsnot_remote_transport,malformed_payload,flag_disabled,mode_not_auto_will_retryandqueue_cap_will_retry.
ccr_session_notices, [session-notices] session_notice on a non-RemoteIO transport \u2014 dropping without ack, \u2026[session_notice content truncated by the CLI:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.