@integrity-labs/agt-cli 0.28.829 → 0.28.830

package/dist/bin/agt.js

@@ -40,12 +40,12 @@ import {
   success,
   table,
   warn
-} from "../chunk-E75YCJTE.js";
+} from "../chunk-NGIFEWP4.js";
 import {
   getProjectDir,
   isSessionResumeDisabled,
   readDirectChatSessionState
-} from "../chunk-6HTCP6D5.js";
+} from "../chunk-N4QVPPYS.js";
 import {
   AnchorSessionClient,
   CHANNEL_REGISTRY,
@@ -79,7 +79,7 @@ import {
   serializeManifestForSlackCli,
   sessionFileExists,
   sessionTranscriptDir
-} from "../chunk-GJY3KZG6.js";
+} from "../chunk-4ZPOP7EW.js";
 import "../chunk-XWVM4KPK.js";
 
 // src/bin/agt.ts
@@ -5467,7 +5467,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync11, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.28.829" : "dev";
+var cliVersion = true ? "0.28.830" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -6658,7 +6658,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.829" : "dev";
+var cliVersion2 = true ? "0.28.830" : "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-GJY3KZG6.js → chunk-4ZPOP7EW.js}

@@ -5453,7 +5453,7 @@ var FLAG_REGISTRY = [
   },
   {
     key: "auto-resume-enabled",
-    description: "DO NOT ARM YET (ENG-8395): this flag has no `since` set until a follow-up bisects it from the published agt-cli dist, and an unset `since` makes the flip-reach estimate report FULL reach for a reader that is host-side \u2014 it will tell you a flip reached hosts that have no code to honour it. Arm only once that follow-up has landed. Bounded BLIND auto-resume for circuit-breaker pauses (ENG-6088): at most one unattended resume per trip cycle, fired once the trip driver has been quiet for the configured window and only for provisioning-reload trips (the ENG-7577 class gate \u2014 a crash-class trip still needs an operator). Superseded wherever `resume-reconciler` is on: that path proves the dependency recovered instead of assuming it, and the blind timer is its flag-off fallback. Boolean gate; ships dark. ENG-8395 promoted this from a raw host env var because AGT_AUTO_RESUME_ENABLED lives in the host env file, so its grain is per-HOST \u2014 one flip arms every agent that host runs (agt-aws-1 carries 14), which made the canary-then-fleet rollout its own documentation prescribes impossible. As a registry flag it resolves per org/team/host/AGENT, so one agent can genuinely be cut over first. Read host-side by the manager (agt-cli), not centrally.",
+    description: "Bounded BLIND auto-resume for circuit-breaker pauses (ENG-6088): at most one unattended resume per trip cycle, fired once the trip driver has been quiet for the configured window and only for provisioning-reload trips (the ENG-7577 class gate \u2014 a crash-class trip still needs an operator). Superseded wherever `resume-reconciler` is on: that path proves the dependency recovered instead of assuming it, and the blind timer is its flag-off fallback. Boolean gate; ships dark. ENG-8395 promoted this from a raw host env var because AGT_AUTO_RESUME_ENABLED lives in the host env file, so its grain is per-HOST \u2014 one flip arms every agent that host runs (agt-aws-1 carries 14), which made the canary-then-fleet rollout its own documentation prescribes impossible. As a registry flag it resolves per org/team/host/AGENT, so one agent can genuinely be cut over first. Read host-side by the manager (agt-cli), not centrally.",
     flagType: "boolean",
     // Declared safe value is `false` — identical to today's behaviour on a host
     // that has never set the env var. Fail-safe direction on a flag-DB read
@@ -5470,16 +5470,41 @@ var FLAG_REGISTRY = [
     // An unattended resume is a real availability change — the agent starts
     // spawning sessions again with no human in the loop — so arming it is a
     // deliberate, confirmed write (ADR-0022 sensitive-flag confirm).
-    sensitive: true
-    // ENG-8395 AC5: `since` is deliberately UNSET at merge. It must be bisected
-    // from the PUBLISHED agt-cli dist once the artifact carrying the host-side
-    // reader exists, never guessed — auto-resume.ts is host-side, so an
-    // under-`since` host has no consumer for this flag and a guessed value makes
-    // the flip-reach modal promise reach it does not have (the defect caught on
-    // ENG-8344 / PR #4014). Precedent for the bisect method: slack-hot-thread-guard
-    // = 0.28.339, slack-scheduled-channel-guard = 0.28.421. Setting it later is
-    // safe: `since` is excluded from projectDefinition, so it does not roll
+    sensitive: true,
+    // ENG-10034: bisected from the PUBLISHED agt-cli dists, not from git history —
+    // auto-resume.ts is host-side, so what matters is the first ARTIFACT a host
+    // could be running that contains a consumer for this flag.
+    //
+    // METHOD, so it can be re-run rather than trusted: download each candidate
+    // tarball from the npm registry and grep its contents for the flag-specific
+    // wiring. Binary search over the 22 versions published either side of
+    // ENG-8395's merge gave a clean one-release boundary, eight minutes wide:
+    //
+    //   0.28.506  2026-08-03T22:29:22Z  readAutoResumeEnvOverride ✗  AUTO_RESUME_FLAG_KEY ✗  'auto-resume-enabled' ✗
+    //   0.28.507  2026-08-03T22:37:00Z  readAutoResumeEnvOverride ✓  AUTO_RESUME_FLAG_KEY ✓  'auto-resume-enabled' ✓
+    //
+    // All three symbols are checked rather than one. `getBooleanForAgent` alone
+    // would have been the wrong probe — it is present in BOTH builds, because the
+    // generic resolver long predates this flag. A `since` bisected on a symbol the
+    // flag does not depend on is a number that looks rigorous and is not.
+    //
+    // ENG-8395 AC5 left this unset on purpose and said why: an unset `since` makes
+    // the flip-reach estimate report FULL reach for a host-side reader, promising
+    // reach it does not have (the defect caught on ENG-8344 / PR #4014). The
+    // follow-up it was waiting on was never filed, so the flag sat un-armable for
+    // a month and ENG-6088's bounded auto-resume stayed dark fleet-wide — a
+    // customer agent sat breaker-paused 2h08m on 2026-09-05 with the recovery path
+    // silently disabled. That is what an administrative blocker recorded only in a
+    // code comment costs.
+    //
+    // Same method as its precedents: slack-hot-thread-guard = 0.28.339,
+    // slack-scheduled-channel-guard = 0.28.421 (ENG-8149). Setting it now is safe:
+    // `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
+    //
+    // This does NOT arm the flag. defaultValue stays false and `sensitive` stays
+    // true; arming is a separate, deliberate decision that belongs to ENG-6066.
+    since: "0.28.507"
   },
   {
     key: "host-poll-rate-alarm",
@@ -13874,4 +13899,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-GJY3KZG6.js.map
+//# sourceMappingURL=chunk-4ZPOP7EW.js.map