@integrity-labs/agt-cli 0.28.372 → 0.28.373

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

@@ -34653,17 +34653,11 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_DIRECT_CHAT_DOORBELL_ENABLED"
   },
-  {
-    key: "kanban-doorbell",
-    description: 'Durable kanban-check delivery (ENG-6785, ADR-0020 T1): the manager enqueues the kanban "check your board" nudge as a direct_chat_messages notice (ENG-6381 kind) and rings the direct-chat doorbell, instead of firing it over unverified tmux send-keys (which always returned delivered=false post-ENG-6345, so every kanban inject logged "failed" and the board never progressed). Boolean gate; ships dark.',
-    flagType: "boolean",
-    // Declared safe value is `false` — keeps today's send-keys kanban inject. The
-    // durable rail reuses the direct-chat notice queue (the board state is already
-    // durable, so this only needs reliable WAKE delivery); flip on per-host to
-    // canary before fleet rollout.
-    defaultValue: false,
-    envVar: "AGT_KANBAN_DOORBELL_ENABLED"
-  },
+  // ENG-7967: the 'kanban-doorbell' flag was RETIRED. The durable direct-chat
+  // notice rail is now the SOLE kanban-nudge delivery path (the tmux send-keys
+  // fallback was removed with it), so there is nothing left to gate. Archived by
+  // migration 20260722000003 (deletes any feature_flags / feature_flag_overrides
+  // rows for the key). Do not re-add without re-introducing a second delivery path.
   {
     key: "direct-chat-stream-reply",
     description: "Server-side type-out for direct-chat replies (direct-chat UI redesign Phase 2, docs/design/direct-chat-ui-chat-sdk.md): the channel MCP posts a small anchor via /host/direct-chat/reply, then reveals the rest of the (already-complete) reply progressively through /host/direct-chat/update so the webapp bubble grows instead of appearing as a wall of text. Purely cosmetic (the persisted reply is identical either way). Boolean gate; ships dark.",

package/dist/mcp/origami.js

@@ -40317,17 +40317,11 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_DIRECT_CHAT_DOORBELL_ENABLED"
   },
-  {
-    key: "kanban-doorbell",
-    description: 'Durable kanban-check delivery (ENG-6785, ADR-0020 T1): the manager enqueues the kanban "check your board" nudge as a direct_chat_messages notice (ENG-6381 kind) and rings the direct-chat doorbell, instead of firing it over unverified tmux send-keys (which always returned delivered=false post-ENG-6345, so every kanban inject logged "failed" and the board never progressed). Boolean gate; ships dark.',
-    flagType: "boolean",
-    // Declared safe value is `false` — keeps today's send-keys kanban inject. The
-    // durable rail reuses the direct-chat notice queue (the board state is already
-    // durable, so this only needs reliable WAKE delivery); flip on per-host to
-    // canary before fleet rollout.
-    defaultValue: false,
-    envVar: "AGT_KANBAN_DOORBELL_ENABLED"
-  },
+  // ENG-7967: the 'kanban-doorbell' flag was RETIRED. The durable direct-chat
+  // notice rail is now the SOLE kanban-nudge delivery path (the tmux send-keys
+  // fallback was removed with it), so there is nothing left to gate. Archived by
+  // migration 20260722000003 (deletes any feature_flags / feature_flag_overrides
+  // rows for the key). Do not re-add without re-introducing a second delivery path.
   {
     key: "direct-chat-stream-reply",
     description: "Server-side type-out for direct-chat replies (direct-chat UI redesign Phase 2, docs/design/direct-chat-ui-chat-sdk.md): the channel MCP posts a small anchor via /host/direct-chat/reply, then reveals the rest of the (already-complete) reply progressively through /host/direct-chat/update so the webapp bubble grows instead of appearing as a wall of text. Purely cosmetic (the persisted reply is identical either way). Boolean gate; ships dark.",

package/dist/mcp/slack-channel.js

@@ -34236,17 +34236,11 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_DIRECT_CHAT_DOORBELL_ENABLED"
   },
-  {
-    key: "kanban-doorbell",
-    description: 'Durable kanban-check delivery (ENG-6785, ADR-0020 T1): the manager enqueues the kanban "check your board" nudge as a direct_chat_messages notice (ENG-6381 kind) and rings the direct-chat doorbell, instead of firing it over unverified tmux send-keys (which always returned delivered=false post-ENG-6345, so every kanban inject logged "failed" and the board never progressed). Boolean gate; ships dark.',
-    flagType: "boolean",
-    // Declared safe value is `false` — keeps today's send-keys kanban inject. The
-    // durable rail reuses the direct-chat notice queue (the board state is already
-    // durable, so this only needs reliable WAKE delivery); flip on per-host to
-    // canary before fleet rollout.
-    defaultValue: false,
-    envVar: "AGT_KANBAN_DOORBELL_ENABLED"
-  },
+  // ENG-7967: the 'kanban-doorbell' flag was RETIRED. The durable direct-chat
+  // notice rail is now the SOLE kanban-nudge delivery path (the tmux send-keys
+  // fallback was removed with it), so there is nothing left to gate. Archived by
+  // migration 20260722000003 (deletes any feature_flags / feature_flag_overrides
+  // rows for the key). Do not re-add without re-introducing a second delivery path.
   {
     key: "direct-chat-stream-reply",
     description: "Server-side type-out for direct-chat replies (direct-chat UI redesign Phase 2, docs/design/direct-chat-ui-chat-sdk.md): the channel MCP posts a small anchor via /host/direct-chat/reply, then reveals the rest of the (already-complete) reply progressively through /host/direct-chat/update so the webapp bubble grows instead of appearing as a wall of text. Purely cosmetic (the persisted reply is identical either way). Boolean gate; ships dark.",

package/dist/mcp/telegram-channel.js

@@ -34586,17 +34586,11 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_DIRECT_CHAT_DOORBELL_ENABLED"
   },
-  {
-    key: "kanban-doorbell",
-    description: 'Durable kanban-check delivery (ENG-6785, ADR-0020 T1): the manager enqueues the kanban "check your board" nudge as a direct_chat_messages notice (ENG-6381 kind) and rings the direct-chat doorbell, instead of firing it over unverified tmux send-keys (which always returned delivered=false post-ENG-6345, so every kanban inject logged "failed" and the board never progressed). Boolean gate; ships dark.',
-    flagType: "boolean",
-    // Declared safe value is `false` — keeps today's send-keys kanban inject. The
-    // durable rail reuses the direct-chat notice queue (the board state is already
-    // durable, so this only needs reliable WAKE delivery); flip on per-host to
-    // canary before fleet rollout.
-    defaultValue: false,
-    envVar: "AGT_KANBAN_DOORBELL_ENABLED"
-  },
+  // ENG-7967: the 'kanban-doorbell' flag was RETIRED. The durable direct-chat
+  // notice rail is now the SOLE kanban-nudge delivery path (the tmux send-keys
+  // fallback was removed with it), so there is nothing left to gate. Archived by
+  // migration 20260722000003 (deletes any feature_flags / feature_flag_overrides
+  // rows for the key). Do not re-add without re-introducing a second delivery path.
   {
     key: "direct-chat-stream-reply",
     description: "Server-side type-out for direct-chat replies (direct-chat UI redesign Phase 2, docs/design/direct-chat-ui-chat-sdk.md): the channel MCP posts a small anchor via /host/direct-chat/reply, then reveals the rest of the (already-complete) reply progressively through /host/direct-chat/update so the webapp bubble grows instead of appearing as a wall of text. Purely cosmetic (the persisted reply is identical either way). Boolean gate; ships dark.",

package/dist/{persistent-session-HXUYS63V.js → persistent-session-G4GDPZ54.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-NDF3YMP5.js";
+} from "./chunk-TRBANZZ4.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-HXUYS63V.js.map
+//# sourceMappingURL=persistent-session-G4GDPZ54.js.map

package/dist/{responsiveness-probe-TVSASSZY.js → responsiveness-probe-2JNQBULO.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-NDF3YMP5.js";
+} from "./chunk-TRBANZZ4.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -437,4 +437,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-TVSASSZY.js.map
+//# sourceMappingURL=responsiveness-probe-2JNQBULO.js.map

package/package.json

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