Architect a deep code review block that misses nothing

A rushed code review misses the bug that takes down production on Friday. This designs a review block that fits the risk: a warm-up to orient yourself in the code before judging it, a structured pass that covers the things people skip, and a close that records what you found. Give it the PR, the scope, the time and how well you know the code, and it builds the session.

I need to design a deep work session for reviewing complex code.

Codebase / PR being reviewed: {CODEBASE_DESCRIPTION}
Scope of the review: {REVIEW_SCOPE}
Session length available: {SESSION_LENGTH}
Risk level (what breaks if I miss something): {RISK_LEVEL}
My familiarity with this code: {FAMILIARITY_LEVEL}

Design the session architecture:
- A warm-up phase to orient myself in the code before evaluating it (context-loading, not reviewing)
- A sequenced review approach: what to check first, second, and last
- How to handle rabbit holes: when to note them and move on vs. dig in
- Break placement that does not break cognitive load mid-logic
- A closing checklist to confirm the review is actually complete
- One constraint for this session that keeps me from skimming

Make it specific to the risk level and scope, not a generic review checklist.