@integrity-labs/agt-cli 0.28.407 → 0.28.409

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

@@ -35240,6 +35240,15 @@ var FLAG_REGISTRY = [
     // 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
+  },
+  {
+    key: "scheduled-task-confirmation-card",
+    description: `Post the \u{1F44D}/\u{1F44E} "Task complete?" kanban confirmation card for completed scheduled_task runs (ENG-4576 / ENG-6048). OFF (default) kills these cards fleet-wide: ENG-8072 found they mis-thread onto the run's captured slack_delivery, which in the persistent-session model is frequently a conversational reply rather than the task's own output - so a routine cron's confirmation card lands in an unrelated human thread (e.g. a half-hourly reconciliation card posted into a "you're back online" DM), and a clean cron emits a human \u{1F44D}/\u{1F44E} prompt on every tick regardless. The card was net-negative, so it is disabled by default. Turn it ON per org to restore scheduled-task ratings for a customer who wants them (e.g. a daily digest delivered to a channel). Evaluated per-org in the API (POST /host/runs/finish + the manager rating-prompt route) via getEvaluatedFlags(); the decision is passed into postScheduledTaskKanbanConfirmation. API-only gate - no host env materialization. Ships dark (cards off).`,
+    flagType: "boolean",
+    // Declared safe value is `false`: cards suppressed. `false` is also the fail-closed
+    // direction - a flag-DB read error must not resurrect the mis-threading/noise the kill
+    // fixes. Net-new gate, registry-only (ADR-0022); API-evaluated, no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/mcp/origami.js

@@ -40856,6 +40856,15 @@ var FLAG_REGISTRY = [
     // 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
+  },
+  {
+    key: "scheduled-task-confirmation-card",
+    description: `Post the \u{1F44D}/\u{1F44E} "Task complete?" kanban confirmation card for completed scheduled_task runs (ENG-4576 / ENG-6048). OFF (default) kills these cards fleet-wide: ENG-8072 found they mis-thread onto the run's captured slack_delivery, which in the persistent-session model is frequently a conversational reply rather than the task's own output - so a routine cron's confirmation card lands in an unrelated human thread (e.g. a half-hourly reconciliation card posted into a "you're back online" DM), and a clean cron emits a human \u{1F44D}/\u{1F44E} prompt on every tick regardless. The card was net-negative, so it is disabled by default. Turn it ON per org to restore scheduled-task ratings for a customer who wants them (e.g. a daily digest delivered to a channel). Evaluated per-org in the API (POST /host/runs/finish + the manager rating-prompt route) via getEvaluatedFlags(); the decision is passed into postScheduledTaskKanbanConfirmation. API-only gate - no host env materialization. Ships dark (cards off).`,
+    flagType: "boolean",
+    // Declared safe value is `false`: cards suppressed. `false` is also the fail-closed
+    // direction - a flag-DB read error must not resurrect the mis-threading/noise the kill
+    // fixes. Net-new gate, registry-only (ADR-0022); API-evaluated, no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/mcp/slack-channel.js

@@ -34775,6 +34775,15 @@ var FLAG_REGISTRY = [
     // 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
+  },
+  {
+    key: "scheduled-task-confirmation-card",
+    description: `Post the \u{1F44D}/\u{1F44E} "Task complete?" kanban confirmation card for completed scheduled_task runs (ENG-4576 / ENG-6048). OFF (default) kills these cards fleet-wide: ENG-8072 found they mis-thread onto the run's captured slack_delivery, which in the persistent-session model is frequently a conversational reply rather than the task's own output - so a routine cron's confirmation card lands in an unrelated human thread (e.g. a half-hourly reconciliation card posted into a "you're back online" DM), and a clean cron emits a human \u{1F44D}/\u{1F44E} prompt on every tick regardless. The card was net-negative, so it is disabled by default. Turn it ON per org to restore scheduled-task ratings for a customer who wants them (e.g. a daily digest delivered to a channel). Evaluated per-org in the API (POST /host/runs/finish + the manager rating-prompt route) via getEvaluatedFlags(); the decision is passed into postScheduledTaskKanbanConfirmation. API-only gate - no host env materialization. Ships dark (cards off).`,
+    flagType: "boolean",
+    // Declared safe value is `false`: cards suppressed. `false` is also the fail-closed
+    // direction - a flag-DB read error must not resurrect the mis-threading/noise the kill
+    // fixes. Net-new gate, registry-only (ADR-0022); API-evaluated, no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/mcp/telegram-channel.js

@@ -35125,6 +35125,15 @@ var FLAG_REGISTRY = [
     // 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
+  },
+  {
+    key: "scheduled-task-confirmation-card",
+    description: `Post the \u{1F44D}/\u{1F44E} "Task complete?" kanban confirmation card for completed scheduled_task runs (ENG-4576 / ENG-6048). OFF (default) kills these cards fleet-wide: ENG-8072 found they mis-thread onto the run's captured slack_delivery, which in the persistent-session model is frequently a conversational reply rather than the task's own output - so a routine cron's confirmation card lands in an unrelated human thread (e.g. a half-hourly reconciliation card posted into a "you're back online" DM), and a clean cron emits a human \u{1F44D}/\u{1F44E} prompt on every tick regardless. The card was net-negative, so it is disabled by default. Turn it ON per org to restore scheduled-task ratings for a customer who wants them (e.g. a daily digest delivered to a channel). Evaluated per-org in the API (POST /host/runs/finish + the manager rating-prompt route) via getEvaluatedFlags(); the decision is passed into postScheduledTaskKanbanConfirmation. API-only gate - no host env materialization. Ships dark (cards off).`,
+    flagType: "boolean",
+    // Declared safe value is `false`: cards suppressed. `false` is also the fail-closed
+    // direction - a flag-DB read error must not resurrect the mis-threading/noise the kill
+    // fixes. Net-new gate, registry-only (ADR-0022); API-evaluated, no env materialization.
+    defaultValue: false
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

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

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

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

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

package/package.json

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