@integrity-labs/agt-cli 0.28.568 → 0.28.570

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

@@ -35211,6 +35211,21 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     public: true
   },
+  {
+    key: "direct-chat-per-user",
+    description: "Scope a STANDARD agent's Direct Chat to the user who had the conversation (ENG-8712). Today two teammates who open the same agent land in the same thread and read each other's messages: the /recent and per-session reads carry no user predicate unless the agent is the per-org system_support concierge. When on, both reads return only sessions the requester authored in PLUS sessions no user has authored in \u2014 the second arm is load-bearing, since every server-originated row (kanban and scheduled-task nudges, integration failures, HITL approvals, degradation alerts) is written as role=user with no user_id and would otherwise vanish from every console (ENG-8431). Does NOT make the thread private in the live direction: assistant replies still fan out on the per-TEAM realtime topic direct-chat-agent:{agentId}, so a teammate holding the drawer open still receives them. Narrowing that topic is follow-up work.",
+    flagType: "boolean",
+    // Declared safe value is `false` — today's team-wide thread. Server-side only
+    // (the two reads in routes/agents.ts); the browser needs no knowledge of it,
+    // so NOT public. No envVar either: this is an org/team-scoped rollout gate
+    // with no host-side consumer, and a declared envVar pinned in sst.config.ts
+    // would make every admin-UI override unreachable (ENG-8303).
+    //
+    // A rollout device, not an undo. Flipping it back off restores the wider read,
+    // but any message written while it was on was still written — and the legacy
+    // backfill in migration 20260812000006 is not reversed by the flag.
+    defaultValue: false
+  },
   {
     key: "onboarding-auto-deploy",
     description: `Auto-deploy the first agent during onboarding (ENG-7378): the agent edit page's Deploy & Test tab fires the existing deploy (draft -> active) automatically once the agent's host is fully deployed (active + manager heartbeating, not provisioning) AND Claude-authenticated (claude_auth_status=valid), replacing the manual "Deploy Agent" click in the recruit funnel. Only draft, non-system_support agents; a failed or timed-out attempt falls back to the manual button (no auto-retry loop).`,
@@ -35371,21 +35386,37 @@ var FLAG_REGISTRY = [
     // by a hand-written process.env gate — so check-new-env-gates.sh stays quiet
     // and the escape hatch still exists for a per-host canary.
     envVar: "AGT_TOOL_CALL_AUDIT_ENABLED",
-    // PLACEHOLDER, deliberately unreachable — see the identical treatment on
-    // `github-broker-credentials` below for the full reasoning. `since` is
-    // advisory: it is read only by computeFlagReach behind GET /admin/reach, so
-    // it changes what an operator is TOLD and does not itself stop a flip.
+    // The real published version, replacing the deliberately-unreachable
+    // placeholder this flag shipped with. `since` is advisory: it is read only
+    // by computeFlagReach behind GET /flags/admin/reach?key=…, so it changes what an
+    // operator is TOLD and does not itself stop a flip. Omitting it is NOT the
+    // safe default — it resolves to `honors`, reporting every host as honouring
+    // the flip, including hosts whose agt-cli has no reader at all.
     //
-    // The host-side reader ships in whichever agt-cli patch the auto-publish
-    // cuts after this merges, and that number cannot be known while writing
-    // this line. Omitting `since` is NOT the safe default here: it resolves to
-    // `honors`, reporting every host as honouring the flip — including hosts
-    // whose agt-cli has no reader at all. An unreachable value reports `stale`
-    // instead: conservative, and visibly wrong rather than invisibly wrong.
+    // 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:
     //
-    // BEFORE THIS FLAG IS FLIPPED ANYWHERE: replace this with the first
-    // published agt-cli version containing `maybeScanToolCalls`.
-    since: "0.29.0"
+    //   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",
@@ -35981,7 +36012,7 @@ var FLAG_REGISTRY = [
     // has no basis for. That is the intended pre-bisect state.
     //
     // BUT `since` IS ADVISORY, NOT A GUARD. It is read in exactly one place -
-    // `computeFlagReach` behind GET /admin/reach, which renders the flip-reach
+    // `computeFlagReach` behind GET /flags/admin/reach?key=…, which renders the flip-reach
     // modal. `evaluate.ts` never reads it and neither does the override write
     // path. The placeholder therefore changes what an operator is TOLD; it does
     // not stop a flip on an under-`since` host. What actually holds the line

package/dist/mcp/origami.js

@@ -41102,6 +41102,21 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     public: true
   },
+  {
+    key: "direct-chat-per-user",
+    description: "Scope a STANDARD agent's Direct Chat to the user who had the conversation (ENG-8712). Today two teammates who open the same agent land in the same thread and read each other's messages: the /recent and per-session reads carry no user predicate unless the agent is the per-org system_support concierge. When on, both reads return only sessions the requester authored in PLUS sessions no user has authored in \u2014 the second arm is load-bearing, since every server-originated row (kanban and scheduled-task nudges, integration failures, HITL approvals, degradation alerts) is written as role=user with no user_id and would otherwise vanish from every console (ENG-8431). Does NOT make the thread private in the live direction: assistant replies still fan out on the per-TEAM realtime topic direct-chat-agent:{agentId}, so a teammate holding the drawer open still receives them. Narrowing that topic is follow-up work.",
+    flagType: "boolean",
+    // Declared safe value is `false` — today's team-wide thread. Server-side only
+    // (the two reads in routes/agents.ts); the browser needs no knowledge of it,
+    // so NOT public. No envVar either: this is an org/team-scoped rollout gate
+    // with no host-side consumer, and a declared envVar pinned in sst.config.ts
+    // would make every admin-UI override unreachable (ENG-8303).
+    //
+    // A rollout device, not an undo. Flipping it back off restores the wider read,
+    // but any message written while it was on was still written — and the legacy
+    // backfill in migration 20260812000006 is not reversed by the flag.
+    defaultValue: false
+  },
   {
     key: "onboarding-auto-deploy",
     description: `Auto-deploy the first agent during onboarding (ENG-7378): the agent edit page's Deploy & Test tab fires the existing deploy (draft -> active) automatically once the agent's host is fully deployed (active + manager heartbeating, not provisioning) AND Claude-authenticated (claude_auth_status=valid), replacing the manual "Deploy Agent" click in the recruit funnel. Only draft, non-system_support agents; a failed or timed-out attempt falls back to the manual button (no auto-retry loop).`,
@@ -41262,21 +41277,37 @@ var FLAG_REGISTRY = [
     // by a hand-written process.env gate — so check-new-env-gates.sh stays quiet
     // and the escape hatch still exists for a per-host canary.
     envVar: "AGT_TOOL_CALL_AUDIT_ENABLED",
-    // PLACEHOLDER, deliberately unreachable — see the identical treatment on
-    // `github-broker-credentials` below for the full reasoning. `since` is
-    // advisory: it is read only by computeFlagReach behind GET /admin/reach, so
-    // it changes what an operator is TOLD and does not itself stop a flip.
+    // The real published version, replacing the deliberately-unreachable
+    // placeholder this flag shipped with. `since` is advisory: it is read only
+    // by computeFlagReach behind GET /flags/admin/reach?key=…, so it changes what an
+    // operator is TOLD and does not itself stop a flip. Omitting it is NOT the
+    // safe default — it resolves to `honors`, reporting every host as honouring
+    // the flip, including hosts whose agt-cli has no reader at all.
     //
-    // The host-side reader ships in whichever agt-cli patch the auto-publish
-    // cuts after this merges, and that number cannot be known while writing
-    // this line. Omitting `since` is NOT the safe default here: it resolves to
-    // `honors`, reporting every host as honouring the flip — including hosts
-    // whose agt-cli has no reader at all. An unreachable value reports `stale`
-    // instead: conservative, and visibly wrong rather than invisibly wrong.
+    // 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:
     //
-    // BEFORE THIS FLAG IS FLIPPED ANYWHERE: replace this with the first
-    // published agt-cli version containing `maybeScanToolCalls`.
-    since: "0.29.0"
+    //   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",
@@ -41872,7 +41903,7 @@ var FLAG_REGISTRY = [
     // has no basis for. That is the intended pre-bisect state.
     //
     // BUT `since` IS ADVISORY, NOT A GUARD. It is read in exactly one place -
-    // `computeFlagReach` behind GET /admin/reach, which renders the flip-reach
+    // `computeFlagReach` behind GET /flags/admin/reach?key=…, which renders the flip-reach
     // modal. `evaluate.ts` never reads it and neither does the override write
     // path. The placeholder therefore changes what an operator is TOLD; it does
     // not stop a flip on an under-`since` host. What actually holds the line

package/dist/mcp/slack-channel.js

@@ -35547,6 +35547,21 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     public: true
   },
+  {
+    key: "direct-chat-per-user",
+    description: "Scope a STANDARD agent's Direct Chat to the user who had the conversation (ENG-8712). Today two teammates who open the same agent land in the same thread and read each other's messages: the /recent and per-session reads carry no user predicate unless the agent is the per-org system_support concierge. When on, both reads return only sessions the requester authored in PLUS sessions no user has authored in \u2014 the second arm is load-bearing, since every server-originated row (kanban and scheduled-task nudges, integration failures, HITL approvals, degradation alerts) is written as role=user with no user_id and would otherwise vanish from every console (ENG-8431). Does NOT make the thread private in the live direction: assistant replies still fan out on the per-TEAM realtime topic direct-chat-agent:{agentId}, so a teammate holding the drawer open still receives them. Narrowing that topic is follow-up work.",
+    flagType: "boolean",
+    // Declared safe value is `false` — today's team-wide thread. Server-side only
+    // (the two reads in routes/agents.ts); the browser needs no knowledge of it,
+    // so NOT public. No envVar either: this is an org/team-scoped rollout gate
+    // with no host-side consumer, and a declared envVar pinned in sst.config.ts
+    // would make every admin-UI override unreachable (ENG-8303).
+    //
+    // A rollout device, not an undo. Flipping it back off restores the wider read,
+    // but any message written while it was on was still written — and the legacy
+    // backfill in migration 20260812000006 is not reversed by the flag.
+    defaultValue: false
+  },
   {
     key: "onboarding-auto-deploy",
     description: `Auto-deploy the first agent during onboarding (ENG-7378): the agent edit page's Deploy & Test tab fires the existing deploy (draft -> active) automatically once the agent's host is fully deployed (active + manager heartbeating, not provisioning) AND Claude-authenticated (claude_auth_status=valid), replacing the manual "Deploy Agent" click in the recruit funnel. Only draft, non-system_support agents; a failed or timed-out attempt falls back to the manual button (no auto-retry loop).`,
@@ -35707,21 +35722,37 @@ var FLAG_REGISTRY = [
     // by a hand-written process.env gate — so check-new-env-gates.sh stays quiet
     // and the escape hatch still exists for a per-host canary.
     envVar: "AGT_TOOL_CALL_AUDIT_ENABLED",
-    // PLACEHOLDER, deliberately unreachable — see the identical treatment on
-    // `github-broker-credentials` below for the full reasoning. `since` is
-    // advisory: it is read only by computeFlagReach behind GET /admin/reach, so
-    // it changes what an operator is TOLD and does not itself stop a flip.
+    // The real published version, replacing the deliberately-unreachable
+    // placeholder this flag shipped with. `since` is advisory: it is read only
+    // by computeFlagReach behind GET /flags/admin/reach?key=…, so it changes what an
+    // operator is TOLD and does not itself stop a flip. Omitting it is NOT the
+    // safe default — it resolves to `honors`, reporting every host as honouring
+    // the flip, including hosts whose agt-cli has no reader at all.
     //
-    // The host-side reader ships in whichever agt-cli patch the auto-publish
-    // cuts after this merges, and that number cannot be known while writing
-    // this line. Omitting `since` is NOT the safe default here: it resolves to
-    // `honors`, reporting every host as honouring the flip — including hosts
-    // whose agt-cli has no reader at all. An unreachable value reports `stale`
-    // instead: conservative, and visibly wrong rather than invisibly wrong.
+    // 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:
     //
-    // BEFORE THIS FLAG IS FLIPPED ANYWHERE: replace this with the first
-    // published agt-cli version containing `maybeScanToolCalls`.
-    since: "0.29.0"
+    //   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",
@@ -36317,7 +36348,7 @@ var FLAG_REGISTRY = [
     // has no basis for. That is the intended pre-bisect state.
     //
     // BUT `since` IS ADVISORY, NOT A GUARD. It is read in exactly one place -
-    // `computeFlagReach` behind GET /admin/reach, which renders the flip-reach
+    // `computeFlagReach` behind GET /flags/admin/reach?key=…, which renders the flip-reach
     // modal. `evaluate.ts` never reads it and neither does the override write
     // path. The placeholder therefore changes what an operator is TOLD; it does
     // not stop a flip on an under-`since` host. What actually holds the line

package/dist/mcp/telegram-channel.js

@@ -35706,6 +35706,21 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     public: true
   },
+  {
+    key: "direct-chat-per-user",
+    description: "Scope a STANDARD agent's Direct Chat to the user who had the conversation (ENG-8712). Today two teammates who open the same agent land in the same thread and read each other's messages: the /recent and per-session reads carry no user predicate unless the agent is the per-org system_support concierge. When on, both reads return only sessions the requester authored in PLUS sessions no user has authored in \u2014 the second arm is load-bearing, since every server-originated row (kanban and scheduled-task nudges, integration failures, HITL approvals, degradation alerts) is written as role=user with no user_id and would otherwise vanish from every console (ENG-8431). Does NOT make the thread private in the live direction: assistant replies still fan out on the per-TEAM realtime topic direct-chat-agent:{agentId}, so a teammate holding the drawer open still receives them. Narrowing that topic is follow-up work.",
+    flagType: "boolean",
+    // Declared safe value is `false` — today's team-wide thread. Server-side only
+    // (the two reads in routes/agents.ts); the browser needs no knowledge of it,
+    // so NOT public. No envVar either: this is an org/team-scoped rollout gate
+    // with no host-side consumer, and a declared envVar pinned in sst.config.ts
+    // would make every admin-UI override unreachable (ENG-8303).
+    //
+    // A rollout device, not an undo. Flipping it back off restores the wider read,
+    // but any message written while it was on was still written — and the legacy
+    // backfill in migration 20260812000006 is not reversed by the flag.
+    defaultValue: false
+  },
   {
     key: "onboarding-auto-deploy",
     description: `Auto-deploy the first agent during onboarding (ENG-7378): the agent edit page's Deploy & Test tab fires the existing deploy (draft -> active) automatically once the agent's host is fully deployed (active + manager heartbeating, not provisioning) AND Claude-authenticated (claude_auth_status=valid), replacing the manual "Deploy Agent" click in the recruit funnel. Only draft, non-system_support agents; a failed or timed-out attempt falls back to the manual button (no auto-retry loop).`,
@@ -35866,21 +35881,37 @@ var FLAG_REGISTRY = [
     // by a hand-written process.env gate — so check-new-env-gates.sh stays quiet
     // and the escape hatch still exists for a per-host canary.
     envVar: "AGT_TOOL_CALL_AUDIT_ENABLED",
-    // PLACEHOLDER, deliberately unreachable — see the identical treatment on
-    // `github-broker-credentials` below for the full reasoning. `since` is
-    // advisory: it is read only by computeFlagReach behind GET /admin/reach, so
-    // it changes what an operator is TOLD and does not itself stop a flip.
+    // The real published version, replacing the deliberately-unreachable
+    // placeholder this flag shipped with. `since` is advisory: it is read only
+    // by computeFlagReach behind GET /flags/admin/reach?key=…, so it changes what an
+    // operator is TOLD and does not itself stop a flip. Omitting it is NOT the
+    // safe default — it resolves to `honors`, reporting every host as honouring
+    // the flip, including hosts whose agt-cli has no reader at all.
     //
-    // The host-side reader ships in whichever agt-cli patch the auto-publish
-    // cuts after this merges, and that number cannot be known while writing
-    // this line. Omitting `since` is NOT the safe default here: it resolves to
-    // `honors`, reporting every host as honouring the flip — including hosts
-    // whose agt-cli has no reader at all. An unreachable value reports `stale`
-    // instead: conservative, and visibly wrong rather than invisibly wrong.
+    // 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:
     //
-    // BEFORE THIS FLAG IS FLIPPED ANYWHERE: replace this with the first
-    // published agt-cli version containing `maybeScanToolCalls`.
-    since: "0.29.0"
+    //   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",
@@ -36476,7 +36507,7 @@ var FLAG_REGISTRY = [
     // has no basis for. That is the intended pre-bisect state.
     //
     // BUT `since` IS ADVISORY, NOT A GUARD. It is read in exactly one place -
-    // `computeFlagReach` behind GET /admin/reach, which renders the flip-reach
+    // `computeFlagReach` behind GET /flags/admin/reach?key=…, which renders the flip-reach
     // modal. `evaluate.ts` never reads it and neither does the override write
     // path. The placeholder therefore changes what an operator is TOLD; it does
     // not stop a flip on an under-`since` host. What actually holds the line

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

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

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

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

package/package.json

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