Why: U4 of the Generative UI proposal - saved pages become visible and survive refresh: SurfaceView renders the snapshot through the existing UIRenderer vocabulary with stable node-id keys and a visible degraded state; surface.updated events project into a surfaces slice behind a strict revision guard (stale/duplicate never overwrite); preview tabs gain a surface: kind with doc-ref bridging into artifact previews and non-stealing auto-open; opening a conversation reloads the authoritative surface list.
Evidence: Task card carries precheck/task-sync/make test receipts (make evidence, SELF); CI ci/test on PR HEAD is the authoritative gate. Component chains green (UI 106/106, frontend 87/87 + tsc clean, backend go test + PG dialect). One known-flaky sandbox test failed once and passed on rerun (noted in card); knip ratchet +1 for the intentional cross-repo SurfaceView export (UI #45).
Why: U4 of the Generative UI proposal - saved pages become visible and survive refresh: SurfaceView renders the snapshot through the existing UIRenderer vocabulary with stable node-id keys and a visible degraded state; surface.updated events project into a surfaces slice behind a strict revision guard (stale/duplicate never overwrite); preview tabs gain a surface: kind with doc-ref bridging into artifact previews and non-stealing auto-open; opening a conversation reloads the authoritative surface list.
Evidence: Task card carries precheck/task-sync/make test receipts (make evidence, SELF); CI ci/test on PR HEAD is the authoritative gate. Component chains green (UI 106/106, frontend 87/87 + tsc clean, backend go test + PG dialect). One known-flaky sandbox test failed once and passed on rerun (noted in card); knip ratchet +1 for the intentional cross-repo SurfaceView export (UI #45).
Impact: core/ui/frontend/backend gitlinks; U5 (form actions) and deployment stay separately reviewed.
Refs: modules/documents/docs/proposals/2026-10-10-generative-ui-plugin.md (r2 U4); task card feature/generative-ui-u4
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-generative-ui-u4.md; R0=a70ed114fba2d51bb93ec8cb0662703ab0bc0614.
Impact: task metadata only; the feature workspace starts at a70ed114fb.
Refs: .task/feature-generative-ui-u4.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=0f589ed7ff5c1dc63a9700906fe9138fe607d85c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: U4 of the Generative UI proposal - saved pages become visible and survive refresh: SurfaceView renders the snapshot through the existing UIRenderer vocabulary with stable node-id keys and a visible degraded state; surface.updated events project into a surfaces slice behind a strict revision guard (stale/duplicate never overwrite); preview tabs gain a surface: kind with doc-ref bridging into artifact previews and non-stealing auto-open; opening a conversation reloads the authoritative surface list.
Evidence: Task card carries precheck/task-sync/make test receipts (make evidence, SELF); CI ci/test on PR HEAD is the authoritative gate. Component chains green (UI 106/106, frontend 87/87 + tsc clean, backend go test + PG dialect). One known-flaky sandbox test failed once and passed on rerun (noted in card); knip ratchet +1 for the intentional cross-repo SurfaceView export (UI #45).
Impact: core/ui/frontend/backend gitlinks; U5 (form actions) and deployment stay separately reviewed.
Refs: modules/documents/docs/proposals/2026-10-10-generative-ui-plugin.md (r2 U4); task card feature/generative-ui-u4