Maurice
f4bbb0fe5d
The ways of driving one leg come from OSRM, except the toll-free or motorway-free offer beside them: the shipped OSRM hosts are built without excludable road classes and answer exclude= with HTTP 400, so that one is asked of the avoidance router instead. Their figures were then read against each other. The quickest was elected across both, which is what decides the road drawn as the one being driven, and every other road was labelled with how far behind that election it sat. The two engines agree on the road to a tenth of a percent and not at all on how fast it may be driven: over twelve European legs the per-leg time ran from 14.7 % under OSRM's to 13.2 % over, with the sign following the region. On a Spanish motorway leg that gap alone is enough to crown a toll-free detour and call the motorway somebody is on the slow way round. An offer now carries the engine that timed it. It takes no part in electing the quickest, no difference is printed across the two, and the bar says where the figure came from. Each route still reports its own time; only the subtraction is refused. An instance running its own OSRM through the MLD pipeline answers exclude itself, so there both figures are one engine's and the comparison works exactly as before.
@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.