Public trip and journey share links handed out more than the owner chose to
share:
- A travel-only trip link still returned every day's title, and every link with
the map returned the free-text day notes the shared page never shows. Days now
go out through a public projection without notes, and travel-only links carry
no day titles. Day notes, packing, budget and chat use explicit field lists
too, and the category list holds only the categories the shared places use,
without creator ids.
- The public journey payload spread whole entry and photo rows, including
storage keys (file_path, thumbnail_path) and internal fields. It is now built
from allow-lists and pinned by a strict response contract.
- /uploads/journey served every entry photo, original and video to anyone who
knew the file name, so a URL kept working after a share link was revoked or
the gallery switched off. It now serves journey covers and other non-entry
objects only; entry media go through the token-checked proxy.
- Anonymous byte paths served stored originals unchanged, so EXIF GPS left the
server even with map sharing off. Every public path (journey share proxy,
covers, trip share photos, public uploads) now sends a copy with location
data blanked in place (EXIF GPS, XMP and IPTC location, MP4/MOV location
atoms), falling back to a metadata-free re-encode or a 404, never the raw
file. Owners and members still get their originals.
- An entry's visibility field never decided the share link but was offered by
MCP and the assistant as if it did. It is now documented as having no effect
and no longer shown as a privacy label; is_draft keeps an entry off the link.
- Paddle as a plannable tour type: one boat (kayak, canoe, SUP, other), river or
lake, a pace that a boat change never overwrites; time is distance over pace
- Hand-drawn legs beside routed ones, drawn dotted and labelled as not routed,
kept through save, reopen and edits elsewhere
- Reverse a tour and close it back to its start, each one undo step
- GPX import shows a preview first (line, measures, duplicates, type) and only
the confirmation stores the tour
- Base maps and overlays per tour type in the planner: hike keeps topo and the
via ferrata layer, paddle gets the OpenSeaMap seamark overlay
A response-contract-exempt comment counted any handler as covered, whatever it returned, so one comment line let a JSON handler past the ratchet. The marker now counts only on a handler taking @Res() or @Next(). The five vacay holiday proxies return the provider's JSON, so they lose their markers and are counted again until they declare a schema.
The vacay plan, calendars, years, entries, stats and shares, and the
journey list, create, tracks, stats, share link and every success answer
get response schemas in shared and a @ResponseContract on their handler.
The holiday proxies pass the provider's answer through and are marked
exempt. The journey e2e stubs return whole rows, as the service does.
shared gains the response schemas these routes answer with (rows in their
storage spelling, as the routes have always sent them) plus the common
success and empty answers, all exported for the client to type its calls
with. Every JSON handler in the four controllers carries its
@ResponseContract; the file download, which streams, is marked exempt. The
files e2e fixture table gains the note_id column the real one has.
The decorator records the @trek/shared response schema a route answers
with. Under NODE_ENV=test it adds an interceptor that parses every response
and fails the request with a logged 500 naming the handler and the issues,
so the e2e and integration suites catch a response that drifted from its
contract; in production nothing is added to the request path and the body
is never rewritten. lint:response-contracts holds the handlers still without
one to a per-file baseline that only shrinks, and runs in server-quality.