Release v0.5.0 — cockpit as the main interface

[robercano]

What

This issue is the release gate for milestone v0.5.0 — cockpit as the main interface. It reuses issue #97's blocking-graph convention as the ENTIRE release gate — no new state machine: the field below tells the loop's census this issue must wait until every other issue in the milestone is closed.

Blocked by #206, #207, #208, #209

Release theme

Turn the cockpit from a read-only status page into the primary interface for driving a release:

• Cockpit v2 foundation: /api/state JSON snapshot + zero-dep client-rendered SPA shell #206 — foundation: /api/state JSON snapshot + zero-dep client-rendered SPA shell
• Cockpit: release board — milestone-centric default view (burn-up, needs-you, in-flight, up-next, blocked, linked PRs) #207 — release board: milestone-centric default view (burn-up, needs-you, in-flight, up-next, blocked, linked PRs)
• Cockpit: interactive dependency graph — milestone DAG with live status coloring #208 — interactive dependency graph with live status coloring
• Cockpit: model-routing editor — validated gates.json writes, auto-committed, loopback-only #209 — model-routing editor: the one sanctioned write path (gates.json budget.*_model keys only, auto-committed, loopback-only)

Explicitly deferred out of this milestone: group/filter by arbitrary label (filed as backlog), retiring the /legacy server-rendered view, any write surface beyond model routing.

Keeping that field current

Whenever an issue is added to (or removed from) this milestone, refresh the field above so it still lists every OTHER open issue in the milestone (never this issue itself). Helper query:

bash .claude/scripts/bot-gh.sh issue list --milestone "v0.5.0 — cockpit as the main interface" --state open --json number,title

What happens once this issue is unblocked and advanced

Once every issue named above is closed, this issue becomes a normal planned + module:* candidate and the loop's ADVANCE step picks it up like any other issue. Its implementer runs the release driver:

bash .claude/scripts/release.sh v0.5.0 --issue <this-issue-number>

which bumps the plugin/marketplace versions, generates the dated CHANGELOG entry from merged PR titles since the last tag, tags the release, and opens the rollout/feedback companion per docs/USAGE.md → "Release cycle".