web feat/booking-ui
stubbing GET /api/legs behind a flag until somebody claims it
goal: Booking flow in the web app
declared Put the numeric booking id in the confirmation URL so it is shorter to share
wr web/booking_form.tsx
wr web/api_client.ts
Entanglement
Sessions on the left, the things they touch on the right. Where two sessions reach the same thing, that node is the collision — and it is drawn the way the mark draws it: two strokes crossing.
✳ 1 node nobody is building ◆ 2 shared nodes 7 attachments
a session — coral or indigo, one per side an area of the repo touched by two sessions — the crossing consumed, nobody producing
◆ critical nobody is building this 6d and still nobody is building GET /api/legs. Devesh Rao · web has two files waiting on it. Take it or cut it — now, not at integration. 2 open conflicts →
api feat/booking-api
reading the existing router
goal: Ship the booking write path end to end
active Implement POST /api/bookings and its handler
wr api/bookings.go
wr api/router.go
wr api/bookings_store.go
tests feat/booking-api
14 cases green, 2 red on the idempotency path
goal: Table tests for the bookings handler
active Table tests for the bookings handler, including the idempotency path
rd api/bookings.go
infra chore/booking-deploy
chart merged to chore/booking-deploy
goal: Get the booking service deployable
done Add the Helm chart and wire the booking service route