AgileWebs/kitchen-ops-bff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(kitchen-ops-bff): align lifecycle board reads

Browse Source
This commit is contained in:
José René White Enciso 2026-03-31 19:59:32 -06:00
parent b6b6c8fcf6
commit 6d4251b3b3
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/api/kitchen-ops-workflows.md
View File

@ -31,5 +31,6 @@ This BFF exposes kitchen board, claim or release, transition, and priority workf
- `kitchen-service` currently exposes claim but not a dedicated release contract, so the release route reuses the claim validation path and projects a release-oriented response for the BFF edge.
- Transition requests now forward `ContextId` to `kitchen-service` so kitchen actions land in the correct shared restaurant lifecycle context.
- Board reads now rely on the lifecycle-driven kitchen ticket materialization in `kitchen-service`, which means newly accepted restaurant orders can appear without a stack reset.
- The BFF keeps temporary edge-state compatibility for existing web clients by translating `Cooking|Ready|Served` to the canonical kitchen-service states `Preparing|ReadyForPickup|Delivered`.
- Correlation IDs are preserved through Thalos session checks and kitchen-service calls.

2
tests/Kitchen.Ops.Bff.Application.UnitTests/KitchenWorkflowServiceClientTests.cs
View File

@ -124,7 +124,7 @@ public sealed class KitchenWorkflowServiceClientTests
private const string BoardPayload = """
{
"contextId": "demo-context",
"summary": "Kitchen board shows queued, preparing, and ready lanes for the current service context.",
"summary": "Kitchen board now reflects persisted tickets linked to shared restaurant orders.",
"lanes": [
{
"lane": "queued",