@integrity-labs/agt-cli 0.28.568 → 0.28.569

package/dist/bin/agt.js

@@ -40,7 +40,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-VGMO43EI.js";
+} from "../chunk-JBOJC6PG.js";
 import {
   AnchorSessionClient,
   CHANNEL_REGISTRY,
@@ -71,7 +71,7 @@ import {
   requiredMcpWildcard,
   resolveChannels,
   serializeManifestForSlackCli
-} from "../chunk-FSWAPB5J.js";
+} from "../chunk-7O2TXBWR.js";
 import "../chunk-XWVM4KPK.js";
 
 // src/bin/agt.ts
@@ -4834,7 +4834,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync10, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.28.568" : "dev";
+var cliVersion = true ? "0.28.569" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -6009,7 +6009,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.568" : "dev";
+var cliVersion2 = true ? "0.28.569" : "dev";
 var program = new Command();
 program.name("agt").description("Augmented CLI \u2014 agent provisioning and management").version(cliVersion2).option("--json", "Emit machine-readable JSON output (suppress spinners and colors)").option("--skip-update-check", "Skip the automatic update check on startup");
 program.hook("preAction", async (thisCommand, actionCommand) => {

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

@@ -10437,6 +10437,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).`,
@@ -10597,21 +10612,20 @@ 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 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.
+    // 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.
     //
-    // BEFORE THIS FLAG IS FLIPPED ANYWHERE: replace this with the first
-    // published agt-cli version containing `maybeScanToolCalls`.
-    since: "0.29.0"
+    // 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"
   },
   {
     key: "conversation-eval-backend",
@@ -11207,7 +11221,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
@@ -15801,4 +15815,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-FSWAPB5J.js.map
+//# sourceMappingURL=chunk-7O2TXBWR.js.map