@integrity-labs/agt-cli 0.28.854 → 0.28.855

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

@@ -36216,6 +36216,35 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_MODEL_API_ERROR_REPORTING_ENABLED"
   },
+  {
+    key: "model-policy-failover-trigger",
+    description: "Automatic model-policy failover (ENG-10156, ADR-0074). off = the trigger does not run. shadow = it evaluates every ingested model-API error against the policy's failover_trigger config and LOGS the decision with its inputs, acting on nothing. Enum gate; ships OFF.",
+    flagType: "enum",
+    // `armed` is DELIBERATELY not an allowed value yet.
+    //
+    // Nothing writes model_policy_failover_state with source='auto' — that is
+    // the actuation half, and it is gated behind a recorded shadow soak
+    // (ENG-10156 AC8). Offering `armed` now would be a setting an operator can
+    // select, that reports success, and that does nothing: the failure mode is
+    // worse than the missing feature, because it looks like a fleet running
+    // with automatic failover enabled. Add it in the same change that makes it
+    // act, not before.
+    allowedValues: ["off", "shadow"],
+    // OFF, not `shadow`, and the contrast with `channel-quarantine-mode` is the
+    // reason: that flag defaults to `shadow` because shadow WAS the live
+    // manager's compiled behaviour, so anything else would have changed the
+    // fleet. Here there is no incumbent behaviour to preserve — nothing has ever
+    // evaluated this — so `off` is the honest default and turning shadow on is a
+    // deliberate act with a soak attached to it.
+    defaultValue: "off",
+    envVar: "AGT_MODEL_POLICY_FAILOVER_TRIGGER_MODE",
+    // Marked sensitive ahead of `armed` existing: the value this flag will
+    // eventually carry moves a host onto a secondary binding whose credential
+    // may be ours (credential_owner: 'platform'), i.e. it spends money with no
+    // human in the loop. Declaring that now costs nothing and means the audited
+    // -flip behaviour is already in place on the day the value is added.
+    sensitive: true
+  },
   {
     key: "claude-md-skills-index",
     description: `Manager injects the "## Available Skills" bullet list (one line per installed skill, name + frontmatter description) into the agent's project CLAUDE.md. Claude Code already surfaces installed skills to the model natively from .claude/skills/*/SKILL.md, so on current models the list is duplicated context - and an expensive one: it measured 12,045 chars across 29 skills on a prod agent, pushing project/CLAUDE.md to 51k against Claude Code's 40,000-char ceiling, past which the tail of the agent's own system prompt is silently truncated. OFF suppresses ONLY the skill bullets; the "Updating Integrations" guidance in the same managed block is real instruction and is always kept. Defaults ON (today's behaviour) - flip OFF per org to reclaim the headroom.`,

package/dist/mcp/index.js

@@ -28486,6 +28486,35 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_MODEL_API_ERROR_REPORTING_ENABLED"
   },
+  {
+    key: "model-policy-failover-trigger",
+    description: "Automatic model-policy failover (ENG-10156, ADR-0074). off = the trigger does not run. shadow = it evaluates every ingested model-API error against the policy's failover_trigger config and LOGS the decision with its inputs, acting on nothing. Enum gate; ships OFF.",
+    flagType: "enum",
+    // `armed` is DELIBERATELY not an allowed value yet.
+    //
+    // Nothing writes model_policy_failover_state with source='auto' — that is
+    // the actuation half, and it is gated behind a recorded shadow soak
+    // (ENG-10156 AC8). Offering `armed` now would be a setting an operator can
+    // select, that reports success, and that does nothing: the failure mode is
+    // worse than the missing feature, because it looks like a fleet running
+    // with automatic failover enabled. Add it in the same change that makes it
+    // act, not before.
+    allowedValues: ["off", "shadow"],
+    // OFF, not `shadow`, and the contrast with `channel-quarantine-mode` is the
+    // reason: that flag defaults to `shadow` because shadow WAS the live
+    // manager's compiled behaviour, so anything else would have changed the
+    // fleet. Here there is no incumbent behaviour to preserve — nothing has ever
+    // evaluated this — so `off` is the honest default and turning shadow on is a
+    // deliberate act with a soak attached to it.
+    defaultValue: "off",
+    envVar: "AGT_MODEL_POLICY_FAILOVER_TRIGGER_MODE",
+    // Marked sensitive ahead of `armed` existing: the value this flag will
+    // eventually carry moves a host onto a secondary binding whose credential
+    // may be ours (credential_owner: 'platform'), i.e. it spends money with no
+    // human in the loop. Declaring that now costs nothing and means the audited
+    // -flip behaviour is already in place on the day the value is added.
+    sensitive: true
+  },
   {
     key: "claude-md-skills-index",
     description: `Manager injects the "## Available Skills" bullet list (one line per installed skill, name + frontmatter description) into the agent's project CLAUDE.md. Claude Code already surfaces installed skills to the model natively from .claude/skills/*/SKILL.md, so on current models the list is duplicated context - and an expensive one: it measured 12,045 chars across 29 skills on a prod agent, pushing project/CLAUDE.md to 51k against Claude Code's 40,000-char ceiling, past which the tail of the agent's own system prompt is silently truncated. OFF suppresses ONLY the skill bullets; the "Updating Integrations" guidance in the same managed block is real instruction and is always kept. Defaults ON (today's behaviour) - flip OFF per org to reclaim the headroom.`,

package/dist/mcp/origami.js

@@ -42439,6 +42439,35 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_MODEL_API_ERROR_REPORTING_ENABLED"
   },
+  {
+    key: "model-policy-failover-trigger",
+    description: "Automatic model-policy failover (ENG-10156, ADR-0074). off = the trigger does not run. shadow = it evaluates every ingested model-API error against the policy's failover_trigger config and LOGS the decision with its inputs, acting on nothing. Enum gate; ships OFF.",
+    flagType: "enum",
+    // `armed` is DELIBERATELY not an allowed value yet.
+    //
+    // Nothing writes model_policy_failover_state with source='auto' — that is
+    // the actuation half, and it is gated behind a recorded shadow soak
+    // (ENG-10156 AC8). Offering `armed` now would be a setting an operator can
+    // select, that reports success, and that does nothing: the failure mode is
+    // worse than the missing feature, because it looks like a fleet running
+    // with automatic failover enabled. Add it in the same change that makes it
+    // act, not before.
+    allowedValues: ["off", "shadow"],
+    // OFF, not `shadow`, and the contrast with `channel-quarantine-mode` is the
+    // reason: that flag defaults to `shadow` because shadow WAS the live
+    // manager's compiled behaviour, so anything else would have changed the
+    // fleet. Here there is no incumbent behaviour to preserve — nothing has ever
+    // evaluated this — so `off` is the honest default and turning shadow on is a
+    // deliberate act with a soak attached to it.
+    defaultValue: "off",
+    envVar: "AGT_MODEL_POLICY_FAILOVER_TRIGGER_MODE",
+    // Marked sensitive ahead of `armed` existing: the value this flag will
+    // eventually carry moves a host onto a secondary binding whose credential
+    // may be ours (credential_owner: 'platform'), i.e. it spends money with no
+    // human in the loop. Declaring that now costs nothing and means the audited
+    // -flip behaviour is already in place on the day the value is added.
+    sensitive: true
+  },
   {
     key: "claude-md-skills-index",
     description: `Manager injects the "## Available Skills" bullet list (one line per installed skill, name + frontmatter description) into the agent's project CLAUDE.md. Claude Code already surfaces installed skills to the model natively from .claude/skills/*/SKILL.md, so on current models the list is duplicated context - and an expensive one: it measured 12,045 chars across 29 skills on a prod agent, pushing project/CLAUDE.md to 51k against Claude Code's 40,000-char ceiling, past which the tail of the agent's own system prompt is silently truncated. OFF suppresses ONLY the skill bullets; the "Updating Integrations" guidance in the same managed block is real instruction and is always kept. Defaults ON (today's behaviour) - flip OFF per org to reclaim the headroom.`,

package/dist/mcp/slack-channel.js

@@ -36994,6 +36994,35 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_MODEL_API_ERROR_REPORTING_ENABLED"
   },
+  {
+    key: "model-policy-failover-trigger",
+    description: "Automatic model-policy failover (ENG-10156, ADR-0074). off = the trigger does not run. shadow = it evaluates every ingested model-API error against the policy's failover_trigger config and LOGS the decision with its inputs, acting on nothing. Enum gate; ships OFF.",
+    flagType: "enum",
+    // `armed` is DELIBERATELY not an allowed value yet.
+    //
+    // Nothing writes model_policy_failover_state with source='auto' — that is
+    // the actuation half, and it is gated behind a recorded shadow soak
+    // (ENG-10156 AC8). Offering `armed` now would be a setting an operator can
+    // select, that reports success, and that does nothing: the failure mode is
+    // worse than the missing feature, because it looks like a fleet running
+    // with automatic failover enabled. Add it in the same change that makes it
+    // act, not before.
+    allowedValues: ["off", "shadow"],
+    // OFF, not `shadow`, and the contrast with `channel-quarantine-mode` is the
+    // reason: that flag defaults to `shadow` because shadow WAS the live
+    // manager's compiled behaviour, so anything else would have changed the
+    // fleet. Here there is no incumbent behaviour to preserve — nothing has ever
+    // evaluated this — so `off` is the honest default and turning shadow on is a
+    // deliberate act with a soak attached to it.
+    defaultValue: "off",
+    envVar: "AGT_MODEL_POLICY_FAILOVER_TRIGGER_MODE",
+    // Marked sensitive ahead of `armed` existing: the value this flag will
+    // eventually carry moves a host onto a secondary binding whose credential
+    // may be ours (credential_owner: 'platform'), i.e. it spends money with no
+    // human in the loop. Declaring that now costs nothing and means the audited
+    // -flip behaviour is already in place on the day the value is added.
+    sensitive: true
+  },
   {
     key: "claude-md-skills-index",
     description: `Manager injects the "## Available Skills" bullet list (one line per installed skill, name + frontmatter description) into the agent's project CLAUDE.md. Claude Code already surfaces installed skills to the model natively from .claude/skills/*/SKILL.md, so on current models the list is duplicated context - and an expensive one: it measured 12,045 chars across 29 skills on a prod agent, pushing project/CLAUDE.md to 51k against Claude Code's 40,000-char ceiling, past which the tail of the agent's own system prompt is silently truncated. OFF suppresses ONLY the skill bullets; the "Updating Integrations" guidance in the same managed block is real instruction and is always kept. Defaults ON (today's behaviour) - flip OFF per org to reclaim the headroom.`,

package/dist/mcp/telegram-channel.js

@@ -37126,6 +37126,35 @@ var FLAG_REGISTRY = [
     defaultValue: false,
     envVar: "AGT_MODEL_API_ERROR_REPORTING_ENABLED"
   },
+  {
+    key: "model-policy-failover-trigger",
+    description: "Automatic model-policy failover (ENG-10156, ADR-0074). off = the trigger does not run. shadow = it evaluates every ingested model-API error against the policy's failover_trigger config and LOGS the decision with its inputs, acting on nothing. Enum gate; ships OFF.",
+    flagType: "enum",
+    // `armed` is DELIBERATELY not an allowed value yet.
+    //
+    // Nothing writes model_policy_failover_state with source='auto' — that is
+    // the actuation half, and it is gated behind a recorded shadow soak
+    // (ENG-10156 AC8). Offering `armed` now would be a setting an operator can
+    // select, that reports success, and that does nothing: the failure mode is
+    // worse than the missing feature, because it looks like a fleet running
+    // with automatic failover enabled. Add it in the same change that makes it
+    // act, not before.
+    allowedValues: ["off", "shadow"],
+    // OFF, not `shadow`, and the contrast with `channel-quarantine-mode` is the
+    // reason: that flag defaults to `shadow` because shadow WAS the live
+    // manager's compiled behaviour, so anything else would have changed the
+    // fleet. Here there is no incumbent behaviour to preserve — nothing has ever
+    // evaluated this — so `off` is the honest default and turning shadow on is a
+    // deliberate act with a soak attached to it.
+    defaultValue: "off",
+    envVar: "AGT_MODEL_POLICY_FAILOVER_TRIGGER_MODE",
+    // Marked sensitive ahead of `armed` existing: the value this flag will
+    // eventually carry moves a host onto a secondary binding whose credential
+    // may be ours (credential_owner: 'platform'), i.e. it spends money with no
+    // human in the loop. Declaring that now costs nothing and means the audited
+    // -flip behaviour is already in place on the day the value is added.
+    sensitive: true
+  },
   {
     key: "claude-md-skills-index",
     description: `Manager injects the "## Available Skills" bullet list (one line per installed skill, name + frontmatter description) into the agent's project CLAUDE.md. Claude Code already surfaces installed skills to the model natively from .claude/skills/*/SKILL.md, so on current models the list is duplicated context - and an expensive one: it measured 12,045 chars across 29 skills on a prod agent, pushing project/CLAUDE.md to 51k against Claude Code's 40,000-char ceiling, past which the tail of the agent's own system prompt is silently truncated. OFF suppresses ONLY the skill bullets; the "Updating Integrations" guidance in the same managed block is real instruction and is always kept. Defaults ON (today's behaviour) - flip OFF per org to reclaim the headroom.`,

package/dist/{persistent-session-N4DJ4VXZ.js → persistent-session-CNVU25IF.js}

@@ -54,8 +54,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-2E2NKILK.js";
-import "./chunk-4Z4GFQAD.js";
+} from "./chunk-7YVKIYVW.js";
+import "./chunk-IHBWFKOW.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -114,4 +114,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-N4DJ4VXZ.js.map
+//# sourceMappingURL=persistent-session-CNVU25IF.js.map

package/dist/{responsiveness-probe-GYE5MIVB.js → responsiveness-probe-TZOKOH6C.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-2E2NKILK.js";
-import "./chunk-4Z4GFQAD.js";
+} from "./chunk-7YVKIYVW.js";
+import "./chunk-IHBWFKOW.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -764,4 +764,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-GYE5MIVB.js.map
+//# sourceMappingURL=responsiveness-probe-TZOKOH6C.js.map

package/dist/{session-auth-dead-K6B6D3WR.js → session-auth-dead-GRYXFDYD.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-4Z4GFQAD.js";
+} from "./chunk-IHBWFKOW.js";
 
 // src/lib/session-auth-dead.ts
 import { closeSync, openSync, readSync, readdirSync, statSync } from "fs";
@@ -203,4 +203,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-K6B6D3WR.js.map
+//# sourceMappingURL=session-auth-dead-GRYXFDYD.js.map

package/package.json

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