@integrity-labs/agt-cli 0.28.457 → 0.28.459

package/dist/mcp/origami.js

@@ -39886,6 +39886,16 @@ var UNKNOWN_RATE_LIMIT = Object.freeze({
   text: null
 });
 
+// ../core/dist/claude-code-usage/turn-failure-classifier.js
+var UNKNOWN_TURN_FAILURE = Object.freeze({
+  outcome: "unknown",
+  atMs: null,
+  failureClass: null,
+  httpStatus: null,
+  attempt: null,
+  maxAttempts: null
+});
+
 // ../core/dist/kanban/state-machine.js
 var KANBAN_STATUSES = [
   "backlog",
@@ -40712,7 +40722,7 @@ var FLAG_REGISTRY = [
   },
   {
     key: "wedge-transient-notice",
-    description: 'When a wedge-respawn was preceded by a transient LLM-API error (529/429/503/500 that exhausted its retries and wedged the turn), the manager writes the ENG-6058 give-up signal tagged reason=transient_overload so the channel sweeps post a friendly "I hit a brief overload \u2014 please resend" notice instead of leaving the user in silence (ENG-7360, extends ENG-6861 to the retry-exhaustion + wedge path). Boolean gate; ships dark \u2014 channel-visible copy soaks per host before going wide.',
+    description: `Tell the person waiting when their turn dies on a transient LLM-API failure (529 overloaded / 5xx). TWO consumers now share this gate. (1) ENG-7360: a wedge-respawn preceded by such an error writes the ENG-6058 give-up signal tagged reason=transient_overload so the channel sweeps post a "please resend" notice. (2) ENG-8269: the channel MCPs watch the dispatched turn in Claude Code's own transcript and notify the conversation that was actually waiting \u2014 Slack, Telegram AND direct chat \u2014 plus a "still working on this" notice after ~3min on Slack/Telegram only (direct chat already shows a client-side one at 90s). NOTE: (2) fires on a MUCH larger population than (1) \u2014 any dispatched turn that dies, not only one that also wedged the session \u2014 and (1) has never actually been able to fire, because its pane.log detector cannot match the banner Claude Code renders today. So flipping this on is in practice enabling (2) for the first time. Boolean gate; ships dark \u2014 channel-visible copy soaks per host before going wide. Materialized into the channel-MCP spawn env: a Docker-isolated agent never mounts the host flags-cache, so a central flip reaches it only that way.`,
     flagType: "boolean",
     defaultValue: false,
     envVar: "AGT_WEDGE_TRANSIENT_NOTICE_ENABLED"
@@ -41206,6 +41216,22 @@ var FLAG_REGISTRY = [
     // registry-only (ADR-0022). NOT `public`: it is resolved server-side only, so it
     // must never be serialized into the browser map.
     defaultValue: false
+  },
+  {
+    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, which stay `Augmented`/`agt` per the CLAUDE.md naming contract (the deep code rename is workstream C of docs/runbooks/rebrand-ninjafy-migration.md and is out of scope here). Set the stage-wide default to flip a whole environment, or add a feature_flag_overrides row to pilot one organization while every other org still sees Augmented. 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.
+    public: true
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));