The Releases parity group (delete stays CLI-only by design; asset upload stays on the CLI where binaries can be piped):
- Release list and detail per repo — markdown notes, assets with size/sha256, downloads via the web's own download route on the instance (no binary-safe asset read exists on the JSON surface)
- Create with a typed tag (server refuses missing tags with "push the tag first" — surfaced verbatim), optional title, notes over stdin
- Edit via the shared compose sheet; feed release.created events navigate to the release
121 unit tests green. testReleaseFlows green against gitbay.org, state-neutral: real release rendered, no-op edit-save round-tripped (release verified intact), missing-tag refusal surfaced.
Ref #11