@integrity-labs/agt-cli 0.28.808 → 0.28.810

package/dist/mcp/origami.js

@@ -39990,7 +39990,15 @@ var INTEGRATION_REGISTRY = [
     // integration_rate_cards; this only declares the model + meter.
     premium: {
       pricing: "usage",
-      note: "Billed per minute of real-time voice conversation.",
+      // THE OPT-IN AUTHORISES BOTH METERS, SO THE NOTE NAMES BOTH (ENG-9913).
+      // This string is the point of sale — it renders in the add-integration
+      // dialog an org admin reads before opting in — and it described only
+      // `voice_session` while the same opt-in, and the same $50 pool, had also
+      // covered Ninja Notes cloud transcription since ENG-9870. "Of audio"
+      // rather than "of meeting" is load-bearing: the two capture sources post
+      // independently, so an hour-long meeting on default settings spends two
+      // audio-hours (ADR-0063 §2a).
+      note: "Billed per minute of real-time voice conversation, and per hour of audio for Ninja Notes cloud transcription \u2014 both against the same monthly budget.",
       meters: [
         { event_type: "voice_session", unit: "minute" },
         // ENG-9870. Ninja Notes cloud transcription, on the SAME definition id
@@ -40002,16 +40010,24 @@ var INTEGRATION_REGISTRY = [
         // `audio_hour`, not `minute`. The vendor prices per hour and the sell
         // price is per hour, so hours store exactly (50 minor) where minutes
         // would be 0.8333 repeating; `integration_usage_events.units` is
-        // `numeric`, so a 30-minute meeting records 0.5 units precisely. This
+        // `numeric`, so 30 minutes of audio records 0.5 units precisely. This
         // is the answer to ENG-9773 §10.1's open question about whether hours
         // convert to minutes or the vocabulary gains hours.
         //
-        // NOTHING RECORDS THIS EVENT YET. Metering belongs at the chokepoint
-        // where audio is actually sent, and ENG-9868 left the transport
-        // injected with no implementation. The rate card exists first
-        // deliberately: a billable event with no USD rate makes
-        // `evaluateUsageBudget` throw, and on a SHARED pool that would break
-        // Voice Chat's budget check, not just this one.
+        // AN AUDIO-HOUR IS NOT A MEETING-HOUR (ENG-9913, Brad, 2026-09-03). The
+        // Mac captures system audio and the microphone as two independent
+        // pipelines that post separately, and both default on, so the ordinary
+        // meeting records two units per wall-clock hour. That is deliberate: the
+        // audio-hour is what we buy, since xAI bills on the duration uploaded.
+        // Pricing per meeting-hour would have varied the markup with a capture
+        // toggle and could only have been built on a client's assertion about
+        // how many pipelines were live. See ADR-0063 §2a.
+        //
+        // THE CHOKEPOINT EXISTS NOW — `POST /notes/transcribe` (ENG-9913)
+        // reserves against this meter before the vendor call, from the bytes it
+        // received. The rate card still had to land first, in ENG-9870: a
+        // billable event with no USD rate makes `evaluateUsageBudget` throw, and
+        // on a SHARED pool that would break Voice Chat's budget check too.
         { event_type: "transcription", unit: "audio_hour" }
       ]
     }
@@ -40908,7 +40924,18 @@ var INTEGRATION_REGISTRY = [
     // premium surface — is the structurally right answer and the follow-up.
     premium: {
       pricing: "included",
-      note: "Notes are included in your plan. Transcription runs on your own Mac and no platform summariser runs, so nothing is metered per note \u2014 the agent turn that reads it is billed as agent-hours like any other. Live meeting advising is the one exception: it is turned on separately, and billed per minute the advisor is armed."
+      // "THE ONE EXCEPTION" BECAME TWO (ENG-9913). Cloud transcription is the
+      // second metered capability under this integration, and this sentence was
+      // true only for as long as its flag stayed off — it would have become
+      // false on arming, silently, in a consent dialog. Both exceptions are
+      // written the same way, and both are still off until someone turns them
+      // on, so the sentence is accurate before and after the rollout.
+      //
+      // "Per hour of AUDIO" is deliberate here too: the two capture sources post
+      // independently, so an hour-long meeting on default settings spends two
+      // audio-hours (ADR-0063 §2a). The Mac's own caption carries the fuller
+      // explanation, at the point where the person choosing it can read it.
+      note: "Notes are included in your plan. Transcription runs on your own Mac by default and no platform summariser runs, so nothing is metered per note \u2014 the agent turn that reads it is billed as agent-hours like any other. Two capabilities are turned on separately and billed when they are: live meeting advising, per minute the advisor is armed; and cloud transcription, per hour of audio."
     }
   },
   {
@@ -43395,6 +43422,18 @@ var FLAG_REGISTRY = [
     // agent-hours-billing-enabled.
     sensitive: true
   },
+  {
+    key: "cloud-speech-to-text",
+    description: 'Cloud transcription in Ninja Notes (ENG-9913). When ON for an org, a person recording a meeting on the Mac may choose to have each capture window transcribed by xAI instead of on-device: the window is POSTed to /notes/transcribe, proxied to xAI with the platform key, metered as grok-voice/transcription per audio_hour, and the text comes back with no speaker labels. THIS IS OUR ROLLOUT GATE AND IT IS THE THIRD KEY, NOT THE FIRST. Three things must all be true before a window leaves the Mac: the org holds the grok-voice premium opt-in (authorisation, resolveCloudSttEntitlement), the user has elected it per-install (consent, CaptureSettings.cloudTranscriptionEnabled), and this flag is on (our own readiness). Without this flag the first two alone were sufficient, which is why it exists: resolveCloudSttEntitlement reports enabled for every org that ever bought Voice Chat, so the route would go live for all of them the moment it deployed. It is what finally lets the server emit `not_available` \u2014 CloudTranscriptionRefusal.notRolledOut has shipped since ENG-9869 carrying the sentence "Cloud transcription is not available for your organisation yet" with nothing able to produce it. Boolean gate; ships dark. OFF NEVER COSTS THE RECORDING. An org without the flag \u2014 or a flag read that fails \u2014 transcribes on-device exactly as before; the microphone still starts and the note is still transcribed and delivered. Same direction as live-meeting-advisor and for the same reason: the user pressed Record and a recording is what they are owed. It is also what makes rollback cheap, because flipping this off mid-flight degrades in-progress meetings to on-device rather than breaking them. Deliberately NO envVar. This is an org-scoped gate, and an envVar is highest-precedence per ADR-0022 \u2014 a literal in sst.config.ts would pin every stage and make the admin control do nothing, the ENG-8303 class exactly. No `since`: the reader is the API route, not a host-side agt-cli consumer, so this does not depend on fleet convergence. The Mac client is a separate fleet that reports no version at all, which is precisely why the gate has to live server-side.',
+    flagType: "boolean",
+    defaultValue: false,
+    // Turning it ON starts sending meeting audio — INCLUDING the other side of
+    // the call, whose participants have not been asked — to a third-party
+    // vendor, and arms a per-audio-hour meter against the org's shared
+    // grok-voice budget. Either half alone would warrant the confirm ADR-0022
+    // §4 reserves for deliberate, audited flips.
+    sensitive: true
+  },
   {
     key: "first-party-token-refusal",
     description: "ENG-8972 AC4 / ADR-0076 decision 2 \u2014 whether `resolveUserId` (packages/api/src/middleware/auth.ts) REFUSES a bearer token carrying a first-party marker that is foreign to the host-exchange lane. SUPABASE_JWT_SECRET is symmetric and signs twelve distinct token families; the generic Bearer door has always admitted any of them that mints a uuid-shaped `sub`, so a token minted for one purpose authenticates as a user for every purpose. off = the capture never runs (no log, no refusal). shadow = record the population an enforcement flip would change, on BOTH admitting lanes (lane=gotrue, lane=sub-claim), and refuse nothing \u2014 this is exactly the behaviour compiled into prod today. enforce = return null with reason=foreign-first-party-marker, above the strategy split, so the token reaches neither GoTrue nor the sub-claim lane. DEFAULT IS `shadow`, NOT `off`, and the divergence is deliberate \u2014 the shadow lines have been live in prod since 68863974b, and they are the soak instrument. Defaulting to `off` would silently switch off the measurement this flag exists to act on: the channel-quarantine-mode landmine (ENG-6252) in its exact shape. A flag-read failure degrades to `shadow` for the same reason it fails open elsewhere on this path: this is the platform front door, and a `feature_flags` blip must not start refusing the fleet. Deliberately NO envVar. The consumer is the API Lambda, whose environment block is at the AWS 4KB cap (ENG-7972), and an envVar is highest-precedence per ADR-0022 \u2014 a literal in sst.config.ts would pin every stage and make the admin control do nothing (ENG-8303). The flag value IS the kill switch: a flip back to shadow takes effect within the ~60s evaluation cache, with no deploy.",

package/dist/mcp/slack-channel.js

@@ -34106,7 +34106,15 @@ var INTEGRATION_REGISTRY = [
     // integration_rate_cards; this only declares the model + meter.
     premium: {
       pricing: "usage",
-      note: "Billed per minute of real-time voice conversation.",
+      // THE OPT-IN AUTHORISES BOTH METERS, SO THE NOTE NAMES BOTH (ENG-9913).
+      // This string is the point of sale — it renders in the add-integration
+      // dialog an org admin reads before opting in — and it described only
+      // `voice_session` while the same opt-in, and the same $50 pool, had also
+      // covered Ninja Notes cloud transcription since ENG-9870. "Of audio"
+      // rather than "of meeting" is load-bearing: the two capture sources post
+      // independently, so an hour-long meeting on default settings spends two
+      // audio-hours (ADR-0063 §2a).
+      note: "Billed per minute of real-time voice conversation, and per hour of audio for Ninja Notes cloud transcription \u2014 both against the same monthly budget.",
       meters: [
         { event_type: "voice_session", unit: "minute" },
         // ENG-9870. Ninja Notes cloud transcription, on the SAME definition id
@@ -34118,16 +34126,24 @@ var INTEGRATION_REGISTRY = [
         // `audio_hour`, not `minute`. The vendor prices per hour and the sell
         // price is per hour, so hours store exactly (50 minor) where minutes
         // would be 0.8333 repeating; `integration_usage_events.units` is
-        // `numeric`, so a 30-minute meeting records 0.5 units precisely. This
+        // `numeric`, so 30 minutes of audio records 0.5 units precisely. This
         // is the answer to ENG-9773 §10.1's open question about whether hours
         // convert to minutes or the vocabulary gains hours.
         //
-        // NOTHING RECORDS THIS EVENT YET. Metering belongs at the chokepoint
-        // where audio is actually sent, and ENG-9868 left the transport
-        // injected with no implementation. The rate card exists first
-        // deliberately: a billable event with no USD rate makes
-        // `evaluateUsageBudget` throw, and on a SHARED pool that would break
-        // Voice Chat's budget check, not just this one.
+        // AN AUDIO-HOUR IS NOT A MEETING-HOUR (ENG-9913, Brad, 2026-09-03). The
+        // Mac captures system audio and the microphone as two independent
+        // pipelines that post separately, and both default on, so the ordinary
+        // meeting records two units per wall-clock hour. That is deliberate: the
+        // audio-hour is what we buy, since xAI bills on the duration uploaded.
+        // Pricing per meeting-hour would have varied the markup with a capture
+        // toggle and could only have been built on a client's assertion about
+        // how many pipelines were live. See ADR-0063 §2a.
+        //
+        // THE CHOKEPOINT EXISTS NOW — `POST /notes/transcribe` (ENG-9913)
+        // reserves against this meter before the vendor call, from the bytes it
+        // received. The rate card still had to land first, in ENG-9870: a
+        // billable event with no USD rate makes `evaluateUsageBudget` throw, and
+        // on a SHARED pool that would break Voice Chat's budget check too.
         { event_type: "transcription", unit: "audio_hour" }
       ]
     }
@@ -35024,7 +35040,18 @@ var INTEGRATION_REGISTRY = [
     // premium surface — is the structurally right answer and the follow-up.
     premium: {
       pricing: "included",
-      note: "Notes are included in your plan. Transcription runs on your own Mac and no platform summariser runs, so nothing is metered per note \u2014 the agent turn that reads it is billed as agent-hours like any other. Live meeting advising is the one exception: it is turned on separately, and billed per minute the advisor is armed."
+      // "THE ONE EXCEPTION" BECAME TWO (ENG-9913). Cloud transcription is the
+      // second metered capability under this integration, and this sentence was
+      // true only for as long as its flag stayed off — it would have become
+      // false on arming, silently, in a consent dialog. Both exceptions are
+      // written the same way, and both are still off until someone turns them
+      // on, so the sentence is accurate before and after the rollout.
+      //
+      // "Per hour of AUDIO" is deliberate here too: the two capture sources post
+      // independently, so an hour-long meeting on default settings spends two
+      // audio-hours (ADR-0063 §2a). The Mac's own caption carries the fuller
+      // explanation, at the point where the person choosing it can read it.
+      note: "Notes are included in your plan. Transcription runs on your own Mac by default and no platform summariser runs, so nothing is metered per note \u2014 the agent turn that reads it is billed as agent-hours like any other. Two capabilities are turned on separately and billed when they are: live meeting advising, per minute the advisor is armed; and cloud transcription, per hour of audio."
     }
   },
   {
@@ -37918,6 +37945,18 @@ var FLAG_REGISTRY = [
     // agent-hours-billing-enabled.
     sensitive: true
   },
+  {
+    key: "cloud-speech-to-text",
+    description: 'Cloud transcription in Ninja Notes (ENG-9913). When ON for an org, a person recording a meeting on the Mac may choose to have each capture window transcribed by xAI instead of on-device: the window is POSTed to /notes/transcribe, proxied to xAI with the platform key, metered as grok-voice/transcription per audio_hour, and the text comes back with no speaker labels. THIS IS OUR ROLLOUT GATE AND IT IS THE THIRD KEY, NOT THE FIRST. Three things must all be true before a window leaves the Mac: the org holds the grok-voice premium opt-in (authorisation, resolveCloudSttEntitlement), the user has elected it per-install (consent, CaptureSettings.cloudTranscriptionEnabled), and this flag is on (our own readiness). Without this flag the first two alone were sufficient, which is why it exists: resolveCloudSttEntitlement reports enabled for every org that ever bought Voice Chat, so the route would go live for all of them the moment it deployed. It is what finally lets the server emit `not_available` \u2014 CloudTranscriptionRefusal.notRolledOut has shipped since ENG-9869 carrying the sentence "Cloud transcription is not available for your organisation yet" with nothing able to produce it. Boolean gate; ships dark. OFF NEVER COSTS THE RECORDING. An org without the flag \u2014 or a flag read that fails \u2014 transcribes on-device exactly as before; the microphone still starts and the note is still transcribed and delivered. Same direction as live-meeting-advisor and for the same reason: the user pressed Record and a recording is what they are owed. It is also what makes rollback cheap, because flipping this off mid-flight degrades in-progress meetings to on-device rather than breaking them. Deliberately NO envVar. This is an org-scoped gate, and an envVar is highest-precedence per ADR-0022 \u2014 a literal in sst.config.ts would pin every stage and make the admin control do nothing, the ENG-8303 class exactly. No `since`: the reader is the API route, not a host-side agt-cli consumer, so this does not depend on fleet convergence. The Mac client is a separate fleet that reports no version at all, which is precisely why the gate has to live server-side.',
+    flagType: "boolean",
+    defaultValue: false,
+    // Turning it ON starts sending meeting audio — INCLUDING the other side of
+    // the call, whose participants have not been asked — to a third-party
+    // vendor, and arms a per-audio-hour meter against the org's shared
+    // grok-voice budget. Either half alone would warrant the confirm ADR-0022
+    // §4 reserves for deliberate, audited flips.
+    sensitive: true
+  },
   {
     key: "first-party-token-refusal",
     description: "ENG-8972 AC4 / ADR-0076 decision 2 \u2014 whether `resolveUserId` (packages/api/src/middleware/auth.ts) REFUSES a bearer token carrying a first-party marker that is foreign to the host-exchange lane. SUPABASE_JWT_SECRET is symmetric and signs twelve distinct token families; the generic Bearer door has always admitted any of them that mints a uuid-shaped `sub`, so a token minted for one purpose authenticates as a user for every purpose. off = the capture never runs (no log, no refusal). shadow = record the population an enforcement flip would change, on BOTH admitting lanes (lane=gotrue, lane=sub-claim), and refuse nothing \u2014 this is exactly the behaviour compiled into prod today. enforce = return null with reason=foreign-first-party-marker, above the strategy split, so the token reaches neither GoTrue nor the sub-claim lane. DEFAULT IS `shadow`, NOT `off`, and the divergence is deliberate \u2014 the shadow lines have been live in prod since 68863974b, and they are the soak instrument. Defaulting to `off` would silently switch off the measurement this flag exists to act on: the channel-quarantine-mode landmine (ENG-6252) in its exact shape. A flag-read failure degrades to `shadow` for the same reason it fails open elsewhere on this path: this is the platform front door, and a `feature_flags` blip must not start refusing the fleet. Deliberately NO envVar. The consumer is the API Lambda, whose environment block is at the AWS 4KB cap (ENG-7972), and an envVar is highest-precedence per ADR-0022 \u2014 a literal in sst.config.ts would pin every stage and make the admin control do nothing (ENG-8303). The flag value IS the kill switch: a flip back to shadow takes effect within the ~60s evaluation cache, with no deploy.",

package/dist/mcp/telegram-channel.js

@@ -34264,7 +34264,15 @@ var INTEGRATION_REGISTRY = [
     // integration_rate_cards; this only declares the model + meter.
     premium: {
       pricing: "usage",
-      note: "Billed per minute of real-time voice conversation.",
+      // THE OPT-IN AUTHORISES BOTH METERS, SO THE NOTE NAMES BOTH (ENG-9913).
+      // This string is the point of sale — it renders in the add-integration
+      // dialog an org admin reads before opting in — and it described only
+      // `voice_session` while the same opt-in, and the same $50 pool, had also
+      // covered Ninja Notes cloud transcription since ENG-9870. "Of audio"
+      // rather than "of meeting" is load-bearing: the two capture sources post
+      // independently, so an hour-long meeting on default settings spends two
+      // audio-hours (ADR-0063 §2a).
+      note: "Billed per minute of real-time voice conversation, and per hour of audio for Ninja Notes cloud transcription \u2014 both against the same monthly budget.",
       meters: [
         { event_type: "voice_session", unit: "minute" },
         // ENG-9870. Ninja Notes cloud transcription, on the SAME definition id
@@ -34276,16 +34284,24 @@ var INTEGRATION_REGISTRY = [
         // `audio_hour`, not `minute`. The vendor prices per hour and the sell
         // price is per hour, so hours store exactly (50 minor) where minutes
         // would be 0.8333 repeating; `integration_usage_events.units` is
-        // `numeric`, so a 30-minute meeting records 0.5 units precisely. This
+        // `numeric`, so 30 minutes of audio records 0.5 units precisely. This
         // is the answer to ENG-9773 §10.1's open question about whether hours
         // convert to minutes or the vocabulary gains hours.
         //
-        // NOTHING RECORDS THIS EVENT YET. Metering belongs at the chokepoint
-        // where audio is actually sent, and ENG-9868 left the transport
-        // injected with no implementation. The rate card exists first
-        // deliberately: a billable event with no USD rate makes
-        // `evaluateUsageBudget` throw, and on a SHARED pool that would break
-        // Voice Chat's budget check, not just this one.
+        // AN AUDIO-HOUR IS NOT A MEETING-HOUR (ENG-9913, Brad, 2026-09-03). The
+        // Mac captures system audio and the microphone as two independent
+        // pipelines that post separately, and both default on, so the ordinary
+        // meeting records two units per wall-clock hour. That is deliberate: the
+        // audio-hour is what we buy, since xAI bills on the duration uploaded.
+        // Pricing per meeting-hour would have varied the markup with a capture
+        // toggle and could only have been built on a client's assertion about
+        // how many pipelines were live. See ADR-0063 §2a.
+        //
+        // THE CHOKEPOINT EXISTS NOW — `POST /notes/transcribe` (ENG-9913)
+        // reserves against this meter before the vendor call, from the bytes it
+        // received. The rate card still had to land first, in ENG-9870: a
+        // billable event with no USD rate makes `evaluateUsageBudget` throw, and
+        // on a SHARED pool that would break Voice Chat's budget check too.
         { event_type: "transcription", unit: "audio_hour" }
       ]
     }
@@ -35182,7 +35198,18 @@ var INTEGRATION_REGISTRY = [
     // premium surface — is the structurally right answer and the follow-up.
     premium: {
       pricing: "included",
-      note: "Notes are included in your plan. Transcription runs on your own Mac and no platform summariser runs, so nothing is metered per note \u2014 the agent turn that reads it is billed as agent-hours like any other. Live meeting advising is the one exception: it is turned on separately, and billed per minute the advisor is armed."
+      // "THE ONE EXCEPTION" BECAME TWO (ENG-9913). Cloud transcription is the
+      // second metered capability under this integration, and this sentence was
+      // true only for as long as its flag stayed off — it would have become
+      // false on arming, silently, in a consent dialog. Both exceptions are
+      // written the same way, and both are still off until someone turns them
+      // on, so the sentence is accurate before and after the rollout.
+      //
+      // "Per hour of AUDIO" is deliberate here too: the two capture sources post
+      // independently, so an hour-long meeting on default settings spends two
+      // audio-hours (ADR-0063 §2a). The Mac's own caption carries the fuller
+      // explanation, at the point where the person choosing it can read it.
+      note: "Notes are included in your plan. Transcription runs on your own Mac by default and no platform summariser runs, so nothing is metered per note \u2014 the agent turn that reads it is billed as agent-hours like any other. Two capabilities are turned on separately and billed when they are: live meeting advising, per minute the advisor is armed; and cloud transcription, per hour of audio."
     }
   },
   {
@@ -38076,6 +38103,18 @@ var FLAG_REGISTRY = [
     // agent-hours-billing-enabled.
     sensitive: true
   },
+  {
+    key: "cloud-speech-to-text",
+    description: 'Cloud transcription in Ninja Notes (ENG-9913). When ON for an org, a person recording a meeting on the Mac may choose to have each capture window transcribed by xAI instead of on-device: the window is POSTed to /notes/transcribe, proxied to xAI with the platform key, metered as grok-voice/transcription per audio_hour, and the text comes back with no speaker labels. THIS IS OUR ROLLOUT GATE AND IT IS THE THIRD KEY, NOT THE FIRST. Three things must all be true before a window leaves the Mac: the org holds the grok-voice premium opt-in (authorisation, resolveCloudSttEntitlement), the user has elected it per-install (consent, CaptureSettings.cloudTranscriptionEnabled), and this flag is on (our own readiness). Without this flag the first two alone were sufficient, which is why it exists: resolveCloudSttEntitlement reports enabled for every org that ever bought Voice Chat, so the route would go live for all of them the moment it deployed. It is what finally lets the server emit `not_available` \u2014 CloudTranscriptionRefusal.notRolledOut has shipped since ENG-9869 carrying the sentence "Cloud transcription is not available for your organisation yet" with nothing able to produce it. Boolean gate; ships dark. OFF NEVER COSTS THE RECORDING. An org without the flag \u2014 or a flag read that fails \u2014 transcribes on-device exactly as before; the microphone still starts and the note is still transcribed and delivered. Same direction as live-meeting-advisor and for the same reason: the user pressed Record and a recording is what they are owed. It is also what makes rollback cheap, because flipping this off mid-flight degrades in-progress meetings to on-device rather than breaking them. Deliberately NO envVar. This is an org-scoped gate, and an envVar is highest-precedence per ADR-0022 \u2014 a literal in sst.config.ts would pin every stage and make the admin control do nothing, the ENG-8303 class exactly. No `since`: the reader is the API route, not a host-side agt-cli consumer, so this does not depend on fleet convergence. The Mac client is a separate fleet that reports no version at all, which is precisely why the gate has to live server-side.',
+    flagType: "boolean",
+    defaultValue: false,
+    // Turning it ON starts sending meeting audio — INCLUDING the other side of
+    // the call, whose participants have not been asked — to a third-party
+    // vendor, and arms a per-audio-hour meter against the org's shared
+    // grok-voice budget. Either half alone would warrant the confirm ADR-0022
+    // §4 reserves for deliberate, audited flips.
+    sensitive: true
+  },
   {
     key: "first-party-token-refusal",
     description: "ENG-8972 AC4 / ADR-0076 decision 2 \u2014 whether `resolveUserId` (packages/api/src/middleware/auth.ts) REFUSES a bearer token carrying a first-party marker that is foreign to the host-exchange lane. SUPABASE_JWT_SECRET is symmetric and signs twelve distinct token families; the generic Bearer door has always admitted any of them that mints a uuid-shaped `sub`, so a token minted for one purpose authenticates as a user for every purpose. off = the capture never runs (no log, no refusal). shadow = record the population an enforcement flip would change, on BOTH admitting lanes (lane=gotrue, lane=sub-claim), and refuse nothing \u2014 this is exactly the behaviour compiled into prod today. enforce = return null with reason=foreign-first-party-marker, above the strategy split, so the token reaches neither GoTrue nor the sub-claim lane. DEFAULT IS `shadow`, NOT `off`, and the divergence is deliberate \u2014 the shadow lines have been live in prod since 68863974b, and they are the soak instrument. Defaulting to `off` would silently switch off the measurement this flag exists to act on: the channel-quarantine-mode landmine (ENG-6252) in its exact shape. A flag-read failure degrades to `shadow` for the same reason it fails open elsewhere on this path: this is the platform front door, and a `feature_flags` blip must not start refusing the fleet. Deliberately NO envVar. The consumer is the API Lambda, whose environment block is at the AWS 4KB cap (ENG-7972), and an envVar is highest-precedence per ADR-0022 \u2014 a literal in sst.config.ts would pin every stage and make the admin control do nothing (ENG-8303). The flag value IS the kill switch: a flip back to shadow takes effect within the ~60s evaluation cache, with no deploy.",

package/dist/{persistent-session-Q23JIYBR.js → persistent-session-LYJCGKH3.js}

@@ -49,8 +49,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-TLPQULYH.js";
-import "./chunk-SWUBTUYM.js";
+} from "./chunk-SBRKT2AV.js";
+import "./chunk-GBSP65E7.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -104,4 +104,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-Q23JIYBR.js.map
+//# sourceMappingURL=persistent-session-LYJCGKH3.js.map

package/dist/{responsiveness-probe-T2I27SCG.js → responsiveness-probe-XRSACVMN.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-TLPQULYH.js";
-import "./chunk-SWUBTUYM.js";
+} from "./chunk-SBRKT2AV.js";
+import "./chunk-GBSP65E7.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -745,4 +745,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-T2I27SCG.js.map
+//# sourceMappingURL=responsiveness-probe-XRSACVMN.js.map

package/dist/{session-auth-dead-O7DBSJ3W.js → session-auth-dead-Y6MASYWN.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-SWUBTUYM.js";
+} from "./chunk-GBSP65E7.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-O7DBSJ3W.js.map
+//# sourceMappingURL=session-auth-dead-Y6MASYWN.js.map

package/package.json

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