{"version":"2.1.234","anchor":"notices-passed-between-sessions-shipped-dark","canonical_anchor":"notices-passed-between-sessions-shipped-dark","heading":"Notices passed between sessions, shipped dark","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/notices-passed-between-sessions-shipped-dark","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Notices passed between sessions, shipped dark\n\nOne session could inject a coordination notice into another, but three separate gates keep it dark.\n\n**What**\n\nA 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.\n\n**Details**\n\n- 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.\n- 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.\n- Redelivery is deduped through a new pending-delivery list in app state, and the ack is only sent once persistence is confirmed.\n- Telemetry `ccr_session_notices` records `not_remote_transport`, `malformed_payload`, `flag_disabled`, `mode_not_auto_will_retry` and `queue_cap_will_retry`.\n\n**Evidence**\n\n`ccr_session_notices`, `[session-notices] session_notice on a non-RemoteIO transport \\u2014 dropping without ack`, `\\u2026[session_notice content truncated by the CLI: `\n\n- Area: Sessions\n- Names: `tengu_polished_lagoon`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}