Review report

Use a linked LOG or DOC with data.kind=review-report and the originating task/run identity when available.

## Result and changed behavior
## Task/spec/selected artifact and influencing lessons
## Base/head/worktree and actual changed files
## Acceptance evidence
| Criterion | Result | Actual observation/output | Timestamp/revision |
## Checks
| Command and directory | Exit/result | Output path | Limitations |
## Decisions, deviations and unresolved work
## Documentation verified/stale/proposed
## Owner review / separate delivery decision

Example: “The real worktree contains the new result file, and the replay fixture passed. No installed provider completed this task; the adapter was simulated. Task remains Review; Git HEAD and remote were not changed.”

Use a fresh task revision before transitioning to review. If a check failed, record it and the actual state rather than applying a success label. Do not embed raw credentials or unrelated transcripts in evidence. Large outputs should be linked through approved local/file records.