App render-substrate: consume the broker's RenderDataFrame

What changed

Where it lives

• src/lib/surface-registry/page-card/render-catalog.ts — NEW. RENDER_CATALOG_VERSION + validateRenderRows (component_id → row Zod schema, reusing GENERATED_PROP_SCHEMAS).
• src/lib/agents/atlas-rail.ts — WireRenderFrame, RailRender, renderFromWire; the render.data case + RailState.render (reset on launch).
• src/components/agents/agent-thread-item.ts — new componentResult kind.
• src/components/agents/agent-chat-panel.tsx — explicit componentResult case + ComponentResultView: text/JSON fallback + denied + empty ONLY (no generic table — typed matter_table/matter_card rendering is 003-components; a valid frame renders as a text/JSON summary until then).
• src/components/agents/agent-dock-mount.tsx (cont.) — the render reference is persisted in its OWN useEffect (inlined), decoupled from the reply-commit gate: a render frame arriving after the same run's reply still persists.
• src/lib/agents/agent-thread-store.ts — componentResult REFERENCE variant (no rows). Persist/hydrate are generic — no per-kind logic change.
• src/lib/agents/use-dock-chat-rail.ts — exposes rail.render (the latest render frame, reset per launch).
• src/lib/agents/dock-render-bridge.ts — NEW, pure. liveRenderItem / mergeLiveRender (rail render → VISIBLE componentResult, rows or text fallback) + renderReference (intent-only persist, no rows).
• src/components/agents/agent-dock-mount.tsx — on a settled turn, persists the reference AND surfaces the live render item (override-by-id); a render frame now counts as turn content. toThreadItem maps a rehydrated reference to an empty placeholder.
• messages/{en,hi}.json — componentFallbackLabel / componentDenied / componentEmpty (both locales).

Verify

pnpm lint        # clean (1 pre-existing avatar.tsx warning, unrelated)
pnpm typecheck   # clean
pnpm test        # 882 passed
pnpm build       # green
git diff --check # clean
# NOTE: do NOT run pnpm codegen — import contracts from src/gen.

• AC2 (mounted dock) agent-dock-mount.render.test.tsx MOUNTS the real <AgentDockMount> (RTL + react-query + intl; useDockChatRail mocked to return a render.data-derived RailRender). It asserts the rail → items → AgentDock → panel wiring end to end: a valid frame paints a VISIBLE componentResult (row text in the DOM), an unknown component_id paints a VISIBLE text/JSON fallback, and the reference is persisted to sessionStorage with intent-only keys (no rows). Panel-level + pure-bridge coverage stays in agent-chat-panel.render.test.tsx / dock-render-bridge.test.ts.
• No stale render a malformed render.data (missing ids) CLEARS any prior rail.render — a stale result never lingers (atlas-rail.test.ts).
• AC2 the persisted envelope carries query_ref + component_id but NOT clientName/rows; it rehydrates as a reference (replay re-runs the intent).
• AC3 malformed rows for a known component fall back (no throw).
• AC4 state="denied" → "no longer available"; a known component with zero rows → empty-state.
• Persist race render persistence lives in its own useEffect, not behind the reply gate, so a render frame arriving after the same run's text reply still persists the reference.
• No regression all existing rail + store tests green; new coverage in atlas-rail.test.ts, agent-thread-store.test.ts, dock-render-bridge.test.ts.

Reversible calls (stated for review): the render frame envelope type is assumed render.data with the RenderDataFrame fields flat on payload (consistent with run.failed); the exact string reconciles with the functions emission ticket and is forward-compatible (unknown frame types are ignored today). No client→brain version carrier is sent — the generated DockChatContext is a STRICT envelope, and D11 unknown-id fallback covers v1.

Deferred (re-scope, AGENT1 blocker-2): the reference-only persist is kept (security invariant satisfied), but replay RE-RUN on rehydrate — re-materializing rows after a refresh — is DEFERRED to a follow-on (coupled to live-rail re-invoke). A rehydrated reference stays an empty placeholder until then (marked with a ponytail: note in the dock).

Non-goal (RFD-AGT-004): no new .tsx catalog components (003-components), no functions/agents changes (separate emission tickets).

Files changed

15 file(s), +932 / -6 lines