# MVP-TASK-037 — Journey 003 non-commercial service loop

**Status:** Implemented  
**Parent:** MVP-JRN-003 and its linked story scenarios

## Objective and required behavior

Demonstrate rapid order entry, explicit non-commercial finalization with optional metadata, zero
checkout calls, common queue/fulfillment, immediate next cart, and unchanged commercial ticker.

## Scope, areas, and non-goals

Expected Playwright journey with deterministic checkout spy plus linked integration evidence. No
reason enum or separate non-commercial fulfillment implementation.

## Evidence and acceptance

Test title includes `MVP-JRN-003`; direct scenario proofs carry their IDs. Accept when one common
operational loop works and checkout/sales exclusions are explicit, traceability is current, and
inherited DoD passes. Handoff records how no-call evidence is established.

## Implementation record

`tests/e2e/journeys.spec.ts` carries one headline test tagged `MVP-JRN-003` and the exact linked
scenario IDs it directly proves. Rapid product taps build the cart, optional queue number, note, and
eat-here choice accompany the explicit non-commercial finalization, and the order enters `Queued`
through the common fulfillment flow, receives the next empty cart, and advances through `Preparing`,
`Ready`, and `Delivered` with the same forward controls as a commercial order until it leaves the
active queue. The commercial ticker is unchanged throughout.

No-call evidence is established three ways in the browser journey: a request listener installed
before sign-in records every mutating checkout/payment-path request (the authenticated
`GET /api/checkout/unresolved` screen read is deliberately excluded because it never contacts a
provider) and asserts the list is empty; a counter asserts the commercial finalization endpoint was
never called; and a database read asserts the finalized order has no checkout-attempt row. The
linked real-PostgreSQL `postgres-order-repository.integration.test.ts` suite owns the durable
classification and sales-exclusion facts for the journey. Full inherited validation and hosted CI
remain outstanding, so the task is Implemented rather than Done.