## Summary

<!-- What and why. Risk is discovered by Gatekeep — do not rubber-stamp "low risk" here. -->

## Testing notes

- [ ] Discovered build/test entry points run locally or in CI (paste command / job link)
- [ ] Benchmarks vs thresholds (fps / startup / memory) if behavior-sensitive — or N/A
- [ ] Client-visible paths: noted if **not** verified on GitHub-hosted runners

Commands / evidence:

```
<!-- e.g. npm test, make verify, artifact URL from gatekeep-last-good-* -->
```

## Risk (author hint — Gatekeep may raise the PR tier)

Author self-assessment (optional): low / medium / high

Sensitive paths touched? (auth, billing, `.github/workflows`, secrets, release): yes / no

<!-- Gatekeep findings lead with severity (Critical→Low) + exact location + why it matters.
     No @-mention chat commands — fix or dismiss: dismissed: <reason> -->

## How to revert

Rollback speed is the load-bearing wall. Fill this in before merge.

1. **One-step revert:** `git revert <merge-sha>` (or GitHub "Revert") then merge the revert PR.
2. **Artifact / slot rollback:** point `active` at previous known-good artifact (see Gatekeep deploy-slots note); restart.
3. **Feature flag / kill switch:** <!-- name → GATEKEEP_MERGE_ENABLED=false also stops AI auto-merge -->
4. **Data / world migrations:** <!-- none | forward-only | script path -->
5. **Owner if this causes an incident:** <!-- @owner → file gatekeep-incident -->

If this change is hard to revert, treat it as **high** risk and get the required human approvals.