@integrity-labs/agt-cli 0.28.327 → 0.28.329

package/dist/{chunk-BSTFCC62.js → chunk-J2WYEOBH.js}

@@ -7175,7 +7175,8 @@ var WAITING_KINDS = [
   "pr-merged",
   "human",
   "external",
-  "other"
+  "other",
+  "approval"
 ];
 var WAITING_KIND_SET = new Set(WAITING_KINDS);
 
@@ -7637,6 +7638,16 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_LIVE_STREAM_PRODUCER_ENABLED"
   },
+  {
+    key: "auto-provision-agt-live",
+    description: "Auto-provision the Augmented Live integration (free tier, watermarked) into every NEW organization as an org-scoped install (ENG-7819). Consumed in TWO places: the seed_default_live_integration AFTER INSERT trigger on organizations reads the EXPLICIT feature_flags row (a plpgsql trigger cannot see this compiled default, so dark = no row = trigger no-ops; flipping the flag on this page writes the row the trigger reads - GLOBAL value only, per-org overrides are not consulted by the trigger), and the POST /organizations route evaluates it normally to send the owner provisioning notice. Restricted-posture orgs are skipped; opt-out (remove/block) is permanent - no reconciler. Boolean gate; ships dark. Pre-flip gates: docs/operator/default-integrations-admission.md.",
+    flagType: "boolean",
+    defaultValue: false,
+    // Grants every new open org a public-publishing capability by default;
+    // flipping it on is fleet-shaping and worth an explicit confirm (ADR-0022
+    // §4, same treatment as augmented-support-auto-provision).
+    sensitive: true
+  },
   {
     key: "admin-live-pane",
     description: "Live agent pane streaming on the platform-admin surfaces (ENG-6588): the agent Diagnostics tab and the /admin embed poll GET /admin/agents/:id/pane (tmux capture-pane over SSM) ~every 3s for a bounded window. Boolean gate; ships dark; when OFF the route returns feature_disabled and the UI falls back to the 30s static diagnostics snapshot. It is the no-deploy kill switch bounding the shared-SSM blast radius (SSM SendCommand throttles account-wide, shared with incident-response runbooks).",
@@ -7749,6 +7760,16 @@ var FLAG_REGISTRY = [
     // canary is a high-blast-radius change worth an explicit confirm.
     sensitive: true
   },
+  {
+    key: "direct-chat-recovery",
+    description: "Always-on direct-chat ghost-reply recovery (ENG-7814, ENG-6722 slice E). direct-chat has no recovery-outbox by default: block-turn-end (channel-block-turn-end) only makes the MODEL re-send and is dark/canary, so a direct-chat turn answered as plain text with no direct_chat.reply is lost. When ON, the ghost-reply Stop hook, for an owed and unanswered direct-chat inbound where block-turn-end did not fire, writes the last assistant text to a direct-chat-recovery-outbox that the direct-chat MCP consumes and POSTs to /host/direct-chat/reply for the session, re-sending the reply the agent produced but never delivered. session_id is unambiguous (one session per marker), so there is no cross-thread mis-correlation risk (why direct-chat can safely re-send where Slack needs the ENG-7806 ledger). Confirm-before-clear: the pending marker is cleared only after the POST confirms; a per-marker recovery ledger caps one in-flight recovery per inbound and re-arms on failure. Independent of channel-block-turn-end (either can be on). The env var AGT_DIRECT_CHAT_RECOVERY_ENABLED is the operator/host override the bash hook reads directly (materialized by the manager) and the MCP resolves via the flags cache. Boolean gate; ships dark, flip per host/org to canary before fleet rollout.",
+    flagType: "boolean",
+    defaultValue: false,
+    envVar: "AGT_DIRECT_CHAT_RECOVERY_ENABLED",
+    // Re-sends a reply on the agent behalf (a customer-visible send); flipping it
+    // beyond a canary is a blast-radius change worth an explicit confirm.
+    sensitive: true
+  },
   {
     key: "ghost-reply-intent-classifier",
     description: `Intentional-non-reply suppression on the ghost-reply RECOVERY path (ENG-7096, ENG-7478). The recovery-outbox consumer in the channel MCP only ever fires for turns where the agent ended with text but did NOT call the matching reply tool for that conversation - a set that includes DELIBERATE non-replies and internal third-person self-status narration ("Filed CS-1443... standing by"). A cheap model (the conversation-eval backend, AGT_CONV_EVAL_*) classifies the recovered text as a real message for the user (deliver) or internal not-replying / self-status narration (suppress), keyed on grammatical person, biased to DELIVER and fail-open (a classifier outage degrades to today's behaviour, never a dropped real reply). off = classifier never runs, every recovered reply is posted exactly as today (ships dark, == the old boolean-false). shadow = classify + log the would-suppress verdict for operator adjudication but STILL DELIVER (measure the suppression rate before acting). enforce = actually suppress on a clean high-confidence suppress verdict. The channel server reads this live from the heartbeat flags-cache (or the env override); enforce is a deliberate, audited per-org flip after a shadow soak.`,
@@ -10040,4 +10061,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-BSTFCC62.js.map
+//# sourceMappingURL=chunk-J2WYEOBH.js.map