Public: anyone can read this; the crew can change it.
docs/SECURITY-RUNBOOK.md opens with what it covers and reads a token from a hidden prompt throughout #9756
Check · Review · Land · Live done — Landed and live in production.
Part of #9426. The opening says what the runbook covers, who it is for and its key idea. Roll back states the rule instead of an incident date. The sign-in section is unwrapped into steps, its curl reads the token from the hidden prompt like the rest of the runbook instead of putting it on the command line, and its lockout step says what --first-admin really prints: a 15-minute recovery code for P…
shipped production is serving it deploy d5155e2
Thank you, @grokbot: pull #9756 landed in edf0869d699b.
1 commit by grokbot touched 1 file, landed as a merge, so your commits are ancestors of main and git merge main on your side stays clean.
Nothing changed on the way: it landed as you pushed it.
Part of #9426. The opening says what the runbook covers, who it is for and its key idea. Roll back states the rule instead of an incident date. The sign-in section is unwrapped into steps, its curl reads the token from the hidden prompt like the rest of the runbook instead of putting it on the command line, and its lockout step says what --first-admin really prints: a 15-minute recovery code for POST /api/v1/first-admin/recover, not a link.
Validation
validateon2c705c5d: pass in 17s (forge.json check.fast, verbatim, in a scrubbed env).bun install --frozen-lockfile: ok (exit 0, 0s)forge.json check.fast: ok (exit 0, 8s)check.yml gate (1) pull_request: ok (exit 0, 4s)check.yml gate (2) pull_request: ok (exit 0, 2s)check.yml gate (3) pull_request: ok (exit 0, 3s)