@integrity-labs/agt-cli 0.28.890 → 0.28.891

package/dist/mcp/origami.js

@@ -43707,14 +43707,38 @@ var FLAG_REGISTRY = [
   },
   {
     key: "agent-unified-screen",
-    description: 'Unified agent screen redesign (ENG-8478 epic / ENG-8480). When ON, the webapp renders the new single-screen "viewing is editing" agent surface (stripped-back hero, working agent switcher, inline-editable profile, embedded operational panels + a live direct-chat drawer) in place of the separate agent view/edit pages; when OFF, the current view/edit pages are unchanged. Additive UI gate \u2014 no data-model change: each panel reads the same existing endpoints the current pages use. Composes independently with app-top-nav-shell (the two flags are reconciled in ENG-8488). Ships dark.',
+    description: 'Unified agent screen redesign (ENG-8478 epic / ENG-8480). When ON, the webapp renders the new single-screen "viewing is editing" agent surface (stripped-back hero, working agent switcher, inline-editable profile, embedded operational panels + a live direct-chat drawer) in place of the separate agent view/edit pages; when OFF, the current view/edit pages are unchanged. Additive UI gate \u2014 no data-model change: each panel reads the same existing endpoints the current pages use. Composes independently with app-top-nav-shell (the two flags are reconciled in ENG-8488). NO LONGER DARK: ENG-9832 cutover step 1 flipped the default to true, so an org with no override now gets the unified screen. The key survives only until cutover step 2 deletes it \u2014 which is blocked on ENG-8547 and ENG-8559, because the flag-off branch is still the only home for the /edit tabs.',
     flagType: "boolean",
-    // Declared safe value is `false` = the current view/edit pages. A flag-DB read
-    // error must fall back to what ships today, never a half-built redesign.
-    defaultValue: false,
-    // Read CLIENT-SIDE by the agent screen ("use client") via usePublicBooleanFlag,
-    // so the key must be in the browser-exposed public map. Additive viewer gate,
-    // resolved within the active-org cookie's scope — not sensitive.
+    // ENG-9832 (cutover step 1): flipped `false` -> `true`. The comment this
+    // replaces called `false` the safe direction — "the current view/edit
+    // pages", never "a half-built redesign". That was true while the redesign
+    // was half built. It has been the shipped surface for the pilot orgs since
+    // ENG-8481, so `false` now points at the pages being retired, not at safety.
+    // The old rationale is recorded rather than deleted because it was correct
+    // under a premise that has since expired.
+    //
+    // MIND THE SPLIT. This value is consulted by the API evaluator when it
+    // builds the `GET /flags` map for an org with NO override. It is NOT the
+    // fallback the webapp uses when that fetch fails: `getPublicBooleanFlagServer`
+    // and `usePublicBooleanFlag` both return the argument passed at the CALL
+    // SITE and never consult this registry. Three call sites carry `true` to
+    // match — agents/[agentId]/page.tsx, agents/[agentId]/edit/page.tsx and
+    // `useAgentUnifiedScreenEnabled` in lib/redesign-flags.ts. Flipping the
+    // registry alone leaves the cutover half-applied with no error anywhere;
+    // eng-9832-unified-fallback-parity.test.ts fails if any of the three drifts.
+    defaultValue: true,
+    // Read BOTH server-side (agents/[agentId]/page.tsx and its /edit sibling, via
+    // getPublicBooleanFlagServer) and client-side (dashboard-sherlock-shell.tsx,
+    // via usePublicBooleanFlag), so the key must be in the browser-exposed public
+    // map. Additive viewer gate, resolved within the active-org cookie's scope
+    // — not sensitive.
+    //
+    // `public` MUST STAY until step 2 deletes the key, and the reason reads
+    // backwards: the server helper resolves against the very SAME public-filtered
+    // `GET /flags` the browser uses (routes/flags.ts filters to
+    // listPublicFlagKeys()). Drop `public` and the key is simply absent from the
+    // map, so both server readers fall through to their call-site argument
+    // forever — silently, with no error raised anywhere.
     public: true
   },
   {

package/dist/mcp/slack-channel.js

@@ -38344,14 +38344,38 @@ var FLAG_REGISTRY = [
   },
   {
     key: "agent-unified-screen",
-    description: 'Unified agent screen redesign (ENG-8478 epic / ENG-8480). When ON, the webapp renders the new single-screen "viewing is editing" agent surface (stripped-back hero, working agent switcher, inline-editable profile, embedded operational panels + a live direct-chat drawer) in place of the separate agent view/edit pages; when OFF, the current view/edit pages are unchanged. Additive UI gate \u2014 no data-model change: each panel reads the same existing endpoints the current pages use. Composes independently with app-top-nav-shell (the two flags are reconciled in ENG-8488). Ships dark.',
+    description: 'Unified agent screen redesign (ENG-8478 epic / ENG-8480). When ON, the webapp renders the new single-screen "viewing is editing" agent surface (stripped-back hero, working agent switcher, inline-editable profile, embedded operational panels + a live direct-chat drawer) in place of the separate agent view/edit pages; when OFF, the current view/edit pages are unchanged. Additive UI gate \u2014 no data-model change: each panel reads the same existing endpoints the current pages use. Composes independently with app-top-nav-shell (the two flags are reconciled in ENG-8488). NO LONGER DARK: ENG-9832 cutover step 1 flipped the default to true, so an org with no override now gets the unified screen. The key survives only until cutover step 2 deletes it \u2014 which is blocked on ENG-8547 and ENG-8559, because the flag-off branch is still the only home for the /edit tabs.',
     flagType: "boolean",
-    // Declared safe value is `false` = the current view/edit pages. A flag-DB read
-    // error must fall back to what ships today, never a half-built redesign.
-    defaultValue: false,
-    // Read CLIENT-SIDE by the agent screen ("use client") via usePublicBooleanFlag,
-    // so the key must be in the browser-exposed public map. Additive viewer gate,
-    // resolved within the active-org cookie's scope — not sensitive.
+    // ENG-9832 (cutover step 1): flipped `false` -> `true`. The comment this
+    // replaces called `false` the safe direction — "the current view/edit
+    // pages", never "a half-built redesign". That was true while the redesign
+    // was half built. It has been the shipped surface for the pilot orgs since
+    // ENG-8481, so `false` now points at the pages being retired, not at safety.
+    // The old rationale is recorded rather than deleted because it was correct
+    // under a premise that has since expired.
+    //
+    // MIND THE SPLIT. This value is consulted by the API evaluator when it
+    // builds the `GET /flags` map for an org with NO override. It is NOT the
+    // fallback the webapp uses when that fetch fails: `getPublicBooleanFlagServer`
+    // and `usePublicBooleanFlag` both return the argument passed at the CALL
+    // SITE and never consult this registry. Three call sites carry `true` to
+    // match — agents/[agentId]/page.tsx, agents/[agentId]/edit/page.tsx and
+    // `useAgentUnifiedScreenEnabled` in lib/redesign-flags.ts. Flipping the
+    // registry alone leaves the cutover half-applied with no error anywhere;
+    // eng-9832-unified-fallback-parity.test.ts fails if any of the three drifts.
+    defaultValue: true,
+    // Read BOTH server-side (agents/[agentId]/page.tsx and its /edit sibling, via
+    // getPublicBooleanFlagServer) and client-side (dashboard-sherlock-shell.tsx,
+    // via usePublicBooleanFlag), so the key must be in the browser-exposed public
+    // map. Additive viewer gate, resolved within the active-org cookie's scope
+    // — not sensitive.
+    //
+    // `public` MUST STAY until step 2 deletes the key, and the reason reads
+    // backwards: the server helper resolves against the very SAME public-filtered
+    // `GET /flags` the browser uses (routes/flags.ts filters to
+    // listPublicFlagKeys()). Drop `public` and the key is simply absent from the
+    // map, so both server readers fall through to their call-site argument
+    // forever — silently, with no error raised anywhere.
     public: true
   },
   {

package/dist/mcp/telegram-channel.js

@@ -38394,14 +38394,38 @@ var FLAG_REGISTRY = [
   },
   {
     key: "agent-unified-screen",
-    description: 'Unified agent screen redesign (ENG-8478 epic / ENG-8480). When ON, the webapp renders the new single-screen "viewing is editing" agent surface (stripped-back hero, working agent switcher, inline-editable profile, embedded operational panels + a live direct-chat drawer) in place of the separate agent view/edit pages; when OFF, the current view/edit pages are unchanged. Additive UI gate \u2014 no data-model change: each panel reads the same existing endpoints the current pages use. Composes independently with app-top-nav-shell (the two flags are reconciled in ENG-8488). Ships dark.',
+    description: 'Unified agent screen redesign (ENG-8478 epic / ENG-8480). When ON, the webapp renders the new single-screen "viewing is editing" agent surface (stripped-back hero, working agent switcher, inline-editable profile, embedded operational panels + a live direct-chat drawer) in place of the separate agent view/edit pages; when OFF, the current view/edit pages are unchanged. Additive UI gate \u2014 no data-model change: each panel reads the same existing endpoints the current pages use. Composes independently with app-top-nav-shell (the two flags are reconciled in ENG-8488). NO LONGER DARK: ENG-9832 cutover step 1 flipped the default to true, so an org with no override now gets the unified screen. The key survives only until cutover step 2 deletes it \u2014 which is blocked on ENG-8547 and ENG-8559, because the flag-off branch is still the only home for the /edit tabs.',
     flagType: "boolean",
-    // Declared safe value is `false` = the current view/edit pages. A flag-DB read
-    // error must fall back to what ships today, never a half-built redesign.
-    defaultValue: false,
-    // Read CLIENT-SIDE by the agent screen ("use client") via usePublicBooleanFlag,
-    // so the key must be in the browser-exposed public map. Additive viewer gate,
-    // resolved within the active-org cookie's scope — not sensitive.
+    // ENG-9832 (cutover step 1): flipped `false` -> `true`. The comment this
+    // replaces called `false` the safe direction — "the current view/edit
+    // pages", never "a half-built redesign". That was true while the redesign
+    // was half built. It has been the shipped surface for the pilot orgs since
+    // ENG-8481, so `false` now points at the pages being retired, not at safety.
+    // The old rationale is recorded rather than deleted because it was correct
+    // under a premise that has since expired.
+    //
+    // MIND THE SPLIT. This value is consulted by the API evaluator when it
+    // builds the `GET /flags` map for an org with NO override. It is NOT the
+    // fallback the webapp uses when that fetch fails: `getPublicBooleanFlagServer`
+    // and `usePublicBooleanFlag` both return the argument passed at the CALL
+    // SITE and never consult this registry. Three call sites carry `true` to
+    // match — agents/[agentId]/page.tsx, agents/[agentId]/edit/page.tsx and
+    // `useAgentUnifiedScreenEnabled` in lib/redesign-flags.ts. Flipping the
+    // registry alone leaves the cutover half-applied with no error anywhere;
+    // eng-9832-unified-fallback-parity.test.ts fails if any of the three drifts.
+    defaultValue: true,
+    // Read BOTH server-side (agents/[agentId]/page.tsx and its /edit sibling, via
+    // getPublicBooleanFlagServer) and client-side (dashboard-sherlock-shell.tsx,
+    // via usePublicBooleanFlag), so the key must be in the browser-exposed public
+    // map. Additive viewer gate, resolved within the active-org cookie's scope
+    // — not sensitive.
+    //
+    // `public` MUST STAY until step 2 deletes the key, and the reason reads
+    // backwards: the server helper resolves against the very SAME public-filtered
+    // `GET /flags` the browser uses (routes/flags.ts filters to
+    // listPublicFlagKeys()). Drop `public` and the key is simply absent from the
+    // map, so both server readers fall through to their call-site argument
+    // forever — silently, with no error raised anywhere.
     public: true
   },
   {

package/dist/{persistent-session-DVG5WKZZ.js → persistent-session-ZDZSEODJ.js}

@@ -62,8 +62,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-AQM4A5JF.js";
-import "./chunk-FHJLOWU2.js";
+} from "./chunk-SXYTFXPO.js";
+import "./chunk-BH5RFBUM.js";
 import "./chunk-XWVM4KPK.js";
 export {
   CLAUDE_HOST_WIDE,
@@ -130,4 +130,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-DVG5WKZZ.js.map
+//# sourceMappingURL=persistent-session-ZDZSEODJ.js.map

package/dist/{responsiveness-probe-PPI3AFQG.js → responsiveness-probe-7CY5VZMG.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-AQM4A5JF.js";
-import "./chunk-FHJLOWU2.js";
+} from "./chunk-SXYTFXPO.js";
+import "./chunk-BH5RFBUM.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -764,4 +764,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-PPI3AFQG.js.map
+//# sourceMappingURL=responsiveness-probe-7CY5VZMG.js.map

package/dist/{session-auth-dead-L7TAICNC.js → session-auth-dead-65TG2DLW.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-FHJLOWU2.js";
+} from "./chunk-BH5RFBUM.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-L7TAICNC.js.map
+//# sourceMappingURL=session-auth-dead-65TG2DLW.js.map

package/package.json

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