Maurice
0879b5aecc
auto/auto-designed.ts holds what the Studio's Auto layout menu calls. autoDesignedBook lays the whole book on the designed templates in the book's own theme object (a recoloured one of its own included, the calm fabric-classic theme for a book without one), over the stored book, its page format kept and every page holding a locked element kept; another seed lays another book. autoRelayoutSpread lays one page again around its locks, its id kept: an entry's page on the best template other than the one on screen and its neighbours', avoiding one that would cut its story where it can; the cover on the next cover template of its archetype and then of its kin; the summary and the countries in their next look, an old classic summary included. Pages the engine did not make are left alone, as before. autoRelayoutKind says which pages those are. designBook's templated path is split so the relayout reads the same setting (templatedSetting) as the whole book, and the page layer is shared (layEntryPage); the parity digests are unchanged by it. buildBook and relayoutSpread stay exported and 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.