Why: U6 workspace extension - surfaces aggregate across conversations under the owner project scope (project resolved from the conversation row, never model-reported); catalog guidance organizes pages by task phase with task facts only from real records.
Evidence: build/vet clean; suites green incl. project-aggregation owner-isolation test.
Impact: New GET /api/projects/{id}/surfaces; Submit resolves project; catalog text.
Refs: proposal r2 U6; Dev task feature/generative-ui-u6
Why: U6 workspace extension - surfaces aggregate across conversations under the owner project scope (project resolved from the conversation row, never model-reported); catalog guidance organizes pages by task phase with task facts only from real records.
Evidence: build/vet clean; suites green incl. project-aggregation owner-isolation test.
Impact: New GET /api/projects/{id}/surfaces; Submit resolves project; catalog text.
Refs: proposal r2 U6; Dev task feature/generative-ui-u6
Why: U6 extends pages from conversations into the task/project
workspace - surfaces aggregate across conversations under the owner's
project scope (project resolved authoritatively from the conversation
row, never self-reported by the model), and the catalog guidance now
organizes pages by task phase (requirements/execution/acceptance)
while stating that task facts come only from real task records.
Evidence: build/vet clean; surfacesvc suite green incl. the new
project-aggregation test (owner isolation, cross-owner zero, history
retained post-disable); genui/store suites green.
Impact: New endpoint GET /api/projects/{id}/surfaces; Submit resolves
project from conversation; catalog text guidance. Existing endpoints
unchanged.
Refs: proposal r2 U6; Dev task feature/generative-ui-u6
weichen
merged commit 696ef15168 into main2026-10-12 02:12:59 +00:00
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: U6 workspace extension - surfaces aggregate across conversations under the owner project scope (project resolved from the conversation row, never model-reported); catalog guidance organizes pages by task phase with task facts only from real records.
Evidence: build/vet clean; suites green incl. project-aggregation owner-isolation test.
Impact: New GET /api/projects/{id}/surfaces; Submit resolves project; catalog text.
Refs: proposal r2 U6; Dev task feature/generative-ui-u6
Why: U6 extends pages from conversations into the task/project workspace - surfaces aggregate across conversations under the owner's project scope (project resolved authoritatively from the conversation row, never self-reported by the model), and the catalog guidance now organizes pages by task phase (requirements/execution/acceptance) while stating that task facts come only from real task records. Evidence: build/vet clean; surfacesvc suite green incl. the new project-aggregation test (owner isolation, cross-owner zero, history retained post-disable); genui/store suites green. Impact: New endpoint GET /api/projects/{id}/surfaces; Submit resolves project from conversation; catalog text guidance. Existing endpoints unchanged. Refs: proposal r2 U6; Dev task feature/generative-ui-u6