Workflow

Identify the invariant owner first. Keep the relevant domain skill loaded when the task is really auth, self-service, checkout, reservation, or admin behavior.
Treat storage/app/booking_release/openapi-v1.json and generated consumer artifacts as the only official frontend contract sources.
When a request or response shape changes, update contract metadata, generated artifacts, and FE-facing docs in the same batch.
Keep the default success envelope stable: { data: ... } or { data: [...], meta: ... } for collections.
Keep machine-readable error behavior stable: error_code, message, request_id, and errors when validation details exist.
When enum or state fields change, expose them through explicit schema, examples, or generated SDK types instead of expecting FE to infer values from incidental strings.
Keep row_version, Idempotency-Key, and X-Session-Id requirements visible in mutation contract outputs when they matter to browser clients.

Read AGENTS.md, .codex/AGENTS.md, and references/paths.md before editing.

Identify the invariant owner first. Keep the relevant domain skill loaded when the task is really auth, self-service, checkout, reservation, or admin behavior.
Treat storage/app/booking_release/openapi-v1.json and generated consumer artifacts as the only official frontend contract sources.
When a request or response shape changes, update contract metadata, generated artifacts, and FE-facing docs in the same batch.
Keep the default success envelope stable: { data: ... } or { data: [...], meta: ... } for collections.
Keep machine-readable error behavior stable: error_code, message, request_id, and errors when validation details exist.
When enum or state fields change, expose them through explicit schema, examples, or generated SDK types instead of expecting FE to infer values from incidental strings.
Keep row_version, Idempotency-Key, and X-Session-Id requirements visible in mutation contract outputs when they matter to browser clients.

RestaurantPOS Web Client Contracts