# MVP-TASK-035 — Journey 001 executable demonstration

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

## Objective and required behavior

Add one real-app Playwright journey in which an authenticated user creates a product, an operator
sells it through successful fake checkout, and its kitchen shorthand appears in the queue.

## Scope, areas, and non-goals

Expected E2E fixtures/spec only plus defects exposed by the journey. Do not duplicate every story
edge case, call Surfboard Demo or Live, or treat this as missing lower-level evidence.

## Evidence and acceptance

Test title includes `MVP-JRN-001` and relevant scenario IDs where one test directly proves them.
Accept when real frontend/backend/PostgreSQL plus fake adapter complete the demonstration reliably,
traceability is current, and inherited DoD passes. Handoff records fixture lifecycle.

## Implementation record

`tests/e2e/journeys.spec.ts` carries one headline test tagged with `MVP-JRN-001` and the exact
linked scenario IDs it directly proves. An isolated authenticated user creates a labeled product
through the administration UI, sees that persisted product in order entry, taps one unit, completes
a real commercial finalization through the deterministic fake, receives a new empty cart, and sees
the captured kitchen shorthand on the queued slip. The journey then advances its order through
delivery so it leaves the active queue; the finalized order and checkout history remain immutable,
while the mutable catalog fixture and synthetic user are removed. Teardown also moves an interrupted
active fixture out of the detailed-slip window so a failed run cannot poison later queue tests.

The focused Playwright run passes in desktop and mobile Chromium against the real frontend, backend,
and PostgreSQL. Full inherited validation and hosted CI remain outstanding, so the task is
Implemented rather than Done.