@integrity-labs/agt-cli 0.28.337 → 0.28.339

package/dist/bin/agt.js

@@ -40,7 +40,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-N7XPDFCW.js";
+} from "../chunk-UVMGRGRO.js";
 import {
   AnchorSessionClient,
   CHANNEL_REGISTRY,
@@ -70,7 +70,7 @@ import {
   renderTemplate,
   resolveChannels,
   serializeManifestForSlackCli
-} from "../chunk-J2WYEOBH.js";
+} from "../chunk-J6QDPXGS.js";
 import "../chunk-XWVM4KPK.js";
 
 // src/bin/agt.ts
@@ -4829,7 +4829,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.337" : "dev";
+var cliVersion = true ? "0.28.339" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -6001,7 +6001,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.337" : "dev";
+var cliVersion2 = true ? "0.28.339" : "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-J2WYEOBH.js → chunk-J6QDPXGS.js}

@@ -7791,6 +7791,24 @@ var FLAG_REGISTRY = [
     // change (ADR-0022 sensitive-flag confirm).
     sensitive: true
   },
+  {
+    key: "slack-hot-thread-guard",
+    description: "Server-side hot-thread guard on the slack.reply surface (ENG-7462). Prevents an agent posting a NEW top-level Slack message when it meant to reply inside the thread it is already working in - a prompt/memory rule proved insufficient (the agent had the rule and still slipped). When a reply would otherwise post to channel ROOT (no thread_ts / message_ts / inbound_id, no active kanban card) and the agent has a recent active thread in that channel (its last bot-posted thread, from the persisted trackedThreads cache, within a freshness window), the reply is redirected into that thread. proactive:true no longer implies channel root; posting at root becomes a deliberate action (the to_channel_root flag, or the thread_ts:null sentinel). off = guard never runs, replies with no coords root exactly as today (ships dark). shadow = compute + log the would-redirect but STILL post to root (measure the fire rate before acting). enforce = apply the redirect (a soft-block: redirect + inform, never a hard rejection). Read live from the heartbeat flags-cache (or the env override); enforce is a deliberate per-org flip after a shadow soak.",
+    flagType: "enum",
+    allowedValues: ["off", "shadow", "enforce"],
+    // Ships dark: off preserves today's behaviour exactly (a coordless reply
+    // roots). shadow is a free local log line (no model spend, unlike ghost-reply)
+    // so it is a cheap opt-in soak; enforce changes where a reply lands, so it is
+    // the audited flip.
+    defaultValue: "off",
+    // Enum override AGT_SLACK_HOT_THREAD_GUARD_MODE (off|shadow|enforce),
+    // resolved by resolveSlackHotThreadMode in the channel-server bundle.
+    envVar: "AGT_SLACK_HOT_THREAD_GUARD_MODE",
+    // enforce reroutes a message the agent asked to send to channel root into a
+    // thread - a visible destination change, so flipping toward it is deliberate
+    // (ADR-0022 sensitive-flag confirm).
+    sensitive: true
+  },
   {
     key: "compaction-notice",
     description: 'Compaction courtesy notice (ENG-7339): when a managed Claude Code session compacts its context, the persistent session pauses and stops replying for a stretch, which looks identical to a dead agent from the channel. When ON, the generated PreCompact hook finds the conversation the user is actively on (the last <channel ...> tag in the transcript) and drops a notice into the matching <channel>-notice-outbox; the channel MCP server (alive while the Claude process compacts) posts a short "reorganizing my memory, back shortly" line. The notice path never clears the pending-inbound marker, so the genuine reply the agent still owes after compaction is unaffected. No active channel tag \u21D2 silent (idle agents never broadcast). Boolean gate; ships dark, canary per host before any fleet flip. When OFF the hook writes nothing and the consumer drops any stray notice unsent.',
@@ -8101,6 +8119,18 @@ var FLAG_REGISTRY = [
     // egress + workflow change worth an explicit confirm.
     sensitive: true
   },
+  {
+    key: "email-guard-per-scope-stage",
+    description: "Per-agent / per-team email-domain guardrail rollout stage (ENG-7830 / ADR-0048). When ON for an org, the effective email_guard_stage is resolved most-specific-non-null (agent ?? team ?? org, with time-boxed exemption decay), so one agent can run shadow while the org is enforce (and vice-versa). When OFF (default) the stage is org-grain only (pre-ENG-7830 behaviour) - the per-agent/team email_guard_stage columns are ignored. Gates the resolver seam (getEffectiveEmailGuardStage) and the owner/admin write routes. Evaluated per-org. Ships dark.",
+    flagType: "boolean",
+    // Declared safe value is `false` (org-only stage = today's behaviour). A flag-DB
+    // read error degrades here, so the per-scope columns stay ignored and the org
+    // policy governs - the fail-closed direction for a compliance control.
+    defaultValue: false,
+    // Enabling it lets a lower scope LOOSEN an email compliance control per-agent, so
+    // flipping it on is worth an explicit confirm (ADR-0022 §4).
+    sensitive: true
+  },
   {
     key: "slack-reply-binding",
     description: "Slack reply-target binding (ENG-7396 / WS2, cross-thread reply routing): the model names which inbound it answers (inbound_id) and the server resolves the destination from its own verified record. shadow = classify + count only, routing unchanged; warn = same routing plus a tool-result note so the model self-corrects; enforce = route a bound reply to the registry thread and REJECT a reply whose target matches no inbound this process delivered. The channel server can't evaluate flags, so the manager materializes the resolved value into the AGT_SLACK_REPLY_BINDING spawn env (the operator/canary override, ADR-0022). Ships shadow.",
@@ -10011,6 +10041,7 @@ export {
   normalizeFlagValue,
   coerceEnvValue,
   FLAGS_SCHEMA_VERSION,
+  LATE_BOUND_VARS,
   expandTemplateVars,
   parseEnvIntegrations,
   sessionTranscriptDir,
@@ -10061,4 +10092,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-J2WYEOBH.js.map
+//# sourceMappingURL=chunk-J6QDPXGS.js.map