bear
8d10bff616
- create_transit_journey takes price / budget_category, as create_transport does: a fare > 0 files the linked expense in the booking's own transaction and rides along in metadata.price. The tool now writes through ReservationWritesService.createBooking, so its events and booking notice are the ones every other booking write sends - create_budget_item and create_budget_item_with_members take reservation_id, the field POST /budget already accepts; create_budget_item now runs BudgetWritesService.createItem like its sibling, so a linked booking's mirrored price is worked out again before budget:created goes out - bookingPriceSchema / bookingBudgetCategorySchema in @trek/shared back the price fields of all three booking tools (mcp-inline-zod baseline lowered) - wiki: MCP-Tools-and-Resources describes the new params
@trek/shared
Single source of truth for TREK's API contracts, expressed as Zod schemas and consumed by both the server (request validation + inferred DTO types) and the client (typed requests/responses).
This package is part of the incremental NestJS + React 19 migration (see the "Brownfield Rewrite" board). It is intentionally dormant until modules start importing it — adding it changes nothing for users.
Rules
- One folder per domain:
src/<domain>/<domain>.schema.ts(+.spec.ts). - Domain-agnostic building blocks live in
src/common/. - A route is only considered migrated once its contract lives here.
- Schemas are the source of truth; server DTOs and client types are inferred from them
(
z.infer<typeof schema>), never hand-duplicated.
Consumption (dev)
Both apps resolve @trek/shared to this package's TypeScript source:
- Server (
tsx): viapathsinserver/tsconfig.json. - Client (
vite): viaresolve.aliasinclient/vite.config.ts(+pathsfor the type-checker).
Production packaging (Docker / workspace wiring) is introduced in card F2, when the server first depends on this package at runtime. Until then prod builds are untouched.
Not yet here
The canonical error envelope is finalised in card F5 (it must match TREK's current Express error responses byte-for-byte), so it is deliberately not invented in F1.