working-with-prslisted

# Working with pull requests Every change reaches `main` through a pull request. `main` is protected, so no path skips this. ## The gate, before you open anything 1. `just cs` applies the formatter and rector fixes. Commit anything it changed. It works from a worktree: the finder uses explicit excludes and throws if it matches zero files, so a vacuous pass is not possible. 2. `just ci` is check-only. It reports style and rector violations but never rewrites files; `just cs` is the step that applies them. Fix every failure, including ones that pre-date your change. 3. Run a Codex review with `mcp__codex-cli__review` and `model: "gpt-5.6-sol"`. Always pass the model explicitly. This Codex account rejects the model the tool picks by default. Review against `origin/main`, never `main`. A worktree's local `main` is often stale, so a review against it reports findings for already-merged code. **One clean pass is not a pass. Run until two consecutive passes come back clean.** The same review on the same commit gives different answers each time. Two runs on one branch, same model and same base, disagreed: the second found a real defect that sat in the tree the first had called clean. The habit that protects you is the one an agent falls into anyway when it fixes findings and re-runs. Branches that stopped at their first clean answer are the ones with the least evidence behind them, however green they look. **Scope the review to the commit, not the base, once a