@integrity-labs/agt-cli 0.28.378 → 0.28.379

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

@@ -34959,6 +34959,17 @@ var FLAG_REGISTRY = [
     // so it is a deliberate, audited per-org flip (ADR-0022 §4).
     sensitive: true
   },
+  {
+    key: "approval-notify-auto-resolve",
+    description: `Approval-notification "Auto" dispatch resolution (ENG-7985). When ON for an org, an approver whose approval_notify_channel is "Auto" (unset) has their approval card resolved to the best LINKED chat surface at dispatch time - Slack DM first, else Telegram DM - instead of silently falling through to the team channel / agent-watched direct-chat thread (where the approver never sees it). Explicit slack/telegram/email/msteams preferences are unchanged, and an explicit-but-unsatisfiable pref is never silently rerouted. Default OFF is behaviour-preserving, so existing orgs' approvers do not suddenly start receiving DMs without opt-in. Evaluated per-org. Ships dark.`,
+    flagType: "boolean",
+    // Safe/default value is `false` (today's resolution: Auto falls to team/direct-chat). A flag-DB
+    // read error degrades to this, so an outage can never flip approval routing for an org.
+    defaultValue: false,
+    // A routing/visibility change (which surface an approval card is DM'd to), not a control that
+    // blocks customer email - so not `sensitive`, unlike the email-guard enable gates above.
+    sensitive: false
+  },
   {
     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.",

package/dist/mcp/origami.js

@@ -40623,6 +40623,17 @@ var FLAG_REGISTRY = [
     // so it is a deliberate, audited per-org flip (ADR-0022 §4).
     sensitive: true
   },
+  {
+    key: "approval-notify-auto-resolve",
+    description: `Approval-notification "Auto" dispatch resolution (ENG-7985). When ON for an org, an approver whose approval_notify_channel is "Auto" (unset) has their approval card resolved to the best LINKED chat surface at dispatch time - Slack DM first, else Telegram DM - instead of silently falling through to the team channel / agent-watched direct-chat thread (where the approver never sees it). Explicit slack/telegram/email/msteams preferences are unchanged, and an explicit-but-unsatisfiable pref is never silently rerouted. Default OFF is behaviour-preserving, so existing orgs' approvers do not suddenly start receiving DMs without opt-in. Evaluated per-org. Ships dark.`,
+    flagType: "boolean",
+    // Safe/default value is `false` (today's resolution: Auto falls to team/direct-chat). A flag-DB
+    // read error degrades to this, so an outage can never flip approval routing for an org.
+    defaultValue: false,
+    // A routing/visibility change (which surface an approval card is DM'd to), not a control that
+    // blocks customer email - so not `sensitive`, unlike the email-guard enable gates above.
+    sensitive: false
+  },
   {
     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.",

package/dist/mcp/slack-channel.js

@@ -34542,6 +34542,17 @@ var FLAG_REGISTRY = [
     // so it is a deliberate, audited per-org flip (ADR-0022 §4).
     sensitive: true
   },
+  {
+    key: "approval-notify-auto-resolve",
+    description: `Approval-notification "Auto" dispatch resolution (ENG-7985). When ON for an org, an approver whose approval_notify_channel is "Auto" (unset) has their approval card resolved to the best LINKED chat surface at dispatch time - Slack DM first, else Telegram DM - instead of silently falling through to the team channel / agent-watched direct-chat thread (where the approver never sees it). Explicit slack/telegram/email/msteams preferences are unchanged, and an explicit-but-unsatisfiable pref is never silently rerouted. Default OFF is behaviour-preserving, so existing orgs' approvers do not suddenly start receiving DMs without opt-in. Evaluated per-org. Ships dark.`,
+    flagType: "boolean",
+    // Safe/default value is `false` (today's resolution: Auto falls to team/direct-chat). A flag-DB
+    // read error degrades to this, so an outage can never flip approval routing for an org.
+    defaultValue: false,
+    // A routing/visibility change (which surface an approval card is DM'd to), not a control that
+    // blocks customer email - so not `sensitive`, unlike the email-guard enable gates above.
+    sensitive: false
+  },
   {
     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.",

package/dist/mcp/telegram-channel.js

@@ -34892,6 +34892,17 @@ var FLAG_REGISTRY = [
     // so it is a deliberate, audited per-org flip (ADR-0022 §4).
     sensitive: true
   },
+  {
+    key: "approval-notify-auto-resolve",
+    description: `Approval-notification "Auto" dispatch resolution (ENG-7985). When ON for an org, an approver whose approval_notify_channel is "Auto" (unset) has their approval card resolved to the best LINKED chat surface at dispatch time - Slack DM first, else Telegram DM - instead of silently falling through to the team channel / agent-watched direct-chat thread (where the approver never sees it). Explicit slack/telegram/email/msteams preferences are unchanged, and an explicit-but-unsatisfiable pref is never silently rerouted. Default OFF is behaviour-preserving, so existing orgs' approvers do not suddenly start receiving DMs without opt-in. Evaluated per-org. Ships dark.`,
+    flagType: "boolean",
+    // Safe/default value is `false` (today's resolution: Auto falls to team/direct-chat). A flag-DB
+    // read error degrades to this, so an outage can never flip approval routing for an org.
+    defaultValue: false,
+    // A routing/visibility change (which surface an approval card is DM'd to), not a control that
+    // blocks customer email - so not `sensitive`, unlike the email-guard enable gates above.
+    sensitive: false
+  },
   {
     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.",

package/dist/{persistent-session-UR2QF76O.js → persistent-session-PGKQK5VU.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-Q64467SG.js";
+} from "./chunk-REVQSDNX.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-UR2QF76O.js.map
+//# sourceMappingURL=persistent-session-PGKQK5VU.js.map

package/dist/{responsiveness-probe-QXVQKH7F.js → responsiveness-probe-T2VF5SVF.js}

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

package/package.json

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