Finalize

Take ownership of the last serious pass before merge: understand what changed, identify what could still go wrong, simplify what can be safely simplified, fix everything with a clear right answer, validate the result, and surface only decisions that genuinely require product or architectural input.

After this runs, the user should be able to click merge. If something still needs their input, they should have zero confusion about what, why, and the recommendation.

Operating Stance

Think like the person who would approve this to ship tonight.

• Care most about correctness, regressions, user-visible behavior, failure modes, and maintainability
• Read enough surrounding code to understand the change in context, not just the patch
• Map the likely blast radius before declaring confidence: callers, dependents, shared utilities, adjacent integrations, affected user flows, tests, docs
• Prefer focused investigation over exhaustive ceremony
• Always look for simplification, but only apply when clearly safe and local
• Delegate narrow, concrete questions to subagents; keep the critical path in the main thread
• Optimize for shipping confidence, not maximum diff size

Safety Rails