# Containerization Runbook

## Image Build

If the repo consumes internal packages from Gitea, pass feed credentials as build args.

```bash
docker build   --build-arg NUGET_FEED_USERNAME=<gitea-login>   --build-arg NUGET_FEED_TOKEN=<gitea-token>   -t agilewebs/kitchen-service:dev .
```

## Local Run

```bash
docker run --rm -p 8080:8080 --name kitchen-service agilewebs/kitchen-service:dev
```

## Health Probe

- Path: `/health`
- Fallback path: `/healthz`
- Port: `8080`

## Runtime Notes

- Exposes internal queue and order state transition endpoints.
- Also exposes board, work-item claim, and priority update endpoints for the kitchen-ops BFF flow.

## Health Endpoint Consistency

- Canonical probe: `/health`
- Compatibility probe: `/healthz`
- Container port: `8080`

## Demo Integration

- Participates in: **restaurant** demo compose stack.
- Integration artifact path: `greenfield/demo/restaurant/docker-compose.yml`
## Known Limitations

- Current runtime adapters are still predominantly in-memory for deterministic local/demo behavior.
- Demo PostgreSQL seeds validate integration contracts and smoke determinism, but do not yet imply full persistence implementation parity.
- Stage 41 adds kitchen workflow contract depth first; downstream BFFs still need to adopt these endpoints before richer board behavior reaches the web app.