# MVP-ORD-002 — Add operational metadata

## Story

As an operator, I want optional kitchen metadata and an eat-here/take-away choice so that
fulfillment has the information it needs.

## Scenarios

### MVP-ORD-002-S01 — Optional fields may be absent

- **Given** no queue number and no note
- **When** a valid order is finalized
- **Then** finalization succeeds and neither value is fabricated
- **Evidence:** E2E plus integration.

### MVP-ORD-002-S02 — Queue number is captured

- **Given** the operator enters a queue number
- **When** the order is finalized
- **Then** that optional display value is associated with the order
- **Evidence:** E2E/integration.

### MVP-ORD-002-S03 — Leading zeroes are preserved

- **Given** queue number `01`
- **When** the order is finalized and displayed
- **Then** it remains `01`
- **Evidence:** E2E/integration.

### MVP-ORD-002-S04 — Duplicate queue numbers are accepted

- **Given** an active order already has a queue number
- **When** another order uses the same value
- **Then** both remain distinct through immutable internal IDs
- **Evidence:** integration plus queue E2E.

### MVP-ORD-002-S05 — Optional note is captured

- **Given** an order-level note
- **When** the order is finalized
- **Then** the note is available to kitchen presentation
- **Evidence:** E2E/integration.

### MVP-ORD-002-S06 — Eat-here/take-away is captured

- **Given** the operator selects eat here or take away
- **When** the order is finalized
- **Then** the selected minimal order metadata is preserved
- **Evidence:** E2E/integration.

## Invariants and exclusions

Queue number is never identity or unique. No generalized fulfillment channel/location model.

## Implementation tasks

[MVP-TASK-010](../tasks/MVP-TASK-010.md) and [MVP-TASK-024](../tasks/MVP-TASK-024.md).