@integrity-labs/agt-cli 0.28.569 → 0.28.571

package/dist/{chunk-7O2TXBWR.js → chunk-72K46XUZ.js}

@@ -10619,13 +10619,30 @@ var FLAG_REGISTRY = [
     // safe default — it resolves to `honors`, reporting every host as honouring
     // the flip, including hosts whose agt-cli has no reader at all.
     //
-    // 0.28.566 is the auto-publish cut from the ENG-8575 merge (583cef8d9,
-    // published 2026-08-12T08:32Z). Verified against the published tarball
-    // rather than inferred from the merge: `maybeScanToolCalls`,
-    // `tool-call-audit` and `tool-call-path-salt` are all present in
-    // package/dist/lib/manager-worker.js — the manager, which is the actual
-    // reader. The dist/mcp/* occurrences are bundling artifacts, not readers.
-    since: "0.28.566"
+    // WHAT THIS VERSION HAS TO MEAN. Not "the first build with a reader" — the
+    // first build where flipping the flag does what the flag is documented to
+    // do. Those diverged twice already, in the same direction:
+    //
+    //   0.28.566 (ENG-8575) — the first build with a reader. Pinned here and
+    //     correct on the day. It has the unbounded scan window and the coverage
+    //     rows that overstate (both ENG-8740), and no `logging_mode` enforcement
+    //     at all (ENG-8726) — so a hash-only agent on it emits plaintext
+    //     `argv0` / `url_host` / `mcp_tool`, which is precisely the governance
+    //     breach this epic exists to prevent.
+    //   0.28.569 (ENG-8740) — bounded window, honest coverage intervals. Still
+    //     no hash-only enforcement. The pin was NOT moved at that merge and went
+    //     stale for a day; reach reported those hosts `honors`.
+    //   0.28.570 (ENG-8726) — hash-only honoured at runtime. Current pin.
+    //
+    // MOVE THIS PIN whenever a change alters what arming the flag DOES on a
+    // host, and verify it against the published tarball rather than inferring it
+    // from the merge — `npm pack @integrity-labs/agt-cli@<v>` and grep
+    // package/dist/lib/manager-worker.js (the manager is the actual reader; the
+    // dist/mcp/* occurrences are bundling artifacts). For 0.28.570 the markers
+    // are `readAgentLoggingMode` and `loggingModeWithholdsTargets`. Auto-publish
+    // patch-bumps from whatever is on main, so if another CLI-touching PR lands
+    // first the real cut is higher than this and the pin under-reports.
+    since: "0.28.570"
   },
   {
     key: "conversation-eval-backend",
@@ -10930,9 +10947,9 @@ var FLAG_REGISTRY = [
   },
   {
     key: "notify-dispatch",
-    description: "Membership-based channel-notify dispatch (ENG-7682 / notify Slice 1). off = today's behaviour: a non-@mention top-level channel message is dropped by the mention_only engagement gate (SLACK_CHANNEL_RESPONSE_MODE). membership = the agent's Slack MCP ADMITS non-@mention channel messages in channels its bot is a member of (the Socket Mode websocket already receives them), waking the agent in-thread via the SAME existing wake path used for @mentions/DMs. Only the mention_only engagement gate is relaxed - the echo/dedup, bot_id/self, and peer-classifier safety leaves still apply, so this never opens a bot-to-bot wake loop. The channel server can't evaluate flags, so the manager materializes the resolved value into the AGT_NOTIFY_DISPATCH spawn env (operator/canary override, ADR-0022). filter = like membership (opt-out) but honours a per-channel mute list: a member-channel message wakes the agent UNLESS the user muted that channel via the /notify slash command. The manager materializes the muted set into AGT_NOTIFY_MUTED_CHANNELS from agent_notify_channel_prefs (ENG-7682 Slice 2). Ships dark (default off).",
+    description: `Membership-based channel-notify dispatch (ENG-7682 / notify Slice 1). off = today's behaviour: a non-@mention top-level channel message is dropped by the mention_only engagement gate (SLACK_CHANNEL_RESPONSE_MODE). membership = the agent's Slack MCP ADMITS non-@mention channel messages in channels its bot is a member of (the Socket Mode websocket already receives them), waking the agent in-thread via the SAME existing wake path used for @mentions/DMs. Only the mention_only engagement gate is relaxed - the echo/dedup, bot_id/self, and peer-classifier safety leaves still apply, so this never opens a bot-to-bot wake loop. The channel server can't evaluate flags, so the manager materializes the resolved value into the AGT_NOTIFY_DISPATCH spawn env (operator/canary override, ADR-0022). filter = like membership (opt-out) but honours a per-channel mute list: a member-channel message wakes the agent UNLESS the user muted that channel via the /notify slash command. The manager materializes the muted set into AGT_NOTIFY_MUTED_CHANNELS from agent_notify_channel_prefs (ENG-7682 Slice 2). addressed = like filter (same per-channel mute, checked FIRST so a mute outranks being named), but a member-channel message additionally has to address THIS agent to wake it: a real Slack mention of its bot user id, \`@<code_name>\` typed verbatim, or the code name used as a vocative at the start of the message ("koda:", "hey koda"). @team / @everyone still wake everyone. This is the fix for one named agent waking every agent in a shared channel (ENG-8657); matching is deliberately conservative, so a name mentioned mid-sentence does NOT wake, and an agent whose identity is unknown to the channel server stays asleep rather than waking on everything. Ships dark (default off).`,
     flagType: "enum",
-    allowedValues: ["off", "membership", "filter"],
+    allowedValues: ["off", "membership", "filter", "addressed"],
     // Declared safe value is `off`: the mention_only gate stays in force, byte-
     // identical to today. membership is the deliberate, per-agent flip that
     // widens what wakes the agent.
@@ -15815,4 +15832,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-7O2TXBWR.js.map
+//# sourceMappingURL=chunk-72K46XUZ.js.map