Release-cut documentation sweep (do with the next develop→main release)

[DocGerd]

Process task, to be executed as part of cutting the next release (not before): audit and update all documentation so it matches the released state.

Checklist at cut time

• README.md — feature list, screenshots, badges, links reflect the release (incl. new user-visible features since v0.3.0: departure time on saved-route cards Routes list cards should show the planned departure time #112, build-time version in About Show the running app version in the UI #125, deploy hardening Harden deploy: prevent a develop push from being able to change production bytes, and make prod stability legible in the Deployments UI #117/Rename the "github-pages" deployment environment to "prod" (or equivalent legibility fix) #127 if user-relevant).
• CHANGELOG.md (CHANGELOG.md (Keep a Changelog) + changelog visible in the app #131, if landed by then) — roll Unreleased into the new [X.Y.Z] - date section; if CHANGELOG.md (Keep a Changelog) + changelog visible in the app #131 hasn't landed, note the release in its backfill scope instead.
• CLAUDE.md — deploy/branching/verification sections still accurate after this cycle's workflow changes (scorecard trigger scorecard.yml: restrict push trigger to develop (main pushes fail by design) #124, deploy.yml prod-dist reuse / dual smoke-probe / prod env record Harden deploy: prevent a develop push from being able to change production bytes, and make prod stability legible in the Deployments UI #117+Rename the "github-pages" deployment environment to "prod" (or equivalent legibility fix) #127, fetch-depth Show the running app version in the UI #125).
• docs/superpowers/specs/ — no silent drift: if released behavior deviates from the design doc, the spec needs a user-approved addendum (spec edits are main-session/user-gated — flag, don't auto-edit).
• GitHub Release notes — written from the changelog, user-relevant framing, passage-planning-aid disclaimer intact.
• In-app copy/i18n — no stale version-specific or feature-stale strings (de/en parity).
• THIRD-PARTY-NOTICES.txt — verify committed file is current (CI-enforced; just confirm green).

Notes

• Trigger: next release cut. Keep open until that release's PR merges; close with it.
• The release itself remains user-approved and user-run per repo process (walkthrough gate before opening the release PR).