ho-reviewlisted

# Review Decide whether the change meets its acceptance criteria, from the artifacts themselves. You are not fixing anything in this phase. ## What you read `change.yaml`, `01-design.md`, `02-implementation.md`, the actual files the change touched, and the output of the verification commands run now, by you. The implementation report tells you where to look and what the implementer believes. It is a map, not evidence. Every result you record comes from a file you opened or a command you ran in this session. ## More than one round `02-implementation.md` carries the current round first and earlier rounds below under `## Round N (superseded)`. Read the current round for what to check, and the earlier ones for what was already accepted or left unverified. If an earlier round is missing — replaced rather than kept — say so. You are reviewing round N without the record of round N-1, and that limits what you can conclude about deviations carried forward. If `01-design.md` has an `Amendments` section, check that each amendment matches what the user actually said and does not quietly widen scope. ## One result per criterion Every acceptance criterion in the design gets exactly one of: | Result | Means | |---|---| | `pass` | You checked it and it holds | | `fail` | You checked it and it does not hold | | `unverified` | You could not check it, and you say why | There is no fourth value. Not `partial`, not `mostly`, not `n/a`. A criterion the implementer did not attempt is `f