@integrity-labs/agt-cli 0.28.651 → 0.28.652

package/dist/{claude-pair-runtime-U52EA7NZ.js → claude-pair-runtime-E6BFNZUV.js}

@@ -100,7 +100,7 @@ async function spawnPairSession(session) {
     return { ok: true };
   } catch {
   }
-  const { resolveClaudeBinary } = await import("./persistent-session-DVZESZDD.js");
+  const { resolveClaudeBinary } = await import("./persistent-session-XXP4NGEP.js");
   const claudeBin = resolveClaudeBinary();
   const pairEnv = {
     ...process.env,
@@ -373,4 +373,4 @@ export {
   startClaudePair,
   submitClaudePairCode
 };
-//# sourceMappingURL=claude-pair-runtime-U52EA7NZ.js.map
+//# sourceMappingURL=claude-pair-runtime-E6BFNZUV.js.map

package/dist/lib/manager-worker.js

@@ -55,7 +55,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   tripClass
-} from "../chunk-EXMRWMXQ.js";
+} from "../chunk-6PR2K3XB.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -111,7 +111,7 @@ import {
   takeZombieDetection,
   toOpencodeModel,
   writeEgressAllowlist
-} from "../chunk-EUXCRRZU.js";
+} from "../chunk-E26EKDFP.js";
 import {
   ACCOUNT_ENFORCEMENT_MARKER_FILENAME,
   AnchorSessionClient,
@@ -192,7 +192,7 @@ import {
   subagentActivityAgeSeconds,
   sumTranscriptUsageInWindow,
   transcriptActivityAgeSeconds
-} from "../chunk-V5MUX3GI.js";
+} from "../chunk-HRMF6VUK.js";
 import {
   reapOrphanChannelMcps
 } from "../chunk-XWVM4KPK.js";
@@ -11609,7 +11609,7 @@ var pendingDayRolloverReset = /* @__PURE__ */ new Set();
 var dayRolloverInboundHold = /* @__PURE__ */ new Map();
 var INBOUND_HOLD_EPISODE_GAP_MS = 12e4;
 async function channelInboundActivityAgeSecondsFor(codeName) {
-  const { newestPendingInboundActivityMtimeMs } = await import("../responsiveness-probe-Q7SVASQS.js");
+  const { newestPendingInboundActivityMtimeMs } = await import("../responsiveness-probe-QSJ263ZW.js");
   const newest = newestPendingInboundActivityMtimeMs(dirname10(paneLogPath(codeName)));
   if (newest === null) return null;
   return Math.max(0, Math.floor((Date.now() - newest) / 1e3));
@@ -12252,7 +12252,7 @@ var agentRestartTimezoneInputs = /* @__PURE__ */ new Map();
 var lastVersionCheckAt = 0;
 var VERSION_CHECK_INTERVAL_MS = 5 * 60 * 1e3;
 var lastResponsivenessProbeAt = 0;
-var agtCliVersion = true ? "0.28.651" : "dev";
+var agtCliVersion = true ? "0.28.652" : "dev";
 function resolveBrewPath(execFileSync3) {
   try {
     const out = execFileSync3("which", ["brew"], { timeout: 5e3 }).toString().trim();
@@ -13560,7 +13560,7 @@ function flushRestartedAgentDiagnostics(hostId, codeNames) {
   if (codeNames.length === 0) return;
   void (async () => {
     try {
-      const { collectDiagnostics } = await import("../persistent-session-DVZESZDD.js");
+      const { collectDiagnostics } = await import("../persistent-session-XXP4NGEP.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics(codeNames, quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor)
@@ -13676,7 +13676,7 @@ async function pollCycleInner() {
     }
     try {
       const { detectHostSecurity } = await import("../host-security-6PDFG7F5.js");
-      const { collectDiagnostics } = await import("../persistent-session-DVZESZDD.js");
+      const { collectDiagnostics } = await import("../persistent-session-XXP4NGEP.js");
       const diagCodeNames = [...agentState.persistentSessionAgents];
       const agentDiagnostics = diagCodeNames.length > 0 ? collectDiagnostics(diagCodeNames, quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor) : void 0;
       let tailscaleHostname;
@@ -13799,7 +13799,7 @@ async function pollCycleInner() {
         collectPanelessActivityProbes,
         getResponsivenessIntervalMs,
         occupancyQualificationClassifications
-      } = await import("../responsiveness-probe-Q7SVASQS.js");
+      } = await import("../responsiveness-probe-QSJ263ZW.js");
       const probeIntervalMs = getResponsivenessIntervalMs();
       if (now - lastResponsivenessProbeAt > probeIntervalMs) {
         const probeCodeNames = [...agentState.persistentSessionAgents];
@@ -13909,7 +13909,7 @@ async function pollCycleInner() {
           collectResponsivenessProbes,
           livePendingInboundOldestAgeSeconds,
           parkPendingInbound
-        } = await import("../responsiveness-probe-Q7SVASQS.js");
+        } = await import("../responsiveness-probe-QSJ263ZW.js");
         const { getProjectDir: wedgeProjectDir } = await import("../scheduler-engine-NDP36U7O.js");
         const wedgeNow = /* @__PURE__ */ new Date();
         const liveAgents = agentState.persistentSessionAgents;
@@ -14065,7 +14065,7 @@ async function pollCycleInner() {
     }
     try {
       const { scrapeMcpFailedBannerCount } = await import("../pane-mcp-banner-scraper-JA437JIB.js");
-      const { probeSessionAuth } = await import("../session-auth-dead-RV3Z64TM.js");
+      const { probeSessionAuth } = await import("../session-auth-dead-HHZT5KIM.js");
       const observations = [];
       const pendingCacheCommits = [];
       const modelApiErrorReportingOn = hostFlagStore().getBoolean("model-api-error-reporting");
@@ -17698,7 +17698,7 @@ async function handleRestartDoorbell(agentId, requestedAt, restartReason) {
     void api.post("/host/restart-ack", { host_id: hostId, agent_id: agentId, restart_requested_at: requestedAt }).catch((err) => log(`[restart-lane] ack failed for '${codeName}': ${err.message}`));
     void (async () => {
       try {
-        const { collectDiagnostics } = await import("../persistent-session-DVZESZDD.js");
+        const { collectDiagnostics } = await import("../persistent-session-XXP4NGEP.js");
         await api.post("/host/heartbeat", {
           host_id: hostId,
           agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor)
@@ -17749,7 +17749,7 @@ async function respawnAgentAfterMcpStop(codeName, reason) {
     }
     try {
       const hostId = await getHostId();
-      const { collectDiagnostics } = await import("../persistent-session-DVZESZDD.js");
+      const { collectDiagnostics } = await import("../persistent-session-XXP4NGEP.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor)
@@ -18346,7 +18346,7 @@ async function processClaudePairSessions(agents) {
     killPairSession,
     pairTmuxSession,
     finalizeClaudePairOnboarding
-  } = await import("../claude-pair-runtime-U52EA7NZ.js");
+  } = await import("../claude-pair-runtime-E6BFNZUV.js");
   for (const pairId of pendingResp.cancelled_pair_ids ?? []) {
     log(`[claude-pair] sweeping orphan tmux session for pair ${pairId.slice(0, 8)}`);
     const killed = await killPairSession(pairTmuxSession(pairId));

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

@@ -33677,7 +33677,7 @@ var INTEGRATION_REGISTRY = [
     id: "firecrawl",
     name: "Firecrawl",
     category: "knowledge",
-    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account, or bring your own Firecrawl API key.",
+    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account.",
     // ENG-7217: Firecrawl migrates from a customer-API-key stdio MCP
     // (`npx firecrawl-mcp`, FIRECRAWL_API_KEY) to a PREMIUM, platform-managed
     // integration on the Deck / ElevenLabs model (ADR-0031, epic ENG-6920):
@@ -33688,16 +33688,30 @@ var INTEGRATION_REGISTRY = [
     // is metered at the one control-plane chokepoint and gated on a per-org opt-in
     // + monthly USD cap.
     //
-    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key` is
-    // now also offered so a customer can bring their OWN Firecrawl key. A BYO
+    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key`
+    // was also offered so a customer could bring their OWN Firecrawl key. A BYO
     // install (`credential_source='byo'`) authenticates with the customer's key
     // (stored encrypted on the install) and is NOT metered — its upstream cost is
-    // on the customer's own Firecrawl bill. BYO is gated on the plan-tier
-    // `byo_credentials` entitlement; managed stays the platform-key, billed path.
-    // `api_key` is the BYO option; the connect UI offers it via the toolkit's
-    // `auth_types` seed (Firecrawl surfaces through the premium list, not the
-    // native `installable` picker — that descriptor is for non-premium natives).
-    supported_auth_types: ["none", "api_key"],
+    // on the customer's own Firecrawl bill.
+    //
+    // ENG-9235: `api_key` is PARKED, not abandoned. BYO is gated on the plan-tier
+    // `byo_credentials` entitlement, which only `enterprise` has (the column is
+    // NOT NULL DEFAULT false, and ENG-9143 explicitly set it false for Team). The
+    // connect wizard never reads that flag, so offering `api_key` here sent every
+    // Team/Business customer to firecrawl.dev for a key we would then reject with
+    // a 403 `byo_not_entitled_by_plan` — after they had signed up for it.
+    //
+    // Removing it is also what removes that screen: the wizard's picker only
+    // renders for 2+ selectable auth types (`selectableWizardAuthMethods`), so a
+    // single `['none']` restores the friction-free managed install with no UI
+    // change. Restore `api_key` only together with an entitlement-aware wizard —
+    // see ENG-9236 for the proper fix.
+    //
+    // KEEP IN LOCKSTEP with the `firecrawl` row in
+    // packages/supabase/seeds/toolkit-definitions.json: that seed carries its own
+    // `auth_types` and is what `db:catalog:seed` upserts on every prod deploy, so
+    // editing this array alone changes nothing a customer can see.
+    supported_auth_types: ["none"],
     capabilities: [
       { id: "firecrawl:scrape", name: "Scrape Pages", description: "Fetch a single URL as clean markdown / structured data (firecrawl_scrape).", access: "write" },
       { id: "firecrawl:search", name: "Web Search", description: "Search the web and return ranked results, optionally scraped (firecrawl_search).", access: "write" },
@@ -36357,22 +36371,33 @@ var FLAG_REGISTRY = [
   },
   {
     key: "ninjafy-brand",
-    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: EVERY consumer evaluates in the active-org cookie scope \u2014 sidebar.tsx and top-nav.tsx via usePublicBooleanFlag, and (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 so a host- or agent-scoped row is accepted by the table but never reached by the console. The THEME is resolved SERVER-side deliberately (ENG-8858): the client hook starts at its default and updates after an async GET /flags, so gating a palette on it paints Augmented and repaints \u2014 a full-page colour flash, not just the wordmark flash it already causes. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
+    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: there is now exactly ONE consumer \u2014 (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 evaluating in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. It resolves the key ONCE per request and passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop. Resolution is SERVER-side deliberately: the client hook starts at its default and updates after an async GET /flags, so anything gated on it paints Augmented and then repaints. ENG-8858 moved the PALETTE for that reason (a full-page colour flash); ENG-9227 moved the WORDMARK, which had been the last surface still swapping after hydration. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
     flagType: "boolean",
     // Declared safe value is `false`: the pre-rebrand brand. `false` is also the
     // fail-closed direction — if the flag DB is unreachable we must show the brand
     // that is currently live and contractually correct, never leak an unannounced
     // rebrand to every customer at once.
     defaultValue: false,
-    // Read on BOTH sides, so the key must be in the browser-exposed public map:
-    // sidebar.tsx and top-nav.tsx are "use client" and resolve it via
-    // usePublicBooleanFlag for the WORDMARK, while (dashboard)/layout.tsx resolves
-    // it server-side via getPublicBooleanFlagServer for the THEME (ENG-8858) — a
-    // palette cannot wait for an async client fetch without flashing. Dropping
-    // `public` would break the two client readers, not just the server one.
-    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — every
-    // reader evaluates inside the active-org cookie's scope, which is exactly the
-    // org whose brand should be shown.
+    // ENG-9227: there are NO client readers of this key left. (dashboard)/
+    // layout.tsx resolves it ONCE server-side via getPublicBooleanFlagServer and
+    // passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop.
+    // ENG-8858 did that for the THEME; ENG-9227 finished the job for the
+    // WORDMARK, which had kept usePublicBooleanFlag and so kept swapping
+    // "augmented.team" to "ninjafy" after hydration.
+    //
+    // `public` MUST STAY ANYWAY, and this is the trap. It is tempting to read
+    // "no client readers" as "no longer needs to be public" — but
+    // getPublicBooleanFlagServer resolves against the very same `GET /flags`
+    // endpoint the browser uses, and that route filters to listPublicFlagKeys()
+    // (routes/flags.ts:72-75). A non-public key is simply absent from the map,
+    // so the server helper would fall through to its default and return `false`
+    // FOREVER — the brand quietly reverting to Augmented for every org, with no
+    // error anywhere. `public` here means "readable through the public map",
+    // not "read by a browser".
+    //
+    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — the
+    // single reader evaluates inside the active-org cookie's scope, which is
+    // exactly the org whose brand should be shown.
     public: true
   },
   {

package/dist/mcp/index.js

@@ -41016,7 +41016,7 @@ var INTEGRATION_REGISTRY = [
     id: "firecrawl",
     name: "Firecrawl",
     category: "knowledge",
-    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account, or bring your own Firecrawl API key.",
+    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account.",
     // ENG-7217: Firecrawl migrates from a customer-API-key stdio MCP
     // (`npx firecrawl-mcp`, FIRECRAWL_API_KEY) to a PREMIUM, platform-managed
     // integration on the Deck / ElevenLabs model (ADR-0031, epic ENG-6920):
@@ -41027,16 +41027,30 @@ var INTEGRATION_REGISTRY = [
     // is metered at the one control-plane chokepoint and gated on a per-org opt-in
     // + monthly USD cap.
     //
-    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key` is
-    // now also offered so a customer can bring their OWN Firecrawl key. A BYO
+    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key`
+    // was also offered so a customer could bring their OWN Firecrawl key. A BYO
     // install (`credential_source='byo'`) authenticates with the customer's key
     // (stored encrypted on the install) and is NOT metered — its upstream cost is
-    // on the customer's own Firecrawl bill. BYO is gated on the plan-tier
-    // `byo_credentials` entitlement; managed stays the platform-key, billed path.
-    // `api_key` is the BYO option; the connect UI offers it via the toolkit's
-    // `auth_types` seed (Firecrawl surfaces through the premium list, not the
-    // native `installable` picker — that descriptor is for non-premium natives).
-    supported_auth_types: ["none", "api_key"],
+    // on the customer's own Firecrawl bill.
+    //
+    // ENG-9235: `api_key` is PARKED, not abandoned. BYO is gated on the plan-tier
+    // `byo_credentials` entitlement, which only `enterprise` has (the column is
+    // NOT NULL DEFAULT false, and ENG-9143 explicitly set it false for Team). The
+    // connect wizard never reads that flag, so offering `api_key` here sent every
+    // Team/Business customer to firecrawl.dev for a key we would then reject with
+    // a 403 `byo_not_entitled_by_plan` — after they had signed up for it.
+    //
+    // Removing it is also what removes that screen: the wizard's picker only
+    // renders for 2+ selectable auth types (`selectableWizardAuthMethods`), so a
+    // single `['none']` restores the friction-free managed install with no UI
+    // change. Restore `api_key` only together with an entitlement-aware wizard —
+    // see ENG-9236 for the proper fix.
+    //
+    // KEEP IN LOCKSTEP with the `firecrawl` row in
+    // packages/supabase/seeds/toolkit-definitions.json: that seed carries its own
+    // `auth_types` and is what `db:catalog:seed` upserts on every prod deploy, so
+    // editing this array alone changes nothing a customer can see.
+    supported_auth_types: ["none"],
     capabilities: [
       { id: "firecrawl:scrape", name: "Scrape Pages", description: "Fetch a single URL as clean markdown / structured data (firecrawl_scrape).", access: "write" },
       { id: "firecrawl:search", name: "Web Search", description: "Search the web and return ranked results, optionally scraped (firecrawl_search).", access: "write" },
@@ -43247,22 +43261,33 @@ var FLAG_REGISTRY = [
   },
   {
     key: "ninjafy-brand",
-    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: EVERY consumer evaluates in the active-org cookie scope \u2014 sidebar.tsx and top-nav.tsx via usePublicBooleanFlag, and (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 so a host- or agent-scoped row is accepted by the table but never reached by the console. The THEME is resolved SERVER-side deliberately (ENG-8858): the client hook starts at its default and updates after an async GET /flags, so gating a palette on it paints Augmented and repaints \u2014 a full-page colour flash, not just the wordmark flash it already causes. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
+    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: there is now exactly ONE consumer \u2014 (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 evaluating in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. It resolves the key ONCE per request and passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop. Resolution is SERVER-side deliberately: the client hook starts at its default and updates after an async GET /flags, so anything gated on it paints Augmented and then repaints. ENG-8858 moved the PALETTE for that reason (a full-page colour flash); ENG-9227 moved the WORDMARK, which had been the last surface still swapping after hydration. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
     flagType: "boolean",
     // Declared safe value is `false`: the pre-rebrand brand. `false` is also the
     // fail-closed direction — if the flag DB is unreachable we must show the brand
     // that is currently live and contractually correct, never leak an unannounced
     // rebrand to every customer at once.
     defaultValue: false,
-    // Read on BOTH sides, so the key must be in the browser-exposed public map:
-    // sidebar.tsx and top-nav.tsx are "use client" and resolve it via
-    // usePublicBooleanFlag for the WORDMARK, while (dashboard)/layout.tsx resolves
-    // it server-side via getPublicBooleanFlagServer for the THEME (ENG-8858) — a
-    // palette cannot wait for an async client fetch without flashing. Dropping
-    // `public` would break the two client readers, not just the server one.
-    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — every
-    // reader evaluates inside the active-org cookie's scope, which is exactly the
-    // org whose brand should be shown.
+    // ENG-9227: there are NO client readers of this key left. (dashboard)/
+    // layout.tsx resolves it ONCE server-side via getPublicBooleanFlagServer and
+    // passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop.
+    // ENG-8858 did that for the THEME; ENG-9227 finished the job for the
+    // WORDMARK, which had kept usePublicBooleanFlag and so kept swapping
+    // "augmented.team" to "ninjafy" after hydration.
+    //
+    // `public` MUST STAY ANYWAY, and this is the trap. It is tempting to read
+    // "no client readers" as "no longer needs to be public" — but
+    // getPublicBooleanFlagServer resolves against the very same `GET /flags`
+    // endpoint the browser uses, and that route filters to listPublicFlagKeys()
+    // (routes/flags.ts:72-75). A non-public key is simply absent from the map,
+    // so the server helper would fall through to its default and return `false`
+    // FOREVER — the brand quietly reverting to Augmented for every org, with no
+    // error anywhere. `public` here means "readable through the public map",
+    // not "read by a browser".
+    //
+    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — the
+    // single reader evaluates inside the active-org cookie's scope, which is
+    // exactly the org whose brand should be shown.
     public: true
   },
   {

package/dist/mcp/origami.js

@@ -39897,7 +39897,7 @@ var INTEGRATION_REGISTRY = [
     id: "firecrawl",
     name: "Firecrawl",
     category: "knowledge",
-    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account, or bring your own Firecrawl API key.",
+    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account.",
     // ENG-7217: Firecrawl migrates from a customer-API-key stdio MCP
     // (`npx firecrawl-mcp`, FIRECRAWL_API_KEY) to a PREMIUM, platform-managed
     // integration on the Deck / ElevenLabs model (ADR-0031, epic ENG-6920):
@@ -39908,16 +39908,30 @@ var INTEGRATION_REGISTRY = [
     // is metered at the one control-plane chokepoint and gated on a per-org opt-in
     // + monthly USD cap.
     //
-    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key` is
-    // now also offered so a customer can bring their OWN Firecrawl key. A BYO
+    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key`
+    // was also offered so a customer could bring their OWN Firecrawl key. A BYO
     // install (`credential_source='byo'`) authenticates with the customer's key
     // (stored encrypted on the install) and is NOT metered — its upstream cost is
-    // on the customer's own Firecrawl bill. BYO is gated on the plan-tier
-    // `byo_credentials` entitlement; managed stays the platform-key, billed path.
-    // `api_key` is the BYO option; the connect UI offers it via the toolkit's
-    // `auth_types` seed (Firecrawl surfaces through the premium list, not the
-    // native `installable` picker — that descriptor is for non-premium natives).
-    supported_auth_types: ["none", "api_key"],
+    // on the customer's own Firecrawl bill.
+    //
+    // ENG-9235: `api_key` is PARKED, not abandoned. BYO is gated on the plan-tier
+    // `byo_credentials` entitlement, which only `enterprise` has (the column is
+    // NOT NULL DEFAULT false, and ENG-9143 explicitly set it false for Team). The
+    // connect wizard never reads that flag, so offering `api_key` here sent every
+    // Team/Business customer to firecrawl.dev for a key we would then reject with
+    // a 403 `byo_not_entitled_by_plan` — after they had signed up for it.
+    //
+    // Removing it is also what removes that screen: the wizard's picker only
+    // renders for 2+ selectable auth types (`selectableWizardAuthMethods`), so a
+    // single `['none']` restores the friction-free managed install with no UI
+    // change. Restore `api_key` only together with an entitlement-aware wizard —
+    // see ENG-9236 for the proper fix.
+    //
+    // KEEP IN LOCKSTEP with the `firecrawl` row in
+    // packages/supabase/seeds/toolkit-definitions.json: that seed carries its own
+    // `auth_types` and is what `db:catalog:seed` upserts on every prod deploy, so
+    // editing this array alone changes nothing a customer can see.
+    supported_auth_types: ["none"],
     capabilities: [
       { id: "firecrawl:scrape", name: "Scrape Pages", description: "Fetch a single URL as clean markdown / structured data (firecrawl_scrape).", access: "write" },
       { id: "firecrawl:search", name: "Web Search", description: "Search the web and return ranked results, optionally scraped (firecrawl_search).", access: "write" },
@@ -42107,22 +42121,33 @@ var FLAG_REGISTRY = [
   },
   {
     key: "ninjafy-brand",
-    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: EVERY consumer evaluates in the active-org cookie scope \u2014 sidebar.tsx and top-nav.tsx via usePublicBooleanFlag, and (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 so a host- or agent-scoped row is accepted by the table but never reached by the console. The THEME is resolved SERVER-side deliberately (ENG-8858): the client hook starts at its default and updates after an async GET /flags, so gating a palette on it paints Augmented and repaints \u2014 a full-page colour flash, not just the wordmark flash it already causes. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
+    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: there is now exactly ONE consumer \u2014 (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 evaluating in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. It resolves the key ONCE per request and passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop. Resolution is SERVER-side deliberately: the client hook starts at its default and updates after an async GET /flags, so anything gated on it paints Augmented and then repaints. ENG-8858 moved the PALETTE for that reason (a full-page colour flash); ENG-9227 moved the WORDMARK, which had been the last surface still swapping after hydration. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
     flagType: "boolean",
     // Declared safe value is `false`: the pre-rebrand brand. `false` is also the
     // fail-closed direction — if the flag DB is unreachable we must show the brand
     // that is currently live and contractually correct, never leak an unannounced
     // rebrand to every customer at once.
     defaultValue: false,
-    // Read on BOTH sides, so the key must be in the browser-exposed public map:
-    // sidebar.tsx and top-nav.tsx are "use client" and resolve it via
-    // usePublicBooleanFlag for the WORDMARK, while (dashboard)/layout.tsx resolves
-    // it server-side via getPublicBooleanFlagServer for the THEME (ENG-8858) — a
-    // palette cannot wait for an async client fetch without flashing. Dropping
-    // `public` would break the two client readers, not just the server one.
-    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — every
-    // reader evaluates inside the active-org cookie's scope, which is exactly the
-    // org whose brand should be shown.
+    // ENG-9227: there are NO client readers of this key left. (dashboard)/
+    // layout.tsx resolves it ONCE server-side via getPublicBooleanFlagServer and
+    // passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop.
+    // ENG-8858 did that for the THEME; ENG-9227 finished the job for the
+    // WORDMARK, which had kept usePublicBooleanFlag and so kept swapping
+    // "augmented.team" to "ninjafy" after hydration.
+    //
+    // `public` MUST STAY ANYWAY, and this is the trap. It is tempting to read
+    // "no client readers" as "no longer needs to be public" — but
+    // getPublicBooleanFlagServer resolves against the very same `GET /flags`
+    // endpoint the browser uses, and that route filters to listPublicFlagKeys()
+    // (routes/flags.ts:72-75). A non-public key is simply absent from the map,
+    // so the server helper would fall through to its default and return `false`
+    // FOREVER — the brand quietly reverting to Augmented for every org, with no
+    // error anywhere. `public` here means "readable through the public map",
+    // not "read by a browser".
+    //
+    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — the
+    // single reader evaluates inside the active-org cookie's scope, which is
+    // exactly the org whose brand should be shown.
     public: true
   },
   {

package/dist/mcp/slack-channel.js

@@ -33963,7 +33963,7 @@ var INTEGRATION_REGISTRY = [
     id: "firecrawl",
     name: "Firecrawl",
     category: "knowledge",
-    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account, or bring your own Firecrawl API key.",
+    description: "Web data for agents: scrape, map, crawl and search any website for clean structured data, plus scheduled change-detection monitors whose updates arrive in the agent's direct-chat. Connect via the platform-managed account.",
     // ENG-7217: Firecrawl migrates from a customer-API-key stdio MCP
     // (`npx firecrawl-mcp`, FIRECRAWL_API_KEY) to a PREMIUM, platform-managed
     // integration on the Deck / ElevenLabs model (ADR-0031, epic ENG-6920):
@@ -33974,16 +33974,30 @@ var INTEGRATION_REGISTRY = [
     // is metered at the one control-plane chokepoint and gated on a per-org opt-in
     // + monthly USD cap.
     //
-    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key` is
-    // now also offered so a customer can bring their OWN Firecrawl key. A BYO
+    // ENG-8304 / ADR-0055 (Phase 1b — Firecrawl is the BYO exemplar): `api_key`
+    // was also offered so a customer could bring their OWN Firecrawl key. A BYO
     // install (`credential_source='byo'`) authenticates with the customer's key
     // (stored encrypted on the install) and is NOT metered — its upstream cost is
-    // on the customer's own Firecrawl bill. BYO is gated on the plan-tier
-    // `byo_credentials` entitlement; managed stays the platform-key, billed path.
-    // `api_key` is the BYO option; the connect UI offers it via the toolkit's
-    // `auth_types` seed (Firecrawl surfaces through the premium list, not the
-    // native `installable` picker — that descriptor is for non-premium natives).
-    supported_auth_types: ["none", "api_key"],
+    // on the customer's own Firecrawl bill.
+    //
+    // ENG-9235: `api_key` is PARKED, not abandoned. BYO is gated on the plan-tier
+    // `byo_credentials` entitlement, which only `enterprise` has (the column is
+    // NOT NULL DEFAULT false, and ENG-9143 explicitly set it false for Team). The
+    // connect wizard never reads that flag, so offering `api_key` here sent every
+    // Team/Business customer to firecrawl.dev for a key we would then reject with
+    // a 403 `byo_not_entitled_by_plan` — after they had signed up for it.
+    //
+    // Removing it is also what removes that screen: the wizard's picker only
+    // renders for 2+ selectable auth types (`selectableWizardAuthMethods`), so a
+    // single `['none']` restores the friction-free managed install with no UI
+    // change. Restore `api_key` only together with an entitlement-aware wizard —
+    // see ENG-9236 for the proper fix.
+    //
+    // KEEP IN LOCKSTEP with the `firecrawl` row in
+    // packages/supabase/seeds/toolkit-definitions.json: that seed carries its own
+    // `auth_types` and is what `db:catalog:seed` upserts on every prod deploy, so
+    // editing this array alone changes nothing a customer can see.
+    supported_auth_types: ["none"],
     capabilities: [
       { id: "firecrawl:scrape", name: "Scrape Pages", description: "Fetch a single URL as clean markdown / structured data (firecrawl_scrape).", access: "write" },
       { id: "firecrawl:search", name: "Web Search", description: "Search the web and return ranked results, optionally scraped (firecrawl_search).", access: "write" },
@@ -36590,22 +36604,33 @@ var FLAG_REGISTRY = [
   },
   {
     key: "ninjafy-brand",
-    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: EVERY consumer evaluates in the active-org cookie scope \u2014 sidebar.tsx and top-nav.tsx via usePublicBooleanFlag, and (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 so a host- or agent-scoped row is accepted by the table but never reached by the console. The THEME is resolved SERVER-side deliberately (ENG-8858): the client hook starts at its default and updates after an async GET /flags, so gating a palette on it paints Augmented and repaints \u2014 a full-page colour flash, not just the wordmark flash it already causes. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
+    description: 'Present the product under the Ninjafy brand instead of Augmented Team (ENG-8250). This is the UMBRELLA brand gate, not a one-off nav toggle: every subsequent rebrand surface (page titles, email templates, marketing-facing copy) reads THIS key rather than adding its own flag, so the whole rebrand keeps a single kill switch. First surface is the left-hand nav wordmark \u2014 ON replaces the human+robot mark and the "augmented.team" text with italic lowercase "ninjafy"; OFF renders exactly what shipped before. Scope is the USER-FACING BRAND PRESENTATION \u2014 text AND VISUAL THEME. ENG-8858 widened this from text alone: the Ninjafy palette is gated here too, because a colour theme is not text. It stays ONE key rather than gaining a `ninjafy-theme` sibling, so a half-branded state \u2014 ninjafy wordmark over Augmented green \u2014 is unreachable and the rebrand keeps a single kill switch. It must never gate a code identifier, package name, env var or CLI name. EXISTING identifiers stay `Augmented`/`agt` per the CLAUDE.md naming contract, which protects them from premature renaming \u2014 the deep rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here. That contract does NOT require NEW code to carry the old brand: artefacts created specifically for the rebrand take Ninjafy naming (ENG-8078 decision 9; see the CLAUDE.md rebrand carve-out). Either way it is a naming rule, not a flag concern \u2014 this key gates presentation, never an identifier. Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot a subset while everyone else still sees Augmented. Overrides resolve at FOUR grains, most specific first \u2014 agent, team, host, then org-wide (evaluate.ts:79-81); organization_id is always required, so there is no global override. Org and team are the useful pilot grains for THIS flag: there is now exactly ONE consumer \u2014 (dashboard)/layout.tsx via getPublicBooleanFlagServer \u2014 evaluating in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. It resolves the key ONCE per request and passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop. Resolution is SERVER-side deliberately: the client hook starts at its default and updates after an async GET /flags, so anything gated on it paints Augmented and then repaints. ENG-8858 moved the PALETTE for that reason (a full-page colour flash); ENG-9227 moved the WORDMARK, which had been the last surface still swapping after hydration. A consequence worth knowing: /login and the marketing routes stay on the Augmented palette whatever an org sets, because getPublicBooleanFlagServer returns the default without a verified session and a pre-auth page has neither a session nor an active org \u2014 a PER-ORG flag structurally cannot brand one. Those surfaces follow only when the stage-wide default flips. Ships dark.',
     flagType: "boolean",
     // Declared safe value is `false`: the pre-rebrand brand. `false` is also the
     // fail-closed direction — if the flag DB is unreachable we must show the brand
     // that is currently live and contractually correct, never leak an unannounced
     // rebrand to every customer at once.
     defaultValue: false,
-    // Read on BOTH sides, so the key must be in the browser-exposed public map:
-    // sidebar.tsx and top-nav.tsx are "use client" and resolve it via
-    // usePublicBooleanFlag for the WORDMARK, while (dashboard)/layout.tsx resolves
-    // it server-side via getPublicBooleanFlagServer for the THEME (ENG-8858) — a
-    // palette cannot wait for an async client fetch without flashing. Dropping
-    // `public` would break the two client readers, not just the server one.
-    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — every
-    // reader evaluates inside the active-org cookie's scope, which is exactly the
-    // org whose brand should be shown.
+    // ENG-9227: there are NO client readers of this key left. (dashboard)/
+    // layout.tsx resolves it ONCE server-side via getPublicBooleanFlagServer and
+    // passes the boolean down to sidebar.tsx and top-nav.tsx as a required prop.
+    // ENG-8858 did that for the THEME; ENG-9227 finished the job for the
+    // WORDMARK, which had kept usePublicBooleanFlag and so kept swapping
+    // "augmented.team" to "ninjafy" after hydration.
+    //
+    // `public` MUST STAY ANYWAY, and this is the trap. It is tempting to read
+    // "no client readers" as "no longer needs to be public" — but
+    // getPublicBooleanFlagServer resolves against the very same `GET /flags`
+    // endpoint the browser uses, and that route filters to listPublicFlagKeys()
+    // (routes/flags.ts:72-75). A non-public key is simply absent from the map,
+    // so the server helper would fall through to its default and return `false`
+    // FOREVER — the brand quietly reverting to Augmented for every org, with no
+    // error anywhere. `public` here means "readable through the public map",
+    // not "read by a browser".
+    //
+    // Unlike onboarding-msteams-channel above there is no wrong-org hazard — the
+    // single reader evaluates inside the active-org cookie's scope, which is
+    // exactly the org whose brand should be shown.
     public: true
   },
   {