@integrity-labs/agt-cli 0.28.405 → 0.28.406

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

@@ -35229,6 +35229,17 @@ var FLAG_REGISTRY = [
     // call the flag evaluator) can gate the kanban_move `waiting` option. Also the
     // highest-precedence operator override, per ADR-0022.
     envVar: "AGT_KANBAN_WAITING_ENABLED"
+  },
+  {
+    key: "scheduled-task-nudge-durable",
+    description: 'Deliver the scheduled-task "work this card" nudge over the durable direct-chat notice rail instead of unverified tmux send-keys (ENG-8068, re-landing ENG-7971). When ON, routeScheduledTaskViaKanban enqueues the nudge via POST /host/scheduled-task/notify (kind:notice, push-and-consumed by the in-session MCP with a per-card consume-time revalidation) and closes the card + run on an enqueue failure, retiring the ENG-6351 orphaned-card gap where an unsubmitted keystroke left a scheduled task silently unrun. When OFF (default) the manager keeps the current tmux send-keys delivery, byte-for-byte as today. This is the kill switch: ENG-7971 was reverted once because the durable rail 500d on a session_id bug (fixed in ENG-8061); flip OFF to fall back to send-keys instantly without a code rollback if the durable path misbehaves. Resolved host-side by the manager via hostFlagStore().getBoolean (the manager evaluates the decision itself, so no spawn-env materialization is needed). Ships dark.',
+    flagType: "boolean",
+    // Declared safe value is `false`: the current, reverted-to send-keys delivery. Turning
+    // it ON activates the durable rail per org/host once operators are confident. `false`
+    // is also the fail-safe direction - a flag-DB read error must never silently switch a
+    // fleet onto the rail that broke prod twice. Net-new gate, so registry-only (ADR-0022);
+    // consumed by the manager's own logic, not an in-container MCP, so no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/mcp/origami.js

@@ -40845,6 +40845,17 @@ var FLAG_REGISTRY = [
     // call the flag evaluator) can gate the kanban_move `waiting` option. Also the
     // highest-precedence operator override, per ADR-0022.
     envVar: "AGT_KANBAN_WAITING_ENABLED"
+  },
+  {
+    key: "scheduled-task-nudge-durable",
+    description: 'Deliver the scheduled-task "work this card" nudge over the durable direct-chat notice rail instead of unverified tmux send-keys (ENG-8068, re-landing ENG-7971). When ON, routeScheduledTaskViaKanban enqueues the nudge via POST /host/scheduled-task/notify (kind:notice, push-and-consumed by the in-session MCP with a per-card consume-time revalidation) and closes the card + run on an enqueue failure, retiring the ENG-6351 orphaned-card gap where an unsubmitted keystroke left a scheduled task silently unrun. When OFF (default) the manager keeps the current tmux send-keys delivery, byte-for-byte as today. This is the kill switch: ENG-7971 was reverted once because the durable rail 500d on a session_id bug (fixed in ENG-8061); flip OFF to fall back to send-keys instantly without a code rollback if the durable path misbehaves. Resolved host-side by the manager via hostFlagStore().getBoolean (the manager evaluates the decision itself, so no spawn-env materialization is needed). Ships dark.',
+    flagType: "boolean",
+    // Declared safe value is `false`: the current, reverted-to send-keys delivery. Turning
+    // it ON activates the durable rail per org/host once operators are confident. `false`
+    // is also the fail-safe direction - a flag-DB read error must never silently switch a
+    // fleet onto the rail that broke prod twice. Net-new gate, so registry-only (ADR-0022);
+    // consumed by the manager's own logic, not an in-container MCP, so no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/mcp/slack-channel.js

@@ -34764,6 +34764,17 @@ var FLAG_REGISTRY = [
     // call the flag evaluator) can gate the kanban_move `waiting` option. Also the
     // highest-precedence operator override, per ADR-0022.
     envVar: "AGT_KANBAN_WAITING_ENABLED"
+  },
+  {
+    key: "scheduled-task-nudge-durable",
+    description: 'Deliver the scheduled-task "work this card" nudge over the durable direct-chat notice rail instead of unverified tmux send-keys (ENG-8068, re-landing ENG-7971). When ON, routeScheduledTaskViaKanban enqueues the nudge via POST /host/scheduled-task/notify (kind:notice, push-and-consumed by the in-session MCP with a per-card consume-time revalidation) and closes the card + run on an enqueue failure, retiring the ENG-6351 orphaned-card gap where an unsubmitted keystroke left a scheduled task silently unrun. When OFF (default) the manager keeps the current tmux send-keys delivery, byte-for-byte as today. This is the kill switch: ENG-7971 was reverted once because the durable rail 500d on a session_id bug (fixed in ENG-8061); flip OFF to fall back to send-keys instantly without a code rollback if the durable path misbehaves. Resolved host-side by the manager via hostFlagStore().getBoolean (the manager evaluates the decision itself, so no spawn-env materialization is needed). Ships dark.',
+    flagType: "boolean",
+    // Declared safe value is `false`: the current, reverted-to send-keys delivery. Turning
+    // it ON activates the durable rail per org/host once operators are confident. `false`
+    // is also the fail-safe direction - a flag-DB read error must never silently switch a
+    // fleet onto the rail that broke prod twice. Net-new gate, so registry-only (ADR-0022);
+    // consumed by the manager's own logic, not an in-container MCP, so no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/mcp/telegram-channel.js

@@ -35114,6 +35114,17 @@ var FLAG_REGISTRY = [
     // call the flag evaluator) can gate the kanban_move `waiting` option. Also the
     // highest-precedence operator override, per ADR-0022.
     envVar: "AGT_KANBAN_WAITING_ENABLED"
+  },
+  {
+    key: "scheduled-task-nudge-durable",
+    description: 'Deliver the scheduled-task "work this card" nudge over the durable direct-chat notice rail instead of unverified tmux send-keys (ENG-8068, re-landing ENG-7971). When ON, routeScheduledTaskViaKanban enqueues the nudge via POST /host/scheduled-task/notify (kind:notice, push-and-consumed by the in-session MCP with a per-card consume-time revalidation) and closes the card + run on an enqueue failure, retiring the ENG-6351 orphaned-card gap where an unsubmitted keystroke left a scheduled task silently unrun. When OFF (default) the manager keeps the current tmux send-keys delivery, byte-for-byte as today. This is the kill switch: ENG-7971 was reverted once because the durable rail 500d on a session_id bug (fixed in ENG-8061); flip OFF to fall back to send-keys instantly without a code rollback if the durable path misbehaves. Resolved host-side by the manager via hostFlagStore().getBoolean (the manager evaluates the decision itself, so no spawn-env materialization is needed). Ships dark.',
+    flagType: "boolean",
+    // Declared safe value is `false`: the current, reverted-to send-keys delivery. Turning
+    // it ON activates the durable rail per org/host once operators are confident. `false`
+    // is also the fail-safe direction - a flag-DB read error must never silently switch a
+    // fleet onto the rail that broke prod twice. Net-new gate, so registry-only (ADR-0022);
+    // consumed by the manager's own logic, not an in-container MCP, so no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/{persistent-session-VMKIIW5Y.js → persistent-session-2AC3P5DJ.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-UYBG62IQ.js";
+} from "./chunk-RD7MIR3G.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-VMKIIW5Y.js.map
+//# sourceMappingURL=persistent-session-2AC3P5DJ.js.map

package/dist/{responsiveness-probe-ZNMY5RVO.js → responsiveness-probe-LGJNUSPU.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-UYBG62IQ.js";
+} from "./chunk-RD7MIR3G.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -437,4 +437,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-ZNMY5RVO.js.map
+//# sourceMappingURL=responsiveness-probe-LGJNUSPU.js.map

package/package.json

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