RemEx
e0c9a8d1b6
The settle-up view says who owes whom, but nothing on the Costs screen answers "what did the trip cost me": the balances move every time a payment is recorded, and the tiles only describe the signed-in user. The settlement response now carries finalBudgets, one row per participant in the ledger: expenses (what they fronted on split expenses), reimbursed (recorded transfers, received minus sent), pending (their current balance) and final = expenses - reimbursed - pending. - Computed in calculateSettlement from the same integer trip cents as the balances, filled by the same loops, so the breakdown can never contradict the balance printed next to it. Each component is converted to the display currency as its own set and the final is subtracted in display cents, so the three lines add up to the total in any currency. - A "Final budget" card on desktop, the narrow desktop layout and the mobile Costs tab: one amount per traveler, and a tap opens the three lines plus the expenses, transfers and open flows behind them. The filtering lives in CostsPanel.helpers so both shells share it. - Contract in shared (budgetParticipantFinalSchema); the MCP get_settlement_summary description mentions the new field it returns. - Four new costs.* keys, translated in every locale.
@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.