fresh-eyes-review

# Fresh-eyes review A context that produced a change reads its intent, not its text, so same-context review misses what a fresh reader would catch. The fix is procedural: a reviewer whose context holds only the artifacts. ## Workflow 1. **Resolve the inputs.** The changeset: whatever the invocation names — a branch, a commit, a diff range, a draft vs its original. Given none, infer it from the session — usually the work just finished, committed or not; no VCS required. With no session context to draw on, fall back to the current git diff; when that too yields nothing, ask the user what to review. Pin the changeset as concretely as the environment allows — a diff or commit range where one exists, otherwise the touched files, with their prior state when reconstructable. Alongside it, a short statement of what the change is supposed to achieve, when one exists (the task as stated, a PR or ticket description); when this session authored the change, never include the session's own reasoning, plan, or messages — leaked rationale recreates the blindness the fresh context exists to remove. Done when changeset and intent are pinned down and free of authoring context. 2. **Confirm the prompt.** Assemble the reviewer prompt — changeset, intent, the mandate and exclusions below, and any further reviewer instructions the invocation supplies (e.g. what to report back). When the invocation supplied changeset, intent, and mandate explicitly (e.g. a driv...