Maurice
fa29ee9ea4
A chapter of several entries used to set the story of its first entry only. Its words now flow in reading order from the opener or the panorama onto the pages after it: the first entry's story, its pros and cons, then every further entry's story under a small heading of its title, else its place or date. A quiet page without a photo runs its column on across both pages, and the planner gives a chapter as many pages for words as its stories need. A chapter that tells a story opens on a hero or a panorama only when a page for its words follows. Pros and cons with no room where they fall wait for a later page that takes words. What the pages cannot hold is said once for the whole book, named by entry, ahead of the notes on stories cut to fit, and an entry two chapters share is told once.
@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.