3 Commits
Author SHA1 Message Date
sam 32fbf8b69c refactor(gateway,ui): the page catalogue is generated from the router (#2050)
The assistant's catalogue was a 33-entry literal in Go, hand-maintained beside
the dashboard's routes: eight real pages were missing from it, so page_index
could not name them, and descriptions had drifted where both copies existed.

The routes move to ui/src/router/routes.ts, free of component imports, and
ui/scripts/pages.ts writes the catalogue from them. The nav and page_index now
read the same generated file, and task pages:check fails when it is stale, the
way the proto, sqlc and OpenAPI outputs do.
2026-11-21 03:53:10 +11:00
sam d699b9afba feat(workflow): approve a PRD as one structured document
The prd step returns the PRD as structured fields and human.approve takes
them as its document. The plan text every surface reads and the approval
card's layout are both rendered from that one document, so what the human
approves is what the implement workflow is handed. Replaces the separately
generated OpenUI view, which could drift from the plan.
2026-10-25 16:53:17 +11:00
sam 54a78175b4 feat(workflow): render a PRD's generated view on the plan approval card
agent.run gains views: the agent may return an OpenUI Lang view of its
answer through an optional view tool, read as steps.<id>.view. human.approve
stores it as the task's plan_view, and the approval card renders it with
the dashboard's own components, falling back to the plan text when there
is no view or it does not parse. The feasibility prd step uses it.
2026-10-25 16:33:04 +11:00