test(ci): inject RM-61 post-readiness crash control

docs/scratchpads/1000-rm-61-ci-contract-exemption.md

@@ -33,14 +33,23 @@ Historical JSON saved locally under `.evidence/rm-61/` (not for commit). Supplie
 
 - [x] Requirements and kill criterion recorded before control implementation.
 - [x] Historical full-JSON records captured.
-- [ ] Startup-failure control observed terminal.
+- [x] Startup-failure control observed terminal.
 - [ ] Post-readiness crash control observed terminal.
 - [ ] Discrimination verdict recorded.
 - [ ] Conditional exemption implementation (only if verdict permits).
 
 ## Tests / evidence
 
-Pending.
+### Control 1 — real startup failure
+
+- Commit: `3931b0e29eb834914f7b17e4db7e221481d436fa`
+- Pipeline: #2189, exact commit match.
+- Full JSON child scan: 9 total — 7 success, 2 failure, 0 skipped/pending/running.
+- `ci-postgres`: `state=failure`, `exit_code=1`, `error=null`, with a five-second execution window.
+- `test`: `state=failure`, `exit_code=1` after the readiness budget expired.
+- Pipeline/workflow: terminal `failure`.
+
+This control is red and its service record differs from #1000 (`exit_code=0` plus pod-not-found). It proves the startup-failure direction only. It does not settle the dangerous post-readiness crash/garbage-collection path.
 
 ## Risks