v0.6.0

v0.6.0

[0.6.0] — 2026-06-11

Added

• references/review-record.md — makes AI review trustworthy and auditable. (1) Reviewer dispatch constraints grounded in the published self-review-bias evidence (three mechanisms: in-context ownership / style familiarity / family-taste correlation — a fresh-context same-family reviewer removes the largest term and leaves a residual the rest of the rules compress): fresh context always, read-only tools, explicit tier ≥ implementer's, refute-first output with the verdict field LAST, file:line + quoted-snippet evidence gate per finding, controller-computed verdicts (never a reviewer-stated "approved"), unanchored pass before any pre-seeded suspicions, lenses-not-clones for multi-reviewer passes. (2) The bidirectional review record on every PR where reviewer subagents ran: comment A = each round's report verbatim (writer must not condense it — a live "verbatim" comment silently dropped ~60% of the reviewer's reasoning) with SHA-range scope header + "not reviewed" list + dispatch-prompt provenance; comment B = builder per-finding response (agree/disagree + why, severity re-graded by actual impact, what changed with SHA, deliberate non-changes, net judgment). (3) Finding→fix rules: mechanically-verifiable → fix vs judgment-call → human ("Reviewer asks"); one review-fix = one commit; reviewer-suggested fix code is untrusted input (a pasted snippet caused real silent data loss on the first live track; adopt the finding, re-derive the fix, add a test); review-fixes are unreviewed code → mandatory final-pass round. (4) Coverage-window check (git log <last-review-SHA>..HEAD empty before merge) and the catch-parity ledger feeding the close-gate: pr-boundary experiment. Wired into SKILL.md (Reviews conventions, Red Flags, reference index, superpowers note), references/cadence.md steps 2/3/4, references/close-gate.md §"Approval timing", and references/pr-comment-template.md (two new companion-comment drafts in the draft-first tree). The draft-first section additionally requires PR-thread content (bodies, comments, review records) to pass the project's language + leak gates BEFORE the gh call — posted content is published and invisible to git-side hooks. Source: dogfood pr-boundary track 1 (two review rounds, each caught one real issue; six field findings) + cited bias research.

Changed

• README.md + README.zh-CN.md — reference trees and the policy-key example block caught up with shipped features: review-record.md + parallel-work.md entries added; roadmap.md (status-file ring), close-gate.md (approval-timing key), pr-comment-template.md (review-record companions), and output-format.md (key list) lines updated; close-gate: per-task added to the CLAUDE.md policy-key example.

---

---

Full history: see CHANGELOG.md

What's Changed

✨ New Features & References

• feat(references): add review-record.md — trustworthy, auditable AI review by @Victoriakaey in #6

Full Changelog: v0.5.0...v0.6.0