Why: The user ruled the initial experience good and directed completing U6 and beyond. U6 brings pages into the work view: a compact task-page section under the current-task card (latest or pinned, jump to preview, disappears cleanly when disabled so the work view stays intact), project-level cross-conversation aggregation behind the owner scope with project resolved authoritatively from the conversation row (never model-reported), and catalog guidance organizing pages by task phase while task facts stay sourced only from real task records.
Evidence: Task card carries precheck/task-sync/make test receipts (make evidence, SELF; one known sandbox-test flake rerun clean); CI ci/test on PR HEAD is the authoritative gate. Backend project-aggregation test covers owner isolation, cross-owner zero visibility, history retention post-disable; frontend pin test covers freeze/follow.
Impact: backend/frontend gitlinks + task card. Auto-trigger mode stays off by default (future opt-in); deployment separately reviewed.
Why: The user ruled the initial experience good and directed completing U6 and beyond. U6 brings pages into the work view: a compact task-page section under the current-task card (latest or pinned, jump to preview, disappears cleanly when disabled so the work view stays intact), project-level cross-conversation aggregation behind the owner scope with project resolved authoritatively from the conversation row (never model-reported), and catalog guidance organizing pages by task phase while task facts stay sourced only from real task records.
Evidence: Task card carries precheck/task-sync/make test receipts (make evidence, SELF; one known sandbox-test flake rerun clean); CI ci/test on PR HEAD is the authoritative gate. Backend project-aggregation test covers owner isolation, cross-owner zero visibility, history retention post-disable; frontend pin test covers freeze/follow.
Impact: backend/frontend gitlinks + task card. Auto-trigger mode stays off by default (future opt-in); deployment separately reviewed.
Refs: modules/documents/docs/proposals/2026-10-10-generative-ui-plugin.md (r2 U6); task card feature/generative-ui-u6
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-generative-ui-u6.md; R0=a1ac948155eb8957a87f37d8da4a9feb870dd532.
Impact: task metadata only; the feature workspace starts at a1ac948155.
Refs: .task/feature-generative-ui-u6.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=df18c35203601bdec8d1671c60e0f4cf7d0b5aef.
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: The user ruled the initial experience good and directed completing U6 and beyond. U6 brings pages into the work view: a compact task-page section under the current-task card (latest or pinned, jump to preview, disappears cleanly when disabled so the work view stays intact), project-level cross-conversation aggregation behind the owner scope with project resolved authoritatively from the conversation row (never model-reported), and catalog guidance organizing pages by task phase while task facts stay sourced only from real task records.
Evidence: Task card carries precheck/task-sync/make test receipts (make evidence, SELF; one known sandbox-test flake rerun clean); CI ci/test on PR HEAD is the authoritative gate. Backend project-aggregation test covers owner isolation, cross-owner zero visibility, history retention post-disable; frontend pin test covers freeze/follow.
Impact: backend/frontend gitlinks + task card. Auto-trigger mode stays off by default (future opt-in); deployment separately reviewed.
Refs: modules/documents/docs/proposals/2026-10-10-generative-ui-plugin.md (r2 U6); task card feature/generative-ui-u6