@integrity-labs/agt-cli 0.28.649 → 0.28.651

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

@@ -32209,6 +32209,9 @@ var TIER_PATTERNS = [
   }
 ];
 
+// ../core/dist/integrations/pending-approval.js
+var PENDING_APPROVAL_TTL_MS = 7 * 24 * 60 * 60 * 1e3;
+
 // ../core/dist/integrations/augmented-live/markup.js
 var MARKUP_MARKER = "__augmentedLiveMarkup";
 var MARKUP_CONTROL_MARKER = "__augmentedLiveMarkupControl";
@@ -36354,18 +36357,22 @@ 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 USER-FACING BRAND TEXT ONLY: 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 text, 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: its only consumer is sidebar.tsx via usePublicBooleanFlag, which evaluates in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. 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: 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.',
     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 CLIENT-SIDE: sidebar.tsx is a "use client" component and resolves this
-    // via usePublicBooleanFlag, so the key must be in the browser-exposed public
-    // map. Unlike onboarding-msteams-channel above there is no wrong-org hazard —
-    // the sidebar renders inside the active-org cookie's scope, which is exactly
-    // the org whose brand should be shown.
+    // 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.
     public: true
   },
   {

package/dist/mcp/index.js

@@ -39548,6 +39548,9 @@ var TIER_PATTERNS = [
   }
 ];
 
+// ../core/dist/integrations/pending-approval.js
+var PENDING_APPROVAL_TTL_MS = 7 * 24 * 60 * 60 * 1e3;
+
 // ../core/dist/integrations/augmented-live/markup.js
 var MARKUP_MARKER = "__augmentedLiveMarkup";
 var MARKUP_CONTROL_MARKER = "__augmentedLiveMarkupControl";
@@ -43244,18 +43247,22 @@ 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 USER-FACING BRAND TEXT ONLY: 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 text, 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: its only consumer is sidebar.tsx via usePublicBooleanFlag, which evaluates in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. 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: 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.',
     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 CLIENT-SIDE: sidebar.tsx is a "use client" component and resolves this
-    // via usePublicBooleanFlag, so the key must be in the browser-exposed public
-    // map. Unlike onboarding-msteams-channel above there is no wrong-org hazard —
-    // the sidebar renders inside the active-org cookie's scope, which is exactly
-    // the org whose brand should be shown.
+    // 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.
     public: true
   },
   {

package/dist/mcp/origami.js

@@ -38429,6 +38429,9 @@ var TIER_PATTERNS = [
   }
 ];
 
+// ../core/dist/integrations/pending-approval.js
+var PENDING_APPROVAL_TTL_MS = 7 * 24 * 60 * 60 * 1e3;
+
 // ../core/dist/integrations/augmented-live/markup.js
 var MARKUP_MARKER = "__augmentedLiveMarkup";
 var MARKUP_CONTROL_MARKER = "__augmentedLiveMarkupControl";
@@ -42104,18 +42107,22 @@ 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 USER-FACING BRAND TEXT ONLY: 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 text, 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: its only consumer is sidebar.tsx via usePublicBooleanFlag, which evaluates in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. 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: 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.',
     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 CLIENT-SIDE: sidebar.tsx is a "use client" component and resolves this
-    // via usePublicBooleanFlag, so the key must be in the browser-exposed public
-    // map. Unlike onboarding-msteams-channel above there is no wrong-org hazard —
-    // the sidebar renders inside the active-org cookie's scope, which is exactly
-    // the org whose brand should be shown.
+    // 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.
     public: true
   },
   {

package/dist/mcp/slack-channel.js

@@ -32489,6 +32489,9 @@ var TIER_PATTERNS = [
   }
 ];
 
+// ../core/dist/integrations/pending-approval.js
+var PENDING_APPROVAL_TTL_MS = 7 * 24 * 60 * 60 * 1e3;
+
 // ../core/dist/integrations/augmented-live/markup.js
 var MARKUP_MARKER = "__augmentedLiveMarkup";
 var MARKUP_CONTROL_MARKER = "__augmentedLiveMarkupControl";
@@ -36587,18 +36590,22 @@ 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 USER-FACING BRAND TEXT ONLY: 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 text, 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: its only consumer is sidebar.tsx via usePublicBooleanFlag, which evaluates in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. 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: 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.',
     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 CLIENT-SIDE: sidebar.tsx is a "use client" component and resolves this
-    // via usePublicBooleanFlag, so the key must be in the browser-exposed public
-    // map. Unlike onboarding-msteams-channel above there is no wrong-org hazard —
-    // the sidebar renders inside the active-org cookie's scope, which is exactly
-    // the org whose brand should be shown.
+    // 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.
     public: true
   },
   {

package/dist/mcp/telegram-channel.js

@@ -32639,6 +32639,9 @@ var TIER_PATTERNS = [
   }
 ];
 
+// ../core/dist/integrations/pending-approval.js
+var PENDING_APPROVAL_TTL_MS = 7 * 24 * 60 * 60 * 1e3;
+
 // ../core/dist/integrations/augmented-live/markup.js
 var MARKUP_MARKER = "__augmentedLiveMarkup";
 var MARKUP_CONTROL_MARKER = "__augmentedLiveMarkupControl";
@@ -36731,18 +36734,22 @@ 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 USER-FACING BRAND TEXT ONLY: 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 text, 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: its only consumer is sidebar.tsx via usePublicBooleanFlag, which evaluates in the active-org cookie scope, so a host- or agent-scoped row is accepted by the table but never reached by the console. 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: 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.',
     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 CLIENT-SIDE: sidebar.tsx is a "use client" component and resolves this
-    // via usePublicBooleanFlag, so the key must be in the browser-exposed public
-    // map. Unlike onboarding-msteams-channel above there is no wrong-org hazard —
-    // the sidebar renders inside the active-org cookie's scope, which is exactly
-    // the org whose brand should be shown.
+    // 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.
     public: true
   },
   {

package/dist/{persistent-session-TE6CKC5R.js → persistent-session-DVZESZDD.js}

@@ -43,8 +43,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-UTNGCJLO.js";
-import "./chunk-WP6LYCRS.js";
+} from "./chunk-EUXCRRZU.js";
+import "./chunk-V5MUX3GI.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -92,4 +92,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-TE6CKC5R.js.map
+//# sourceMappingURL=persistent-session-DVZESZDD.js.map

package/dist/{responsiveness-probe-BQNVH63L.js → responsiveness-probe-Q7SVASQS.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-UTNGCJLO.js";
-import "./chunk-WP6LYCRS.js";
+} from "./chunk-EUXCRRZU.js";
+import "./chunk-V5MUX3GI.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -727,4 +727,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-BQNVH63L.js.map
+//# sourceMappingURL=responsiveness-probe-Q7SVASQS.js.map

package/dist/{session-auth-dead-SZXCIJ4S.js → session-auth-dead-RV3Z64TM.js}

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

package/package.json

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