v0.22.0 — Product / Architect / Code Generation as separate dashboard views

Changed

The status dashboard (/architect:report-status, /product:report-status, /architect:report-backlog-status — all one tool) now has four views instead of two, cycled with Tab / Shift-Tab: Product · Architect · Code Generation · Backlog Delivery. A view the project has nothing behind is dimmed and skipped.

Product and architect are separate tabs

The single "pipeline" tab had to detect whether a project was running the product or the architect pipeline and then showed only that one. On a project that ran both, the other pipeline was unreachable, and every phase its manifest defined was dumped into the tab's "recorded outside the manifest" group as if it were an anomaly.

They are separate pipelines with separate manifests, so they are now separate tabs — each stating which pipeline it shows rather than guessing. A registry entry the other plugin's manifest defines is no longer reported as unmanifested: it is the tab next door.

Code generation is its own view

generate-scalardb-code, generate-infra-code, generate-docs and /product:generate-frontend are run by hand after whichever pipeline designed the system and emit code into the target project rather than reports under reports/, so they no longer sit inside a pipeline tree they are not a step of. The Code Generation view collects them from both plugins, groups by plugin, and each row offers its own plugin's slash command (/product:generate-frontend, /architect:generate-infra-code) rather than the view's.

generate-test-specs stays in the architect pipeline: it writes specifications, not code.

Cross-boundary dependencies and staleness are unaffected — generate-scalardb-code is still blocked by design-implementation and still goes stale when it is rerun. Only the grouping and the progress fraction are per-view.

CLI

• --view= takes product, architect, codegen, backlog, plus pipeline (whichever pipeline this project runs, from --plugin= or detection) and auto (unchanged: the detected pipeline, else the backlog).
• --group=core|extension keeps applying to the architect pipeline view only; it has no meaning in the codegen view, whose groups are plugins.
• --md for the codegen view defaults to reports/codegen-status.md.
• --json gained view, section, and a per-phase plugin / section; each phase's group is now the group header it actually renders under.

Verification

tools/lib/pipeline_status_data.test.py gains check_sections (the pipeline/codegen split, the codegen tree grouping by plugin and offering per-phase commands, and which plugins a project has evidence of having run); tools/nexus-status.test.sh gains view-selection cases for all four views. All seven runnable suites pass.

Full changelog: CHANGELOG.md · CHANGELOG_ja.md