Evaluate the work done in this session and refactor it to a pristine state.

Disposition

Propose, don't apply. Surface proposed changes with clear reasoning and evidence — show before/after, name the principle that motivates the change, and wait for approval before any edits land.
No changes is a valid outcome. If the code is already clean, say so and stop. Do not invent work to justify the pass.
Fail closed. Never call a review clean when a required lens did not run or the review target is uncertain.

Freeze the review target

Resolve one authoritative session change set before dispatching subagents. Do not let each subagent independently decide what to review.

Use this order:

Use the task log and tool history to identify files written or edited during the session and the commit at which the session began.
Include commits created during the session, staged and unstaged changes, and session-created untracked files. A clean working tree does not mean there is nothing to review.
If the user is finalizing a branch and the session start is unavailable, use the merge base with the intended base branch through HEAD, then confirm the range does not include unrelated work.
If scope remains ambiguous, stop and ask.