15 lines
849 B
Markdown
15 lines
849 B
Markdown
# Handoff guide
|
|
|
|
## Documentation
|
|
|
|
- Update the current-behavior contract only for behavior verified on the candidate. Keep proposed work clearly proposed.
|
|
- Record one disposition: `updated`, `not_required` with a concrete reason, `deferred`, or `blocked`.
|
|
- Put run-specific logs, screenshots, and command results in the review handoff, not the enduring contract, unless the contract explicitly depends on one identified run.
|
|
|
|
## Review content
|
|
|
|
- Summarize the user-visible change and its bounded impact.
|
|
- Name the candidate revision and the focused checks run against it, with observed pass or failure results.
|
|
- Give a reviewer executable steps and expected observations for any behavior that automated checks cannot establish.
|
|
- State remaining uncertainty and recovery steps. Attribute provider or Human observations to their actual source.
|