Read this first. It is self-contained. You should not need anything outside this file plus repo access to continue this work.
We are adding a guest checkout path so buyers can complete an order without creating an account. The database layer and the order-total logic are done and tested; the HTTP route that ties them together is stubbed but not wired. This document tells you exactly what is true, what to verify, and what to do next.
| Fact | Value | Verify |
|—|—|—|
| Branch | feature/guest-checkout | git rev-parse --abbrev-ref HEAD |
| True at commit | a1b2c3d4e5f6 | git log a1b2c3d4e5f6..HEAD --oneline (empty means nothing drifted) |
| Open PR | https://github.com/acme/store/pull/812 (draft) | gh pr view 812 |
| Worktree? | no | n/a |
| Tickets | STORE-441, STORE-442 in progress | grep -n 'In progress' TASKS.md |
| Claim | Verify |
|—|—|
| guest_orders table migration exists but has not been applied to preview | ls migrations/ | grep guest_orders |
| Order-total logic handles guest tax the same as member tax | npm test -- order-total |
| The /api/guest-order route returns a hardcoded stub | grep -n 'STUB' src/routes/guestOrder.ts |
| Rate limiting on the route | [belief, unverified] — not yet added, confirm before launch |
docs/CHECKOUT_SPEC.md, for the intended behavior. Its section on saved payment methods is out of date since we descoped that (see section 4).test/guest-checkout/, for the contract the code actually meets.Order model directly for guest orders. It failed because the model requires a non-null user_id at the database level, and making it nullable broke three member-side queries. The guest path gets its own table instead.guest_orders table rather than a nullable column on orders, because it keeps member queries unchanged and isolates the guest data for later cleanup./api/guest-order route at the new table (replace the stub). This is also the header first_action.verify_cmd passes.npm test -- guest-checkout && npm run typecheck