Cover the admin Releases page end to end

[selfcontained]

What

release-admin.tsx and the five modules #970 split out of it — release-admin-banners.tsx, release-admin-create.tsx, release-admin-list.tsx, release-admin-unreleased.tsx, and use-release-admin-data.ts — had no test coverage at all. release-utils.ts and OperationTakeover were already covered (release-utils.test.ts, PR #982), so this file is scoped to the admin-only surfaces.

One test file mounts the real ReleasesAdmin with a fake EventSource for the release stream and a URL-routed fetch, so the props wiring between the shell, the four panes, and the data hook is exercised together rather than mocked apart.

What it pins

• Unreleased changes — the ternary ladder in priority order: an unreleased-fetch error outranks a missing ref, which outranks the commit count. Plus the commit list, the +N more overflow line, and the singular/plural wording.
• useReleaseAdminData — both mount fetches, the x-dispatch-release-client-id header that lets the server push info-progress back over the stream, refresh() hitting both endpoints, and the promote mutation: request body, the row flipping to stable on success, and a failed promote surfacing a cleaned error while the confirmation collapses so the operator gets the button back.
• Promote confirm flow — scoped to the row the operator actually clicked, not every prerelease.
• Create release — the render gate (hidden at a zero count, shown when the ref is missing), the bumped-tag previews taking the newest GitHub release over the deployed tag, the confirm dialog, the POST method and body, and the switch into the progress takeover. A rejected request shows the error and stays on the page.
• Banners — in-flight, failed, and the watchedRelease guard that stops a stale done snapshot from claiming a release just finished, plus the refresh-once-per-run behaviour when one really does.

Validation

• pnpm run check, pnpm run format, pnpm run lint:web (0 errors), pnpm run finalize:web — all clean
• pnpm run test — server 164 files/2808 tests, web 72/1090 (1064 → 1090, +26), extension 9/60
• pnpm run test:e2e — 181 passed / 12 skipped
• pnpm run test:e2e:live — 11 passed in 20.8s, no stray e2e-* tmux sessions or leaked containers
• Mutation battery: 45 mutants across the six modules, 45 killed. Three initial survivors were diagnosed rather than worked around — a promote confirmation that stayed open after a failed request, a failed release also reading as in-flight, and the non-create job-type filter — and each was killed by sharpening or adding an assertion.

A review pass over the diff found six items, all applied: the job fixture now uses the real Extract<ReleaseJob, { jobType: "create" }> wire type (a typo'd phase previously type-checked and silently gutted a test), four structurally-unfailable negative assertions on sibling ternary branches were deleted, and the client-id lookup got a guard so a missing call fails readably.

Test-only change; no product code touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Dqcng3rgYPEToKrksY3FZk