Review Change

Use this during development after an implementation slice and before declaring
the task locally ready. This is an advisory development review, not the final
PR gate. Use co-review only for the finished-PR gate.

Set REVIEW_SKILL_FILE to this skill's absolute SKILL.md path supplied by
the skill loader. If it is absent, use the existing DOTFILEDIR; never derive
the helper path from the reviewed checkout.

REVIEW_ROOT=$(uv run --no-project python - "${REVIEW_SKILL_FILE:-}" "${DOTFILEDIR:-}" <<'PYROOT'
from pathlib import Path
import sys

source, fallback = sys.argv[1:]
if source and (not Path(source).is_absolute() or Path(source).name != "SKILL.md"):
    raise SystemExit("Use the absolute SKILL.md path supplied by the skill loader")
root = Path(source).resolve(strict=True).parents[3] if source else (
    Path(fallback).expanduser().resolve(strict=True) if fallback else None
)
required = ("claude/hooks/agent_runtime.py", "claude/skills/lib/workflow_context.py", "claude/skills/co-review/references/failure-classes.md")
if root is None or not all((root / name).is_file() for name in required):
    raise SystemExit("Installed review helpers are unavailable")
print(root)
PYROOT
) || exit 2
RUNNER="$REVIEW_ROOT/claude/hooks/agent_runtime.py"
CONTEXT="$REVIEW_ROOT/claude/skills/lib/workflow_context.py"
RUBRIC="$REVIEW_ROOT/claude/skills/co-review/references/failure-classes.md"

Use the exact target worktree and a pinned base from the caller. Derive the full
relevant diff and affected callers from that target. Read the task or change to
derive intended behavior; ask only when it is not established. Review the
target against its base, relevant callers, and repository contracts. Reproduce
failures safely when useful.

For a repair batch, require a packet naming the original finding's provenance,
scenario, and concrete violated contract. Review self-review and independent
evidence: where executable, a behavioral regression must show the original
failure and repaired success, with affected failure paths including ownership or
lifecycle when relevant. Classify each new blocker as repair-introduced,
previously missed, or changed requirements, with a concrete consequence.
Set REVIEW_REPAIR_PACKET to the readable packet path for a repair batch.

Resolve account scope from the original target before dispatch. Preserve that
scope, including an intentionally unset personal CLAUDE_CONFIG_DIR.

uv run --no-project python "$CONTEXT" account-scope \
  --cwd "$REVIEW_REPO" --runtime codex

Resolve the native Codex route before dispatch and require a ready result.

uv run --no-project python "$RUNNER" route \
  --runtime codex --role development_reviewer --risk normal --provisional

Use the returned model and effort to spawn one fresh native Codex child in the
target worktree, read-only. Set fork_turns: "none", model to the returned
model, and reasoning_effort to the returned effort; do not silently inherit
the controller's history or effort. The default route is Codex gpt-5.6-sol/high.
The coordinator starts its 600-second deadline when it dispatches, then calls
interrupt_agent at that deadline. A timeout is incomplete feedback. Do not
run codex exec or another Codex CLI from Codex. If route availability is
provisional, preserve the observation as unknown; it does not establish a
completed review. Use --risk critical only for an explicit critical risk. An
already-dispatched reviewer executes the review directly and does not dispatch
another reviewer.

Its prompt supplies the exact target worktree, pinned base, intended behavior,
affected callers, and full relevant diff. For a repair batch it also supplies
the REVIEW_REPAIR_PACKET path and rendered content, asking the child to verify
self-review, behavioral-regression, and affected failure-path evidence; it
classifies each new blocker as repair-introduced, previously missed, or changed
requirements with a concrete consequence. It also appends the complete
## Classes section of $RUBRIC (from that heading to the end of the file),
the same rubric co-review seats receive, and asks the child to probe its
classes, apply the lenses its path table selects, and report an
Architecture section as it describes. Require blocking findings, useful
advisory findings, safe reproduction evidence, and coverage gaps. Its prompt
permits relevant reference skills for language, security, framework and
architecture guidance. This review scope,
material-impact threshold and read-only authority take precedence over that
guidance. Require the reviewer to perform the review itself; do not launch
another review workflow, delegate reviewers, modify code or publish findings.
Do not invoke co-review, partners, markers, external posts, or fixes.

Treat a confirmed major, high, or critical defect as blocking only when it has
a concrete material consequence for intended behavior, caller contracts, data,
security, lifecycle, or required integration. Require the finding to state
that impact; a written rule or TODO-like token alone is insufficient. Minor,
low, nit, taste, and speculative findings are advisory. A timeout, empty report, unknown completion,
unknown evidence, or material coverage gap is incomplete feedback, never a
clean review.

Report findings with severity, location, scenario, and evidence. Separate
blocking findings, advisory findings, and unresolved evidence gaps. Do not
invoke co-review, partners, markers, external posts, or fixes.

A repair packet's self-review is evidence only and never grants approval. A
complete clean review supports only task-local readiness and cannot renew a
bounded --fix allowance or replace its follow-up verification. An exhausted
allowance stops the outer development/shipping workflow too; diagnosis, a new
head, or a resumed session cannot reset it. Return control to the user.

Only a complete report with no blockers can support existing Herd task-local
readiness. A task-local readiness result is never PR approval, merge authority,
or a PR approval marker.