Checkpoint 5.4: a release that was actually installed

Fresh-prefix install drill passed end to end — migrations, livez/readyz/version, dashboard, auth — with README and RUNBOOK rewritten to what the system actually is.

at a glance

Goal: Another developer installs it, gets a useful alert, and can distinguish a target outage from missing monitoring data — the ship gate.
Built: Installable artifact + docs: fresh-prefix install drill (migrations → /livez /readyz /version → dashboard → auth); GET /version reports the binary's own version; README rewritten; RUNBOOK verify steps check /version; e2e gate fixed for config-less playwright runs.
Result: install drill: fresh prefix → migrations ran → livez+readyz+version answered → dashboard served → auth held (401/200) · 4/4 browser specs on the fixed gate
Code: akira-shirase-oss/monitoring-service · main @ 2cf5e53

What changed: scripts/deploy.sh → releases/<sha>/bin + current symlink, data/ outside releases — run on a fresh prefix end to end: migrations ran, /livez /readyz /version answered, the dashboard served, auth held (401/200). GET /version reports the binary’s own version — the only honest answer after an upgrade or rollback. README rewritten to what the system actually is (it still said “scaffold”); the RUNBOOK’s verify steps now check /version. The e2e gate was fixed to run config-less so a fresh checkout can prove itself.

Proof: the install drill passed on a clean prefix, and 4/4 browser specs ran on the fixed gate. That closes the ship gate: another developer can install it, get a useful alert, and distinguish a target outage from missing monitoring data.