# FE-RB-001 — Boot configuration failure Trigger on `BOOT_CONFIG_FAILURE` after the single bounded refetch fails. Stop product route mounting and show the safe support shell; the planned owner triage target is five minutes. Escalate from the environment/config owner to the release owner. Close only after a clean-session boot mounts the product root, config validation evidence passes, and repeated boot-error telemetry is absent. ## Changing an emergency switch without a rebuild Only `CAPABILITY_OVERRIDES` and `FEATURE_OVERRIDES` may change in a deployed `config.json`. Every browser validates the document on boot, so a typo there causes this runbook's failure for every user. Change it in four steps: 1. Download the deployed `config.json` twice, as `deployed.json` (keep it as is) and `edited.json`. Change only the switch in `edited.json`. 2. From a checkout of the deployed commit, run `RELEASE_TARGET= corepack pnpm check:release-admission --config /abs/edited.json --original /abs/deployed.json` (absolute paths: pnpm runs it from the repository root). It must print `ADMITTED`. It refuses a schema error, a target rule, and any changed field other than the two switches, `BUILD_ID` and `RELEASE_ID` included. 3. Upload `edited.json` next to the live file and rename it over `config.json` on the same filesystem. Never edit the live file in place. To undo, rename `deployed.json` back the same way. 4. Boot in a clean session (new browser profile) and see the product root mount. The switch takes effect on the next boot only. The served document then differs from the release record (`checksums.txt`, the promoted archive). Note the change in the release log, and put it in the profile (`config/runtime/.json`) for the next build.