Linking a gallery photo to an entry and taking it off told nobody, so other tabs, and the journey page after an assistant change, stayed as they were. Both now go through a photo links service that broadcasts journey:entry:updated after the write, with the asking socket left out on REST; a caption change through PATCH photos/:id broadcasts journey:updated the same way. The service also moves photos from one entry to another of the same journey in one transaction, as POST /api/journeys/entries/:entryId/photos/move, with a strict contract. The MCP tools link_journey_photo, unlink_journey_photo, move_journey_photos and set_journey_photo_caption call the same methods; the caption tool answers the caption it replaced.
@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.