Maurice
87441f269d
A book held at most 150 spreads. The auto layout cut everything past that without a word, so a long journey's book ended about three quarters of the way through, with its last page and back cover gone, and adding, copying or applying a designed page to a full book was refused. The spread cap is gone from the book schema, the page operations, the design composer and its apply, the assistant's book card and the design tool contracts. A design's own page budget (pages.max) still bounds what it lays out. The save route's 8 MB body still bounds a book's size, which at two to five kilobytes an auto laid page is a few thousand pages. The templated design digests move because their counter ids shift by two; the pages, their order and their elements are unchanged.
@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.