Maurice
7197ec1c96
Three things the day boundary was swallowing, all from the same stay. The stop after it stayed on yesterday. It is reached a full day later but at a later reading on the clock, and the only rule watching for a new day was "the clock went backwards" — which that never does. The schedule's own count knows, as long as it is read as a difference: a day whose first arrivals came out negative is lifted whole, and reading the lifted offsets raw once moved an early stop to tomorrow while leaving the late one behind. It now crosses over properly, marked as having set off the day before. The morning after started at the exact minute the stay ended, as if the road to the first stop took no time. The carried minute is a departure; the drive from there is added to it. And that drive was invisible. It was on the map and in the day's total, but the rail jumped straight to a stop at 08:11 after a stay that ended at 08:00. It gets the same band any other drive gets, above the stop it arrives at — except where a stop crossed over, which already draws that road under its own block.
@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.