manual page/ Tutorial
Review
- Sections
- 5
- Format
- Markdown
- Order
- 14 / 156
This page creates:
reviews/checkout-expiry.md
Use a reviewer that did not implement the change.
Create the packet
---
type: review
id: REVIEW-checkout-expiry
task: TASK-checkout-expiry
pr: none yet
reviewer: you
status: draft
---
# Review: Expired checkout session returns 409
Add coverage
The task scope has one requirement, so the table has one row:
## Requirement coverage
| ID | Result | Evidence | Human attention |
| --- | --- | --- | --- |
| AC-001 | Pass | `npm run test:integration -- expired-session` -> `Tests: 3 passed, 3 total` | yes |
This is Pass because evidence is present.
If evidence is empty, the result is Unverified.
Spot-check
Record one green-row check:
Spot-checked: AC-001 - reran `npm run test:integration -- expired-session`; output matched the evidence row.
For this fictional shop-api, the command is illustrative. In your repo, run it.
Route human attention
Checkout is a money path. Keep one attention item:
## Human attention
1. Risky path: checkout validates the session before charging. Confirm the 409 path runs before any charge call.
Decide
## Suggested decision
Merge. AC-001 passes with evidence. Review the money-path note before merging.
Set frontmatter:
status: pass
Check:
- one row for
AC-001 - evidence cell has output
- spot-check recorded
- human-attention item names the risk
- reviewer is independent
Next: Close.
Starter kit: Set up a workspace