Marc-André Bombeck 87877b285f fix(share): date a shared PDF by the owner's day, not the display default ...

The page at c/[token] resolved the owner's timezone; the PDF download beside
it resolved nothing and fell through to the display default. Same link, same
reading, two dates — and the one a practice files is the one that was wrong.

Resolved in the shared download gate rather than in the route, so the PDF and
the FHIR bundle cannot drift apart the way the page and the PDF did. The
owner's clock preference travels with it for the same reason.

The fixture is deliberately west of UTC: Berlin is the fallback, so a Berlin
fixture cannot tell a resolved timezone from a forgotten one.

2026-07-26 22:37:10 +02:00

..

[token]

fix(share): date a shared PDF by the owner's day, not the display default

2026-07-26 22:37:10 +02:00

error.tsx

feat(sharing): add an error boundary to the public share route

2026-06-28 11:53:52 +02:00