@integrity-labs/agt-cli 0.28.569 → 0.28.570

package/dist/mcp/direct-chat-channel.js

@@ -35393,13 +35393,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",

package/dist/mcp/origami.js

@@ -41284,13 +41284,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",

package/dist/mcp/slack-channel.js

@@ -35729,13 +35729,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",

package/dist/mcp/telegram-channel.js

@@ -35888,13 +35888,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",

package/dist/{persistent-session-WUNZJXCI.js → persistent-session-HY6GUPBQ.js}

@@ -41,7 +41,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-7O2TXBWR.js";
+} from "./chunk-6XCGZUSS.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -87,4 +87,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-WUNZJXCI.js.map
+//# sourceMappingURL=persistent-session-HY6GUPBQ.js.map

package/dist/{responsiveness-probe-V3P5TGBH.js → responsiveness-probe-6EEZKJVV.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-7O2TXBWR.js";
+} from "./chunk-6XCGZUSS.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -689,4 +689,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-V3P5TGBH.js.map
+//# sourceMappingURL=responsiveness-probe-6EEZKJVV.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.569",
+  "version": "0.28.570",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {