@integrity-labs/agt-cli 0.28.1053 → 0.28.1054

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

@@ -37900,6 +37900,16 @@ var FLAG_REGISTRY = [
     // put a first-of-its-kind classifier in front of real customer traffic with nothing
     // observed. Arm per-org, then revisit once there is evidence.
   },
+  {
+    key: "heartbeat-writes-claude-account-email",
+    description: "ENG-10796 (#6382): when ON, the host heartbeat writes the Claude account address it reads from the host (oauthAccount.emailAddress) into hosts.claude_account_email, so the Tokens label self-heals. OFF (default) the heartbeat never writes the column and the label stays whatever an operator set. Ships DARK because the column must first sit behind column-level grants (ENG-11162, #6596): until then any org member, and every co-tenant org on a pool host, can read it raw through Supabase REST, and on an IL-provisioned box the harvested address is a staff login (Obi Wan ecad15b6eff5). Evaluated at PLATFORM scope only: the heartbeat does not know the host org before its UPDATE, so flip the platform value once ENG-11162 is live.",
+    flagType: "boolean",
+    // Safe value is `false` (write nothing). A flag read error degrades here, so a flags outage
+    // can never start harvesting addresses into a customer-readable row.
+    defaultValue: false,
+    // Turning it on starts publishing an identifier into customer-visible rows (ADR-0022 §4).
+    sensitive: true
+  },
   {
     key: "email-guard-require-approval-enabled",
     description: "Platform enable-gate for the email-domain guardrail REQUIRE_APPROVAL stage (ENG-7939). When ON for an org, a scope at email_guard_stage=require_approval routes a send to a non-allowed domain into Human Approval (an Approve/Deny card) instead of a hard block: the rollout UI unlocks the option and the write routes accept require_approval. When OFF (default) the write routes reject require_approval and the UI shows it as not yet available, so no scope can select it. Structurally also depends on hitl-approval-routing being on (the approval broker fails closed to a hard block when routing is off). Evaluated per-org. Ships dark.",

package/dist/mcp/index.js

@@ -30231,6 +30231,16 @@ var FLAG_REGISTRY = [
     // put a first-of-its-kind classifier in front of real customer traffic with nothing
     // observed. Arm per-org, then revisit once there is evidence.
   },
+  {
+    key: "heartbeat-writes-claude-account-email",
+    description: "ENG-10796 (#6382): when ON, the host heartbeat writes the Claude account address it reads from the host (oauthAccount.emailAddress) into hosts.claude_account_email, so the Tokens label self-heals. OFF (default) the heartbeat never writes the column and the label stays whatever an operator set. Ships DARK because the column must first sit behind column-level grants (ENG-11162, #6596): until then any org member, and every co-tenant org on a pool host, can read it raw through Supabase REST, and on an IL-provisioned box the harvested address is a staff login (Obi Wan ecad15b6eff5). Evaluated at PLATFORM scope only: the heartbeat does not know the host org before its UPDATE, so flip the platform value once ENG-11162 is live.",
+    flagType: "boolean",
+    // Safe value is `false` (write nothing). A flag read error degrades here, so a flags outage
+    // can never start harvesting addresses into a customer-readable row.
+    defaultValue: false,
+    // Turning it on starts publishing an identifier into customer-visible rows (ADR-0022 §4).
+    sensitive: true
+  },
   {
     key: "email-guard-require-approval-enabled",
     description: "Platform enable-gate for the email-domain guardrail REQUIRE_APPROVAL stage (ENG-7939). When ON for an org, a scope at email_guard_stage=require_approval routes a send to a non-allowed domain into Human Approval (an Approve/Deny card) instead of a hard block: the rollout UI unlocks the option and the write routes accept require_approval. When OFF (default) the write routes reject require_approval and the UI shows it as not yet available, so no scope can select it. Structurally also depends on hitl-approval-routing being on (the approval broker fails closed to a hard block when routing is off). Evaluated per-org. Ships dark.",

package/dist/mcp/origami.js

@@ -44145,6 +44145,16 @@ var FLAG_REGISTRY = [
     // put a first-of-its-kind classifier in front of real customer traffic with nothing
     // observed. Arm per-org, then revisit once there is evidence.
   },
+  {
+    key: "heartbeat-writes-claude-account-email",
+    description: "ENG-10796 (#6382): when ON, the host heartbeat writes the Claude account address it reads from the host (oauthAccount.emailAddress) into hosts.claude_account_email, so the Tokens label self-heals. OFF (default) the heartbeat never writes the column and the label stays whatever an operator set. Ships DARK because the column must first sit behind column-level grants (ENG-11162, #6596): until then any org member, and every co-tenant org on a pool host, can read it raw through Supabase REST, and on an IL-provisioned box the harvested address is a staff login (Obi Wan ecad15b6eff5). Evaluated at PLATFORM scope only: the heartbeat does not know the host org before its UPDATE, so flip the platform value once ENG-11162 is live.",
+    flagType: "boolean",
+    // Safe value is `false` (write nothing). A flag read error degrades here, so a flags outage
+    // can never start harvesting addresses into a customer-readable row.
+    defaultValue: false,
+    // Turning it on starts publishing an identifier into customer-visible rows (ADR-0022 §4).
+    sensitive: true
+  },
   {
     key: "email-guard-require-approval-enabled",
     description: "Platform enable-gate for the email-domain guardrail REQUIRE_APPROVAL stage (ENG-7939). When ON for an org, a scope at email_guard_stage=require_approval routes a send to a non-allowed domain into Human Approval (an Approve/Deny card) instead of a hard block: the rollout UI unlocks the option and the write routes accept require_approval. When OFF (default) the write routes reject require_approval and the UI shows it as not yet available, so no scope can select it. Structurally also depends on hitl-approval-routing being on (the approval broker fails closed to a hard block when routing is off). Evaluated per-org. Ships dark.",

package/dist/mcp/slack-channel.js

@@ -38784,6 +38784,16 @@ var FLAG_REGISTRY = [
     // put a first-of-its-kind classifier in front of real customer traffic with nothing
     // observed. Arm per-org, then revisit once there is evidence.
   },
+  {
+    key: "heartbeat-writes-claude-account-email",
+    description: "ENG-10796 (#6382): when ON, the host heartbeat writes the Claude account address it reads from the host (oauthAccount.emailAddress) into hosts.claude_account_email, so the Tokens label self-heals. OFF (default) the heartbeat never writes the column and the label stays whatever an operator set. Ships DARK because the column must first sit behind column-level grants (ENG-11162, #6596): until then any org member, and every co-tenant org on a pool host, can read it raw through Supabase REST, and on an IL-provisioned box the harvested address is a staff login (Obi Wan ecad15b6eff5). Evaluated at PLATFORM scope only: the heartbeat does not know the host org before its UPDATE, so flip the platform value once ENG-11162 is live.",
+    flagType: "boolean",
+    // Safe value is `false` (write nothing). A flag read error degrades here, so a flags outage
+    // can never start harvesting addresses into a customer-readable row.
+    defaultValue: false,
+    // Turning it on starts publishing an identifier into customer-visible rows (ADR-0022 §4).
+    sensitive: true
+  },
   {
     key: "email-guard-require-approval-enabled",
     description: "Platform enable-gate for the email-domain guardrail REQUIRE_APPROVAL stage (ENG-7939). When ON for an org, a scope at email_guard_stage=require_approval routes a send to a non-allowed domain into Human Approval (an Approve/Deny card) instead of a hard block: the rollout UI unlocks the option and the write routes accept require_approval. When OFF (default) the write routes reject require_approval and the UI shows it as not yet available, so no scope can select it. Structurally also depends on hitl-approval-routing being on (the approval broker fails closed to a hard block when routing is off). Evaluated per-org. Ships dark.",

package/dist/mcp/telegram-channel.js

@@ -38890,6 +38890,16 @@ var FLAG_REGISTRY = [
     // put a first-of-its-kind classifier in front of real customer traffic with nothing
     // observed. Arm per-org, then revisit once there is evidence.
   },
+  {
+    key: "heartbeat-writes-claude-account-email",
+    description: "ENG-10796 (#6382): when ON, the host heartbeat writes the Claude account address it reads from the host (oauthAccount.emailAddress) into hosts.claude_account_email, so the Tokens label self-heals. OFF (default) the heartbeat never writes the column and the label stays whatever an operator set. Ships DARK because the column must first sit behind column-level grants (ENG-11162, #6596): until then any org member, and every co-tenant org on a pool host, can read it raw through Supabase REST, and on an IL-provisioned box the harvested address is a staff login (Obi Wan ecad15b6eff5). Evaluated at PLATFORM scope only: the heartbeat does not know the host org before its UPDATE, so flip the platform value once ENG-11162 is live.",
+    flagType: "boolean",
+    // Safe value is `false` (write nothing). A flag read error degrades here, so a flags outage
+    // can never start harvesting addresses into a customer-readable row.
+    defaultValue: false,
+    // Turning it on starts publishing an identifier into customer-visible rows (ADR-0022 §4).
+    sensitive: true
+  },
   {
     key: "email-guard-require-approval-enabled",
     description: "Platform enable-gate for the email-domain guardrail REQUIRE_APPROVAL stage (ENG-7939). When ON for an org, a scope at email_guard_stage=require_approval routes a send to a non-allowed domain into Human Approval (an Approve/Deny card) instead of a hard block: the rollout UI unlocks the option and the write routes accept require_approval. When OFF (default) the write routes reject require_approval and the UI shows it as not yet available, so no scope can select it. Structurally also depends on hitl-approval-routing being on (the approval broker fails closed to a hard block when routing is off). Evaluated per-org. Ships dark.",

package/dist/{persistent-session-5RX4P7GP.js → persistent-session-3WRSJIDM.js}

@@ -65,8 +65,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-4ZH75WMF.js";
-import "./chunk-MQ4COFCI.js";
+} from "./chunk-AT7E625H.js";
+import "./chunk-2SGXGNDW.js";
 import "./chunk-OCMJ5E6J.js";
 import "./chunk-XWVM4KPK.js";
 import "./chunk-EL5MWGGH.js";
@@ -139,4 +139,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-5RX4P7GP.js.map
+//# sourceMappingURL=persistent-session-3WRSJIDM.js.map

package/dist/{responsiveness-probe-C75AUK6I.js → responsiveness-probe-2DF6VH7Q.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-4ZH75WMF.js";
-import "./chunk-MQ4COFCI.js";
+} from "./chunk-AT7E625H.js";
+import "./chunk-2SGXGNDW.js";
 import "./chunk-OCMJ5E6J.js";
 import "./chunk-XWVM4KPK.js";
 import "./chunk-EL5MWGGH.js";
@@ -802,4 +802,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-C75AUK6I.js.map
+//# sourceMappingURL=responsiveness-probe-2DF6VH7Q.js.map

package/dist/{session-auth-dead-VFRUHVTF.js → session-auth-dead-GRTHA2Z5.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-MQ4COFCI.js";
+} from "./chunk-2SGXGNDW.js";
 import "./chunk-DGUM43GV.js";
 
 // src/lib/session-auth-dead.ts
@@ -204,4 +204,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-VFRUHVTF.js.map
+//# sourceMappingURL=session-auth-dead-GRTHA2Z5.js.map

package/package.json

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