- The phone's admin sections follow the desktop sidebar: the same groups (Users, Configuration, Maintenance) in its dropdown, Security and Services instead of one Settings section, and live flights and booking mails beside the addons they configure. An old ?tab=settings link still opens Security. - Passkey login and the 2FA rule sit with the other ways in; the passkey card keeps the domain, and a managed install no longer shows the danger zone. - MAdminSelect replaces every native select on the admin screens: TREK's own field or row pill that opens the picker sheet (permissions, backup schedule, invite trip, plugin settings). - Explanations wait behind an info mark (MHintLabel), as on the desktop: admin rows and fields, the settings rows' new `hint`, addon and provider rows. - Permissions are one line each with the level as a pill; addon rows lose the type badge their heading already names; settings buttons no longer wrap. - "Require 2FA" in every language; admin.tabs.settings is unused and gone.
@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.