@cat-factory/app 0.241.0 → 0.241.2

package/README.md

@@ -618,7 +618,17 @@ event left to restore it.
 - **Never gate readiness on a snapshot a later resync can undo.** The on-connect resync flips
   `connected` only after it settles (which is why e2e gates on `data-connected`).
 - **A REPLACE-style `hydrate` must never silently drop live-only state.** Either fold that state
-  into the snapshot or reconcile rather than replace.
+  into the snapshot or reconcile rather than replace. The `refreshSeq` guard above orders
+  refreshes against each OTHER and does nothing when ONE slow fetch straddles a live event, so
+  every such store also takes a WATERMARK: `refresh()` captures each one's `hydrateBaseline()`
+  before the fetch (`LiveWriteBaselines`) and its `hydrate` keeps whatever was written after it.
+  `board` and `notifications` are the two today; `execution` gets the same protection from the
+  server `rev` it carries. Whether the store can re-derive the dropped state is what decides how
+  bad the bug is: a block's status arrives again on the run's next transition, while a
+  notification is pushed ONCE, so dropping the card leaves a parked run nothing can surface (the
+  `pr-review` spec's flaky 30s wait on `notifications-bell`). A watermark that tracks only
+  INSERTS is half a guard: a card resolved live must also stay gone, or a snapshot read while it
+  was open resurrects an action the server has already taken.
 - **An action's OPTIMISTIC ECHO is a clobber too, and it bypasses both guards above.** A store
   that awaits a mutation and then assigns the returned sub-state onto the cached run
   (`step.forkDecision`, `step.prReview`, `step.judge`, `step.followUps`) is writing straight past

package/app/components/panels/StepToolServers.logic.ts

@@ -37,6 +37,14 @@ export const REASON_KEY: Record<ToolServerUnavailableReason, string> = {
  * (`docs`' table in `backend/docs/mcp-tool-servers.md` is the same mapping for a reader who never
  * opens the SPA); a reason with no remedy leaves the operator holding an accurate diagnosis and no
  * next step, which is the state this surface was built to end.
+ *
+ * EDITING ONE OF THESE MEANS READING EVERY CAUSE IT COVERS FIRST. A member is not a cause:
+ * `harness_unsupported`, `missing_secret` and `oauth_not_connected` are each reached from more
+ * than one place, and a line addressing only the obvious one is a dead end for whoever hit the
+ * other, which is worse than the bare diagnosis this replaced because it also costs them the
+ * attempt. The causes per member are enumerated on kernel's `UnavailableToolServer` (which the SPA
+ * cannot import) and restated in that doc's table, whose "What happened" column is the list to
+ * check a remedy against.
  */
 export const REMEDY_KEY: Record<ToolServerUnavailableReason, string> = {
   harness_unsupported: 'panels.stepDetail.toolServers.remedy.harnessUnsupported',

package/app/stores/notifications.ts

@@ -22,11 +22,42 @@ export const useNotificationsStore = defineStore('notifications', () => {
     remove,
   } = useUpsertList<Notification>({ key: (n) => n.id, prepend: true })
 
-  /** Replace the cache from a server snapshot. */
-  function hydrate(notifications: Notification[]) {
-    open.value = [...notifications]
-      .filter((n) => n.status === 'open')
-      .sort((a, b) => b.createdAt - a.createdAt)
+  // Client-side monotonic guard against a stale full-snapshot `hydrate` CLOBBERING newer live
+  // state — the same hazard `useBoardStore` guards, on the delivery shape that has no second
+  // chance. A run raises its card as a targeted `notification` event; a full `refresh()` whose
+  // snapshot was READ before that card existed can resolve AFTER it, and a plain replace then
+  // drops the card with NO further event to restore it, so the inbox bell never appears (the
+  // pr-review e2e flake). Notifications carry no server revision, so each live write is stamped
+  // with a monotonic sequence and a refresh that captured its baseline BEFORE the fetch keeps
+  // every write newer than that baseline. It cuts both ways: a live-ADDED card the snapshot
+  // cannot know about is re-inserted, and a live-RESOLVED one the snapshot still calls open
+  // stays gone.
+  let liveSeq = 0
+  /** Last live write per id: the notification to keep, or `null` once it was resolved. */
+  const liveWrites = new Map<string, { seq: number; value: Notification | null }>()
+
+  /**
+   * Baseline for {@link hydrate}: capture this BEFORE a refresh's snapshot fetch and pass it
+   * back in, so a notification written live while the fetch was in flight survives the hydrate.
+   * Callers that don't pass a baseline get a plain full replace (initial load / board switch —
+   * no live-write race to guard).
+   */
+  function hydrateBaseline(): number {
+    return liveSeq
+  }
+
+  /** Replace the cache from a server snapshot, keeping live writes newer than `since`. */
+  function hydrate(notifications: Notification[], since = liveSeq) {
+    const newer = new Map<string, Notification | null>()
+    for (const [id, write] of liveWrites) {
+      // A write the snapshot already reflects is reconciled and can be forgotten, so the map
+      // stays bounded by what is genuinely in flight rather than by the session's history.
+      if (write.seq > since) newer.set(id, write.value)
+      else liveWrites.delete(id)
+    }
+    const merged = notifications.filter((n) => n.status === 'open' && !newer.has(n.id))
+    for (const value of newer.values()) if (value) merged.push(value)
+    open.value = merged.sort((a, b) => b.createdAt - a.createdAt)
   }
 
   /**
@@ -34,7 +65,9 @@ export const useNotificationsStore = defineStore('notifications', () => {
    * replaced in place; a resolved one (acted/dismissed) is removed from the inbox.
    */
   function upsert(notification: Notification) {
-    if (notification.status !== 'open') {
+    const isOpen = notification.status === 'open'
+    liveWrites.set(notification.id, { seq: ++liveSeq, value: isOpen ? notification : null })
+    if (!isOpen) {
       remove(notification.id)
       return
     }
@@ -76,5 +109,5 @@ export const useNotificationsStore = defineStore('notifications', () => {
     upsert(resolved)
   }
 
-  return { open, hydrate, upsert, byBlock, count, act, dismiss }
+  return { open, hydrate, hydrateBaseline, upsert, byBlock, count, act, dismiss }
 })

package/app/stores/workspace/commands.ts

@@ -13,7 +13,7 @@ export interface WorkspaceCommandContext {
   api: ReturnType<typeof useApi>
   workspaceId: Ref<string | null>
   workspaces: Ref<WorkspaceListItem[]>
-  hydrate: (snapshot: WorkspaceSnapshot, boardSince?: number) => void
+  hydrate: (snapshot: WorkspaceSnapshot) => void
   /** Open one of the active account's boards, creating one when it has none. */
   resolveActiveBoard: () => Promise<void>
 }

package/app/stores/workspace/hydrate.ts

@@ -49,23 +49,28 @@ export function resetPerBoardCaches() {
   useFragmentsStore().invalidate()
 }
 
+/**
+ * The live-write watermarks a refresh captured BEFORE its snapshot fetch, one per store whose
+ * `hydrate` REPLACES a list that live events also write to. Each store preserves whatever it
+ * was handed after its own baseline, so a slower refresh can't clobber newer live state (see
+ * `useBoardStore().hydrate` and `useNotificationsStore().hydrate`). Omitted by fresh loads
+ * (init / board switch / create), where there is no in-flight race to guard.
+ */
+export type LiveWriteBaselines = { board: number; notifications: number }
+
 /**
  * Fan a workspace snapshot out into the per-feature data stores. Extracted verbatim from the
  * `workspace` store's `hydrate` (which keeps the workspace-scoped state it owns + the
  * board-switch cache reset) so the ordering of the hydrate calls is preserved exactly — a
  * size-only split, not a new seam.
- *
- * `boardSince` (captured BEFORE this snapshot's fetch) lets the board store preserve any block
- * live-`upsert`ed while the fetch was in flight, so a slower refresh can't clobber a newer live
- * status (see `useBoardStore().hydrate`).
  */
-export function applySnapshotToStores(snapshot: WorkspaceSnapshot, boardSince?: number) {
+export function applySnapshotToStores(snapshot: WorkspaceSnapshot, baselines?: LiveWriteBaselines) {
   useUserSettingsStore().hydrate(snapshot.userSettings ?? null)
   // The signed-in user's tutorial progress MERGES rather than replaces (see the store): both id
   // lists are grow-only sets, so a snapshot must never un-say a walkthrough this browser finished
   // while the mirror write was failing. Absent ⇒ no server copy, and the local one stands.
   useTutorialStore().mergeServerProgress(snapshot.tutorialProgress ?? null)
-  useBoardStore().hydrate(snapshot.blocks, boardSince)
+  useBoardStore().hydrate(snapshot.blocks, baselines?.board)
   useBoardStore().hydrateArchived(snapshot.archivedServices ?? [])
   usePipelinesStore().hydrate(
     snapshot.pipelines,
@@ -77,7 +82,7 @@ export function applySnapshotToStores(snapshot: WorkspaceSnapshot, boardSince?:
   useAgentRunsStore().hydrate(snapshot.bootstrapJobs ?? [], snapshot.workspace.id)
   useAgentRunsStore().hydrateEnvConfigRepair(snapshot.envConfigRepairJobs ?? [])
   useEnvironmentTestStore().hydrate(snapshot.environmentTestRuns ?? [], snapshot.workspace.id)
-  useNotificationsStore().hydrate(snapshot.notifications ?? [])
+  useNotificationsStore().hydrate(snapshot.notifications ?? [], baselines?.notifications)
   useRiskPoliciesStore().hydrate(snapshot.riskPolicies ?? [], snapshot.riskPolicyCatalogVersions)
   useSharedStacksStore().hydrate(snapshot.sharedStacks ?? [])
   useWorkspaceSettingsStore().hydrate(snapshot.settings)

package/app/stores/workspace.spec.ts

@@ -1,11 +1,14 @@
 import { beforeEach, describe, expect, it, vi } from 'vitest'
-import type { Block, WorkspaceSnapshot } from '~/types/domain'
+import type { Block, Notification, WorkspaceSnapshot } from '~/types/domain'
 import { useBoardStore } from '~/stores/board'
+import { useNotificationsStore } from '~/stores/notifications'
 import { useWorkspaceStore } from '~/stores/workspace'
 
 // The workspace store's `hydrate` fans out to ~20 sibling stores via Nuxt auto-imports, which
 // aren't defined under plain vitest. Stub every one INERT (a proxy whose every method is a no-op)
-// EXCEPT the board store, which we keep real so the block list a refresh commits is observable.
+// EXCEPT the two stores whose live-write guards these tests drive: the board store (kept real via
+// the stub below) and the notifications store (imported by name in `workspace/hydrate.ts`, so it
+// is real already and must NOT be listed here).
 const INERT_STORES = [
   'useAccountsStore',
   'useAgentConfigStore',
@@ -22,7 +25,6 @@ const INERT_STORES = [
   'useInitiativesStore',
   'useRiskPoliciesStore',
   'useModelPresetsStore',
-  'useNotificationsStore',
   'usePipelinesStore',
   'useProviderConnectionsStore',
   'useRecurringPipelinesStore',
@@ -68,13 +70,34 @@ function block(id: string, over: Partial<Block> = {}): Block {
   }
 }
 
+/** Minimal open inbox card — only the fields the notifications store reads. */
+function notification(id: string, over: Partial<Notification> = {}): Notification {
+  return {
+    id,
+    type: 'pr_review_ready',
+    status: 'open',
+    blockId: 't1',
+    executionId: null,
+    title: id,
+    body: '',
+    createdAt: 1,
+    resolvedAt: null,
+    ...over,
+  }
+}
+
 /** Minimal snapshot — the arrays a bare hydrate iterates; everything else defaults. */
-function snapshot(id: string, blocks: Block[]): WorkspaceSnapshot {
+function snapshot(
+  id: string,
+  blocks: Block[],
+  notifications: Notification[] = [],
+): WorkspaceSnapshot {
   return {
     workspace: { id, name: id, accountId: null },
     blocks,
     pipelines: [],
     executions: [],
+    notifications,
   } as unknown as WorkspaceSnapshot
 }
 
@@ -149,6 +172,70 @@ describe('workspace store refresh ordering', () => {
     // The live terminal status survives — the stale refresh did NOT clobber it back.
     expect(board.getBlock('t1')?.status).toBe('done')
   })
+
+  // The same interleaved-live-write axis on the delivery shape with NO second chance. A parked
+  // run raises its inbox card as a targeted `notification` event and never re-sends it, while the
+  // park ALSO fans out coarse `board` events whose debounced refresh is routinely in flight at
+  // that moment. A snapshot READ before the card existed used to replace the whole inbox and drop
+  // it, so the bell never appeared and nothing could bring it back — the `pr-review` e2e spec's
+  // 30s timeout on `notifications-bell`. The notifications store now stamps each live write and
+  // `refresh()` captures its baseline beside the board's.
+  it('a refresh started before a live notification does not drop the raised card', async () => {
+    const frame = block('f1')
+    let resolveRefresh!: (s: WorkspaceSnapshot) => void
+    const getWorkspace = vi
+      .fn()
+      // 1) switchTo — nothing in the inbox yet.
+      .mockResolvedValueOnce(snapshot('ws1', [frame]))
+      // 2) a refresh whose fetch is in flight while the run parks and raises its card.
+      .mockReturnValueOnce(new Promise<WorkspaceSnapshot>((r) => (resolveRefresh = r)))
+    vi.stubGlobal('useApi', () => ({ getWorkspace }))
+
+    const ws = useWorkspaceStore()
+    const notifications = useNotificationsStore()
+    await ws.switchTo('ws1')
+
+    // A refresh starts (captures the notifications baseline; its snapshot has an empty inbox).
+    const pass = ws.refresh()
+    // The run parks mid-fetch and pushes its card.
+    notifications.upsert(notification('n1'))
+    expect(notifications.count).toBe(1)
+    // The now-stale refresh resolves, still carrying the empty inbox it read.
+    resolveRefresh(snapshot('ws1', [frame]))
+    await pass
+
+    // The card survives: it is the only delivery there will ever be.
+    expect(notifications.count).toBe(1)
+  })
+
+  // The mirror image, and the reason the guard tracks REMOVALS too: a card resolved live (acted
+  // on in another tab, or cleared by the engine) must not be resurrected by a snapshot that was
+  // read while it was still open — a resurrected card offers an action the server has already
+  // taken.
+  it('a refresh started before a live resolve does not resurrect the card', async () => {
+    const frame = block('f1')
+    let resolveRefresh!: (s: WorkspaceSnapshot) => void
+    const getWorkspace = vi
+      .fn()
+      // 1) switchTo — the card is open.
+      .mockResolvedValueOnce(snapshot('ws1', [frame], [notification('n1')]))
+      // 2) a refresh whose fetch is in flight while the card is resolved elsewhere.
+      .mockReturnValueOnce(new Promise<WorkspaceSnapshot>((r) => (resolveRefresh = r)))
+    vi.stubGlobal('useApi', () => ({ getWorkspace }))
+
+    const ws = useWorkspaceStore()
+    const notifications = useNotificationsStore()
+    await ws.switchTo('ws1')
+    expect(notifications.count).toBe(1)
+
+    const pass = ws.refresh()
+    notifications.upsert(notification('n1', { status: 'acted', resolvedAt: 2 }))
+    expect(notifications.count).toBe(0)
+    resolveRefresh(snapshot('ws1', [frame], [notification('n1')]))
+    await pass
+
+    expect(notifications.count).toBe(0)
+  })
 })
 
 // Cold-open waterfall flattening (app-startup initiative, item 8): `init()` fetches the persisted

package/app/stores/workspace.ts

@@ -9,6 +9,8 @@ import type {
 } from '~/types/domain'
 import { useAccountsStore } from '~/stores/accounts'
 import { useBoardStore } from '~/stores/board'
+import { useNotificationsStore } from '~/stores/notifications'
+import type { LiveWriteBaselines } from '~/stores/workspace/hydrate'
 import { applySnapshotToStores, resetPerBoardCaches } from '~/stores/workspace/hydrate'
 import { createWorkspaceCommands } from '~/stores/workspace/commands'
 import { createInfraSetupState } from '~/stores/workspace/infraSetup'
@@ -81,12 +83,12 @@ export const useWorkspaceStore = defineStore(
     )
 
     /**
-     * Push a snapshot into the data stores. `boardSince` (captured BEFORE this snapshot's fetch)
-     * lets the board store preserve any block live-`upsert`ed while the fetch was in flight, so a
-     * slower refresh can't clobber a newer live status (see `useBoardStore().hydrate`). Omitted by
-     * fresh loads (init/switch/create), where there is no in-flight-upsert race to guard.
+     * Push a snapshot into the data stores. `baselines` (captured BEFORE this snapshot's fetch)
+     * lets the replace-style stores preserve anything written live while the fetch was in flight,
+     * so a slower refresh can't clobber newer live state (see {@link LiveWriteBaselines}). Omitted
+     * by fresh loads (init/switch/create), where there is no in-flight race to guard.
      */
-    function hydrate(snapshot: WorkspaceSnapshot, boardSince?: number) {
+    function hydrate(snapshot: WorkspaceSnapshot, baselines?: LiveWriteBaselines) {
       // A change of active board (or the first load) drops the per-block caches that are NOT
       // part of the snapshot; a same-board refresh keeps them (see `resetPerBoardCaches`).
       if (workspaceId.value !== snapshot.workspace.id) resetPerBoardCaches()
@@ -107,7 +109,7 @@ export const useWorkspaceStore = defineStore(
         workspaces.value.unshift(snapshot.workspace)
       }
       // Fan the rest of the snapshot out into the per-feature data stores.
-      applySnapshotToStores(snapshot, boardSince)
+      applySnapshotToStores(snapshot, baselines)
     }
 
     /** Resolve accounts + boards, then open the right board for the active account. */
@@ -209,17 +211,20 @@ export const useWorkspaceStore = defineStore(
       const targetId = workspaceId.value
       if (!targetId) return
       const seq = ++refreshSeq
-      // Capture the board's live-upsert baseline BEFORE the fetch: any block upserted by a live
-      // event while this (potentially slow) snapshot is in flight is newer than the snapshot, so
-      // `hydrate` must NOT clobber it back. The `refreshSeq` guard below only orders refreshes
-      // against each OTHER — this guards a refresh against an interleaved live upsert (e.g. a
-      // run's terminal status landing mid-fetch), the coherence hazard under CI latency.
-      const boardSince = useBoardStore().hydrateBaseline()
+      // Capture the live-write baselines BEFORE the fetch: anything a live event writes while
+      // this (potentially slow) snapshot is in flight is newer than the snapshot, so `hydrate`
+      // must NOT clobber it back. The `refreshSeq` guard below only orders refreshes against each
+      // OTHER — this guards a refresh against an interleaved live write (a run's terminal status
+      // landing mid-fetch, or the inbox card it raises), the coherence hazard under CI latency.
+      const baselines: LiveWriteBaselines = {
+        board: useBoardStore().hydrateBaseline(),
+        notifications: useNotificationsStore().hydrateBaseline(),
+      }
       const snapshot = await api.getWorkspace(targetId)
       // A newer refresh was issued (or the active board switched) while this fetch was in flight —
       // discard this older/staler result so it can't clobber the newer hydrate.
       if (seq !== refreshSeq || workspaceId.value !== targetId) return
-      hydrate(snapshot, boardSince)
+      hydrate(snapshot, baselines)
     }
 
     /** The active workspace id, or throw if the app isn't bootstrapped yet. */

package/i18n/locales/de.json

@@ -2000,11 +2000,11 @@
           "unknown": "war nicht verfügbar ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Führen Sie den Schritt auf einer Agenten-CLI mit MCP aus, oder erweitern Sie die Harness-Liste des Servers.",
+          "harnessUnsupported": "Führen Sie den Schritt auf einer Agenten-CLI mit MCP aus, oder erweitern Sie die Harness-Liste des Servers. Ein Codex-Lauf mit Ihrer eigenen CLI-Anmeldung hat keinen laufspezifischen Ablageort für den Server; verwenden Sie stattdessen Zugangsdaten der Plattform.",
           "transportUnsupported": "Deklarieren Sie dafür einen stdio-Server, oder führen Sie den Schritt auf einer Agenten-CLI aus, die HTTP-Server erreicht.",
-          "missingSecret": "Hinterlegen Sie die genannte Zugangsinformation im Infrastruktur-Fenster unter den Capability-Zugangsdaten.",
+          "missingSecret": "Hinterlegen Sie die genannte Zugangsinformation entweder als Umgebungsvariable des Deployments oder im Infrastruktur-Fenster unter den Capability-Zugangsdaten.",
           "reservedSecret": "Ändern Sie die Deklaration auf einen anderen Schlüssel; das Setzen dieser Variablen hilft gerade nicht.",
-          "oauthNotConnected": "Verbinden Sie dieses Board im Infrastruktur-Fenster damit.",
+          "oauthNotConnected": "Verbinden Sie dieses Board im Infrastruktur-Fenster damit. Ein Deployment ohne ENCRYPTION_KEY hat keinen Ort für eine Berechtigung, das muss ein Betreiber also zuerst setzen.",
           "oauthTokenFailed": "Verbinden Sie es im Infrastruktur-Fenster neu, oder warten Sie die Störung des Anbieters ab.",
           "overBudget": "Kürzen Sie, was der Agent deklariert, damit ein Lauf alles mitführen kann."
         }

package/i18n/locales/en.json

@@ -1527,11 +1527,11 @@
           "unknown": "was not available ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Run the step on an agent CLI that speaks MCP, or widen the server's harness list.",
+          "harnessUnsupported": "Run the step on an agent CLI that speaks MCP, or widen the server's harness list. A Codex run signed in with your own CLI login has nowhere per-run to keep the server, so use a platform credential instead.",
           "transportUnsupported": "Declare a stdio server for it, or run the step on an agent CLI that reaches HTTP servers.",
-          "missingSecret": "Set the credential it names under capability credentials, in the Infrastructure window.",
+          "missingSecret": "Set the credential it names, either as a deployment environment variable or under capability credentials in the Infrastructure window.",
           "reservedSecret": "Change the declaration to ask for another key; setting that variable is exactly what will not help.",
-          "oauthNotConnected": "Connect this board to it from the Infrastructure window.",
+          "oauthNotConnected": "Connect this board to it from the Infrastructure window. A deployment with no ENCRYPTION_KEY has nowhere to keep a grant, so an operator has to set that first.",
           "oauthTokenFailed": "Reconnect it from the Infrastructure window, or wait out the vendor's outage.",
           "overBudget": "Trim what the agent declares, so one run can carry all of it."
         }

package/i18n/locales/es.json

@@ -1436,11 +1436,11 @@
           "unknown": "no estuvo disponible ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Ejecuta el paso en una CLI de agente que hable MCP, o amplía la lista de harnesses del servidor.",
+          "harnessUnsupported": "Ejecuta el paso en una CLI de agente que hable MCP, o amplía la lista de harnesses del servidor. Una ejecución de Codex con tu propia sesión de la CLI no tiene dónde guardar el servidor durante esa ejecución, así que usa una credencial de la plataforma.",
           "transportUnsupported": "Declara un servidor stdio para él, o ejecuta el paso en una CLI de agente que alcance servidores HTTP.",
-          "missingSecret": "Configura la credencial que nombra en las credenciales de capacidades, en la ventana de Infraestructura.",
+          "missingSecret": "Configura la credencial que nombra, ya sea como variable de entorno del despliegue o en las credenciales de capacidades, en la ventana de Infraestructura.",
           "reservedSecret": "Cambia la declaración para que pida otra clave; definir esa variable es justo lo que no ayudará.",
-          "oauthNotConnected": "Conecta este tablero con él desde la ventana de Infraestructura.",
+          "oauthNotConnected": "Conecta este tablero con él desde la ventana de Infraestructura. Un despliegue sin ENCRYPTION_KEY no tiene dónde guardar una concesión, así que un operador debe configurarla primero.",
           "oauthTokenFailed": "Vuelve a conectarlo desde la ventana de Infraestructura, o espera a que pase la caída del proveedor.",
           "overBudget": "Recorta lo que declara el agente, para que una ejecución pueda llevarlo todo."
         }

package/i18n/locales/fr.json

@@ -1436,11 +1436,11 @@
           "unknown": "n'était pas disponible ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Exécutez l’étape sur une CLI d’agent qui parle MCP, ou élargissez la liste de harnesses du serveur.",
+          "harnessUnsupported": "Exécutez l’étape sur une CLI d’agent qui parle MCP, ou élargissez la liste de harnesses du serveur. Une exécution Codex connectée avec votre propre session CLI n’a nulle part où conserver le serveur le temps de l’exécution : utilisez plutôt un identifiant de la plateforme.",
           "transportUnsupported": "Déclarez un serveur stdio à sa place, ou exécutez l’étape sur une CLI d’agent qui atteint les serveurs HTTP.",
-          "missingSecret": "Renseignez l’identifiant qu’il nomme dans les identifiants de capacités, depuis la fenêtre Infrastructure.",
+          "missingSecret": "Renseignez l’identifiant qu’il nomme, soit comme variable d’environnement du déploiement, soit dans les identifiants de capacités, depuis la fenêtre Infrastructure.",
           "reservedSecret": "Modifiez la déclaration pour demander une autre clé ; définir cette variable est précisément ce qui n’aidera pas.",
-          "oauthNotConnected": "Connectez ce tableau à ce serveur depuis la fenêtre Infrastructure.",
+          "oauthNotConnected": "Connectez ce tableau à ce serveur depuis la fenêtre Infrastructure. Un déploiement sans ENCRYPTION_KEY n’a nulle part où conserver une autorisation : un opérateur doit d’abord la définir.",
           "oauthTokenFailed": "Reconnectez-le depuis la fenêtre Infrastructure, ou attendez la fin de la panne du fournisseur.",
           "overBudget": "Réduisez ce que l’agent déclare, pour qu’une exécution puisse tout transporter."
         }

package/i18n/locales/he.json

@@ -1436,11 +1436,11 @@
           "unknown": "לא היה זמין ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "הריצו את השלב על ממשק סוכן שדובר MCP, או הרחיבו את רשימת המעטפות של השרת.",
+          "harnessUnsupported": "הריצו את השלב על ממשק סוכן שדובר MCP, או הרחיבו את רשימת המעטפות של השרת. בהרצת Codex עם חיבור ה-CLI שלכם אין מקום ייעודי להרצה לשמירת השרת, ולכן השתמשו באישור גישה של הפלטפורמה במקום.",
           "transportUnsupported": "הצהירו עבורו שרת stdio, או הריצו את השלב על ממשק סוכן שמגיע לשרתי HTTP.",
-          "missingSecret": "הגדירו את אישור הגישה שהוא מבקש באישורי היכולות, בחלון התשתית.",
+          "missingSecret": "הגדירו את אישור הגישה שהוא מבקש, בין כמשתנה סביבה של הפריסה ובין באישורי היכולות בחלון התשתית.",
           "reservedSecret": "שנו את ההצהרה כך שתבקש מפתח אחר; הגדרת המשתנה הזה היא בדיוק מה שלא יעזור.",
-          "oauthNotConnected": "חברו את הלוח הזה אליו מחלון התשתית.",
+          "oauthNotConnected": "חברו את הלוח הזה אליו מחלון התשתית. בפריסה ללא ENCRYPTION_KEY אין היכן לשמור הרשאה, ולכן מפעיל צריך להגדיר אותו קודם.",
           "oauthTokenFailed": "חברו אותו מחדש מחלון התשתית, או המתינו לסיום התקלה אצל הספק.",
           "overBudget": "צמצמו את מה שהסוכן מצהיר עליו, כדי שריצה אחת תוכל לשאת הכול."
         }

package/i18n/locales/it.json

@@ -2000,11 +2000,11 @@
           "unknown": "non era disponibile ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Esegui il passo su una CLI dell'agente che parla MCP, oppure amplia l'elenco di harness del server.",
+          "harnessUnsupported": "Esegui il passo su una CLI dell'agente che parla MCP, oppure amplia l'elenco di harness del server. Un'esecuzione Codex con il tuo login della CLI non ha dove tenere il server per quell'esecuzione, quindi usa una credenziale della piattaforma.",
           "transportUnsupported": "Dichiara un server stdio al suo posto, oppure esegui il passo su una CLI dell'agente che raggiunge i server HTTP.",
-          "missingSecret": "Imposta la credenziale che indica nelle credenziali delle capability, dalla finestra Infrastruttura.",
+          "missingSecret": "Imposta la credenziale che indica, come variabile d'ambiente del deployment oppure nelle credenziali delle capability, dalla finestra Infrastruttura.",
           "reservedSecret": "Cambia la dichiarazione perché chieda un'altra chiave; impostare quella variabile è proprio ciò che non aiuterà.",
-          "oauthNotConnected": "Collega questa lavagna al server dalla finestra Infrastruttura.",
+          "oauthNotConnected": "Collega questa lavagna al server dalla finestra Infrastruttura. Un deployment senza ENCRYPTION_KEY non ha dove conservare una concessione, quindi un operatore deve impostarla prima.",
           "oauthTokenFailed": "Ricollegalo dalla finestra Infrastruttura, oppure attendi la fine del disservizio del fornitore.",
           "overBudget": "Riduci ciò che l'agente dichiara, così una singola esecuzione può portarlo tutto."
         }

package/i18n/locales/ja.json

@@ -1436,11 +1436,11 @@
           "unknown": "は利用できませんでした（{reason}）。"
         },
         "remedy": {
-          "harnessUnsupported": "MCP を話すエージェント CLI でステップを実行するか、サーバーのハーネス一覧を広げてください。",
+          "harnessUnsupported": "MCP を話すエージェント CLI でステップを実行するか、サーバーのハーネス一覧を広げてください。自分の CLI ログインでサインインした Codex の実行には、サーバーを実行ごとに保管する場所がないため、代わりにプラットフォームの認証情報を使ってください。",
           "transportUnsupported": "このサーバー用に stdio サーバーを宣言するか、HTTP サーバーに接続できるエージェント CLI でステップを実行してください。",
-          "missingSecret": "インフラストラクチャ ウィンドウのケイパビリティ認証情報で、要求されている認証情報を設定してください。",
+          "missingSecret": "要求されている認証情報を、デプロイの環境変数として設定するか、インフラストラクチャ ウィンドウのケイパビリティ認証情報で設定してください。",
           "reservedSecret": "別のキーを要求するよう宣言を変更してください。その変数を設定しても解決しません。",
-          "oauthNotConnected": "インフラストラクチャ ウィンドウからこのボードを接続してください。",
+          "oauthNotConnected": "インフラストラクチャ ウィンドウからこのボードを接続してください。ENCRYPTION_KEY のないデプロイには許可を保管する場所がないため、まず運用者がそれを設定する必要があります。",
           "oauthTokenFailed": "インフラストラクチャ ウィンドウから接続し直すか、提供元の障害が収まるのを待ってください。",
           "overBudget": "1 回の実行ですべて運べるよう、このエージェントの宣言を減らしてください。"
         }

package/i18n/locales/pl.json

@@ -1436,11 +1436,11 @@
           "unknown": "nie był dostępny ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Uruchom krok na CLI agenta, które zna MCP, albo poszerz listę harnessów serwera.",
+          "harnessUnsupported": "Uruchom krok na CLI agenta, które zna MCP, albo poszerz listę harnessów serwera. Uruchomienie Codex z Twoim własnym logowaniem do CLI nie ma gdzie przechować serwera na czas przebiegu, więc użyj poświadczenia platformy.",
           "transportUnsupported": "Zadeklaruj dla niego serwer stdio albo uruchom krok na CLI agenta, które dosięga serwerów HTTP.",
-          "missingSecret": "Ustaw wskazane poświadczenie w poświadczeniach możliwości, w oknie Infrastruktura.",
+          "missingSecret": "Ustaw wskazane poświadczenie jako zmienną środowiskową wdrożenia albo w poświadczeniach możliwości, w oknie Infrastruktura.",
           "reservedSecret": "Zmień deklarację tak, by prosiła o inny klucz; ustawienie tej zmiennej to właśnie to, co nie pomoże.",
-          "oauthNotConnected": "Połącz tę tablicę z serwerem w oknie Infrastruktura.",
+          "oauthNotConnected": "Połącz tę tablicę z serwerem w oknie Infrastruktura. Wdrożenie bez ENCRYPTION_KEY nie ma gdzie przechować zgody, więc operator musi ją najpierw ustawić.",
           "oauthTokenFailed": "Połącz go ponownie w oknie Infrastruktura albo przeczekaj awarię dostawcy.",
           "overBudget": "Skróć to, co deklaruje agent, aby jedno uruchomienie uniosło całość."
         }

package/i18n/locales/tr.json

@@ -1436,11 +1436,11 @@
           "unknown": "kullanılamadı ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Adımı MCP konuşan bir ajan CLI'sinde çalıştırın ya da sunucunun harness listesini genişletin.",
+          "harnessUnsupported": "Adımı MCP konuşan bir ajan CLI'sinde çalıştırın ya da sunucunun harness listesini genişletin. Kendi CLI oturumunuzla yapılan bir Codex çalıştırmasında sunucuyu o çalıştırmaya özel tutacak bir yer yoktur; bunun yerine bir platform kimlik bilgisi kullanın.",
           "transportUnsupported": "Onun için bir stdio sunucusu bildirin ya da adımı HTTP sunucularına erişen bir ajan CLI'sinde çalıştırın.",
-          "missingSecret": "Adı geçen kimlik bilgisini Altyapı penceresindeki yetenek kimlik bilgilerinde ayarlayın.",
+          "missingSecret": "Adı geçen kimlik bilgisini dağıtımın ortam değişkeni olarak ya da Altyapı penceresindeki yetenek kimlik bilgilerinde ayarlayın.",
           "reservedSecret": "Bildirimi başka bir anahtar isteyecek şekilde değiştirin; o değişkeni ayarlamak tam da yardımcı olmayacak şeydir.",
-          "oauthNotConnected": "Bu panoyu Altyapı penceresinden ona bağlayın.",
+          "oauthNotConnected": "Bu panoyu Altyapı penceresinden ona bağlayın. ENCRYPTION_KEY olmayan bir dağıtımda izni saklayacak bir yer yoktur, bu yüzden önce bir operatörün bunu ayarlaması gerekir.",
           "oauthTokenFailed": "Altyapı penceresinden yeniden bağlayın ya da sağlayıcının kesintisinin geçmesini bekleyin.",
           "overBudget": "Tek bir çalıştırma hepsini taşıyabilsin diye ajanın bildirdiklerini kısaltın."
         }

package/i18n/locales/uk.json

@@ -1436,11 +1436,11 @@
           "unknown": "був недоступний ({reason})."
         },
         "remedy": {
-          "harnessUnsupported": "Виконайте крок на CLI агента, який володіє MCP, або розширте список harness сервера.",
+          "harnessUnsupported": "Виконайте крок на CLI агента, який володіє MCP, або розширте список harness сервера. Запуск Codex із вашим власним входом у CLI не має де зберігати сервер у межах запуску, тож використайте облікові дані платформи.",
           "transportUnsupported": "Оголосіть для нього сервер stdio або виконайте крок на CLI агента, що досягає серверів HTTP.",
-          "missingSecret": "Задайте названі облікові дані в облікових даних можливостей, у вікні інфраструктури.",
+          "missingSecret": "Задайте названі облікові дані або як змінну середовища розгортання, або в облікових даних можливостей у вікні інфраструктури.",
           "reservedSecret": "Змініть оголошення так, щоб воно просило інший ключ; задати цю змінну це саме те, що не допоможе.",
-          "oauthNotConnected": "Під’єднайте цю дошку до нього у вікні інфраструктури.",
+          "oauthNotConnected": "Під’єднайте цю дошку до нього у вікні інфраструктури. Розгортання без ENCRYPTION_KEY не має де зберігати дозвіл, тож оператор має спершу задати його.",
           "oauthTokenFailed": "Під’єднайте його заново у вікні інфраструктури або перечекайте збій постачальника.",
           "overBudget": "Скоротіть те, що оголошує агент, щоб один запуск ніс усе."
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.241.0",
+  "version": "0.241.2",
   "description": "Reusable Nuxt layer for the Agent Architecture Board SPA (components, stores, composables, pages). Consume it from a thin deployment app via `extends: ['@cat-factory/app']` and point it at your backend with NUXT_PUBLIC_API_BASE. See deploy/frontend for an example.",
   "repository": {
     "type": "git",
@@ -40,7 +40,7 @@
     "valibot": "^1.4.2",
     "vue": "3.5.40",
     "wretch": "^3.0.9",
-    "@cat-factory/contracts": "0.261.0"
+    "@cat-factory/contracts": "0.261.1"
   },
   "devDependencies": {
     "@toad-contracts/testing": "0.3.2",