@integrity-labs/agt-cli 0.28.480 → 0.28.482

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

@@ -34852,17 +34852,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/mcp/index.js

@@ -21415,6 +21415,78 @@ function describeRecruitAgentResult(resp) {
   }
 }
 
+// src/agent-roles.ts
+function renderRole(r) {
+  const id = r.id ?? "(unknown)";
+  const title = r.title ?? id;
+  const tier = r.suggested_risk_tier ? ` \xB7 risk ${r.suggested_risk_tier}` : "";
+  const custom3 = r.source === "custom" ? " \xB7 custom to your org" : "";
+  const lines = [`- role_id: ${id} \u2014 ${title}${tier}${custom3}`];
+  if (r.summary && r.summary !== title) lines.push(`  ${r.summary}`);
+  const tasks = (r.default_tasks ?? []).filter((t) => t && t.name);
+  if (tasks.length > 0) {
+    const shown = tasks.slice(0, 4).map((t) => `${t.name}${t.cadence ? ` (${t.cadence})` : ""}`);
+    const more = tasks.length > shown.length ? `, +${tasks.length - shown.length} more` : "";
+    lines.push(`  comes with ${tasks.length} scheduled task(s): ${shown.join("; ")}${more}`);
+  }
+  if (r.bundled_skill_count && r.bundled_skill_count > 0) {
+    lines.push(`  comes with ${r.bundled_skill_count} bundled skill(s)`);
+  }
+  if (r.suggested_integrations && r.suggested_integrations.length > 0) {
+    lines.push(`  typically needs: ${r.suggested_integrations.join(", ")}`);
+  }
+  return lines.join("\n");
+}
+function describeListAgentRolesResult(resp) {
+  if (resp.status === "feature_disabled") {
+    return {
+      text: `${resp.message ?? "Recruiting teammates is not enabled for this organization."} This is a setting, not a fault \u2014 do not retry.`,
+      isError: true
+    };
+  }
+  if (resp.status !== "ok" || !Array.isArray(resp.roles)) {
+    return {
+      text: `Could not load the role catalog${resp.message ? `: ${resp.message}` : ""}. Do not invent a role in its place \u2014 a role label that is not in the catalog will not provision the role's scheduled tasks or skills. Try again shortly, or tell your operator.`,
+      isError: true
+    };
+  }
+  if (resp.roles.length === 0) {
+    return {
+      text: "The role catalog came back empty, which is unexpected. Do not substitute a made-up role \u2014 tell your operator.",
+      isError: true
+    };
+  }
+  const labels = /* @__PURE__ */ new Map();
+  for (const c of resp.categories ?? []) {
+    if (c?.id) labels.set(c.id, c.label ?? c.id);
+  }
+  const byCategory = /* @__PURE__ */ new Map();
+  for (const r of resp.roles) {
+    const key = r.category ?? "other";
+    const bucket = byCategory.get(key);
+    if (bucket) bucket.push(r);
+    else byCategory.set(key, [r]);
+  }
+  const ordered = [
+    ...[...labels.keys()].filter((k) => byCategory.has(k)),
+    ...[...byCategory.keys()].filter((k) => !labels.has(k))
+  ];
+  const sections = ordered.map((key) => {
+    const heading = labels.get(key) ?? key;
+    const body = (byCategory.get(key) ?? []).map(renderRole).join("\n");
+    return `${heading}:
+${body}`;
+  });
+  return {
+    text: `${resp.roles.length} role(s) available to your organization.
+
+${sections.join("\n\n")}
+
+Pass the exact role_id to recruit_agent as \`role_id\`. Choosing a catalog role is strongly preferred over a free-text role: it seeds the new agent's description and risk tier, and its scheduled tasks and bundled skills are provisioned automatically. A made-up role label gets none of that. Only use a custom role when nothing here fits the remit you agreed with the person you are interviewing.`,
+    isError: false
+  };
+}
+
 // src/request-reconnect.ts
 function describeReconnectRequestResult(resp) {
   switch (resp.status) {
@@ -22599,9 +22671,44 @@ server.tool(
     return { content: [{ type: "text", text }], ...isError ? { isError: true } : {} };
   }
 );
+server.tool(
+  "list_agent_roles",
+  "List the predefined agent roles available to your organization. Call this BEFORE recruit_agent, and go through the results with the person who asked, so the new teammate is created from a curated role rather than a label you invented. Each role carries a vetted description, a risk tier, scheduled tasks and bundled skills that are provisioned automatically when the role is used \u2014 a made-up role label gets none of that. Pass the chosen role_id to recruit_agent.",
+  {},
+  async () => {
+    if (!AGT_AGENT_CODE_NAME) {
+      return {
+        content: [{ type: "text", text: "Error: AGT_AGENT_CODE_NAME not configured." }],
+        isError: true
+      };
+    }
+    let resp;
+    try {
+      resp = await apiGet(
+        `/host/agent-roles?agent_code_name=${encodeURIComponent(AGT_AGENT_CODE_NAME)}`
+      );
+    } catch (err) {
+      process.stderr.write(
+        `list_agent_roles: GET /host/agent-roles failed: ${err instanceof Error ? err.message : String(err)}
+`
+      );
+      return {
+        content: [
+          {
+            type: "text",
+            text: "Could not reach the role catalog. Do not substitute a made-up role \u2014 a label that is not in the catalog provisions no tasks and no skills. Try again shortly."
+          }
+        ],
+        isError: true
+      };
+    }
+    const { text, isError } = describeListAgentRolesResult(resp);
+    return { content: [{ type: "text", text }], ...isError ? { isError: true } : {} };
+  }
+);
 server.tool(
   "recruit_agent",
-  "Propose a NEW teammate agent for your organization when the work in front of you genuinely needs a different agent \u2014 a distinct role, a separate remit, or capacity you cannot cover yourself. This does NOT create anything: it sends a request to an organization owner, who approves or denies it. Use it sparingly and only when you can say concretely what the new agent is for; do not use it to duplicate yourself, to get around a tool you are missing (use request_feature), or because a single task is large. After calling this, stop and report that it is awaiting approval \u2014 poll with check_approval if you need the outcome.",
+  "Propose a NEW teammate agent for your organization when the work in front of you genuinely needs a different agent \u2014 a distinct role, a separate remit, or capacity you cannot cover yourself. This does NOT create anything: it sends a request to an organization owner, who approves or denies it. INTERVIEW THE PERSON WHO ASKED BEFORE CALLING THIS. You need their answers, not your own assumptions, for: what the agent is responsible for, what it must NOT do, how they will judge whether it is working, and who it reports to (use directory_lookup to get that id). Call list_agent_roles first and agree a role with them \u2014 a catalog role brings a vetted description, scheduled tasks and skills that a made-up role label does not. If you cannot get those answers, ask for them; do not fill them in yourself. Use this sparingly: do not duplicate yourself, do not use it to get around a tool you are missing (use request_feature), and do not use it because a single task is large. After calling this, stop and report that it is awaiting approval \u2014 poll with check_approval if you need the outcome.",
   {
     code_name: external_exports.string().min(1).max(64).regex(/^[a-z0-9]+(-[a-z0-9]+)*$/, "code_name must be kebab-case").describe(
       'kebab-case identifier for the proposed agent (lowercase, hyphen-separated), e.g. "invoice-helper". If the name is already taken in your team a numeric suffix is added automatically.'
@@ -22610,7 +22717,25 @@ server.tool(
     description: external_exports.string().min(20).max(2e3).describe(
       "What this teammate is FOR: its remit, the work it would take on, and why that work needs a separate agent. A human reads this to decide \u2014 be specific and honest. Vague descriptions get denied."
     ),
-    role: external_exports.string().max(200).optional().describe('Optional short role label for the proposed agent, e.g. "Accounts receivable".'),
+    role_id: external_exports.string().max(120).optional().describe(
+      "Preferred. The id of a role from list_agent_roles, agreed with the person you interviewed. Using one seeds the new agent's description and risk tier from the catalog and provisions that role's scheduled tasks and bundled skills on approval. A free-text role gets none of that."
+    ),
+    role: external_exports.string().max(200).optional().describe(
+      'Only when no catalog role fits: a short free-text role label, e.g. "Accounts receivable". Ignored when role_id is supplied.'
+    ),
+    responsibilities: external_exports.array(external_exports.string().min(3).max(300)).min(1).max(8).describe(
+      "What this teammate will be responsible for, in the words of the person who asked for it. Ask them \u2014 do not write this yourself. One short bullet each."
+    ),
+    boundaries: external_exports.array(external_exports.string().min(3).max(300)).min(1).max(8).describe(
+      "What this teammate must NOT do \u2014 the limits of its remit, agreed explicitly with the person you interviewed. This is the field approvers rely on most, so ask the question directly rather than inferring the answer."
+    ),
+    success_criteria: external_exports.array(external_exports.string().min(3).max(300)).min(1).max(8).describe(
+      "How the person will judge whether this teammate is working. Ask them for concrete, checkable statements."
+    ),
+    reports_to: external_exports.string().uuid().describe(
+      "Who this teammate answers to: the uuid of an existing agent or person in your organization. Ask the requester, then use directory_lookup to resolve the id \u2014 do not guess it."
+    ),
+    reports_to_type: external_exports.enum(["agent", "person"]).describe("Whether reports_to is another 'agent' or a 'person' (a human in your organization)."),
     reason: external_exports.string().max(1e3).optional().describe(
       "Optional context for the approver: what prompted this now (a spike in volume, a user request, a gap you keep hitting). Shown as context only \u2014 the decision is made on the description above."
     ),
@@ -22632,6 +22757,16 @@ server.tool(
         code_name: params.code_name,
         display_name: params.display_name,
         description: params.description,
+        // ENG-8306: the interviewed remit. Sent unconditionally — the API
+        // REJECTS a proposal missing any of these, which is what makes the
+        // interview mandatory rather than advisory (the server cannot observe
+        // that the conversation happened, only that its output is present).
+        responsibilities: params.responsibilities,
+        boundaries: params.boundaries,
+        success_criteria: params.success_criteria,
+        reports_to: params.reports_to,
+        reports_to_type: params.reports_to_type,
+        ...params.role_id ? { role_id: params.role_id } : {},
         ...params.role ? { role: params.role } : {},
         ...params.reason ? { reason: params.reason } : {},
         ...params.host_id ? { host_id: params.host_id } : {}
@@ -24034,6 +24169,10 @@ var LOCAL_TOOL_NAMES = /* @__PURE__ */ new Set([
   // server-side org-scoped agent-recruit flag, see the registration comment).
   // No API tool shares this name; listed here to keep the lockstep guard green.
   "recruit_agent",
+  // ENG-8306: enumerate the org's role catalog so a recruit can pick a curated
+  // role instead of inventing a free-text label. Always registered for the same
+  // reason as recruit_agent — the gate is server-side.
+  "list_agent_roles",
   // ENG-6686: self-service identity edit (always registered). Listed here to
   // keep the lockstep guard green; no API tool shares this name.
   "update_identity",

package/dist/mcp/origami.js

@@ -40799,17 +40799,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/mcp/slack-channel.js

@@ -35077,17 +35077,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/mcp/telegram-channel.js

@@ -35403,17 +35403,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/{persistent-session-USTI74Q5.js → persistent-session-IBMUPQZ2.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-EOH75U22.js";
+} from "./chunk-DNC5JGOV.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-USTI74Q5.js.map
+//# sourceMappingURL=persistent-session-IBMUPQZ2.js.map

package/dist/{responsiveness-probe-3PRCIAML.js → responsiveness-probe-QBLQIMZR.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-EOH75U22.js";
+} from "./chunk-DNC5JGOV.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -596,4 +596,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-3PRCIAML.js.map
+//# sourceMappingURL=responsiveness-probe-QBLQIMZR.js.map

package/package.json

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