Maurice
e5f1f573c5
The assistant offered 25 hand-picked tools. It now offers every tool the MCP registry holds, but a short denylist with a reason per tool (deleting the trip, share, invite and feed links, membership changes, fetching an address the model picks, documents to the provider, instance-wide categories and holidays). The scopes widen to every addon but trips:delete, the share scopes, file contents and plugins. - A tool annotated read-only runs at once, every other one waits as a change card; reads that fetch a planted address wait too. - A turn starts with the trip's core tools; use_addon_tools loads tours, road trip, journey, vacay, atlas, collections, trip chat, files, account or plugin tools for the rest of the turn. - A writing tool without a card of its own gets one from its arguments: add, change or remove, the part of TREK it works in, the trip's days, places and people named. - The boot check fails on a tool that shares, invites or publishes and is neither denied nor known to only take back.
@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.