Updates

Changelog

Every fix, feature and update — so you can see exactly what we've been suffering over.

v1.35.0

MinorNov 2, 2026

New

—Season calendar feed (`lib/calendar/*`, `app/api/v1/me/calendar`, `app/api/calendar/feed/[token]`, migration 0036): a rider subscribes to their season in Apple Calendar or any calendar app. Race days plus known entry open and close dates, stable event ids, skipped races and awaiting editions left out.
—The feed link is a 32-byte token stored only as its hash; `POST` creates or rotates it, `DELETE` revokes it, an unknown or revoked link answers 404. API v1 answers carry `X-PainPlan-Api: 1`.

Changed

—The site-wide no-store header skips `/api/calendar/feed/`, so the feed keeps `private, max-age=900` and its 404 keeps `no-store`.

v1.34.1

PatchNov 2, 2026

Changed

—The last screens say "My season": user menu, footer, calendar empty state and profile.
—Help page in the brand voice: no "suffering", no "community", no exclamation marks; the category is "Crews".
—"Sign in to rate this race" has its missing space back (it read "Sign into rate").

v1.34.0

MinorNov 2, 2026

Fixed

—Signed-in riders no longer hit the React hydration error (#418): the header, bottom navigation and race actions wait for hydration before they show session state. Sign In appears once the page has hydrated.
—Route lines answer only for published races: `/api/races/[slug]/route-line` returns 404 with no-store for drafts and races awaiting enrichment, the same rule as the race page; the public cache applies to published races only.

v1.33.2

PatchNov 2, 2026

Fixed

—The build no longer downloads Google Fonts: Archivo, IBM Plex Mono, Newsreader, Overpass Mono and Space Grotesk are served from the repo (`app/fonts/`, OFL licences included) with the same subsets, weights and variables. A Google Fonts blip failed a prod build on 2 Nov; a build now needs no font network at all.

v1.33.1

PatchNov 2, 2026

Security

—Private crews are reachable only by their members: every crew API handler (16) checks membership before it reads or writes, and a private crew answers exactly like a missing one (404). Before, any signed-in rider could read a private crew's member names, race statuses and notes through the race-status route (found by the 1.31.0 security gate; present since crews shipped).
—A private crew's page title no longer shows its name or description to non-members.
—Join limiter: both join routes share one per-rider bucket; the per-address limit groups IPv6 by /64 through the waitlist's `clientIp`/`ipKey`; requests without an address get their own strict bucket; the limiter maps are capped.

v1.33.0

MinorNov 2, 2026

Fixed

—Race pages load without the React hydration error (#418) for signed-out visitors: cards that depend on the session (claim panel, FTP estimate, review form) wait for hydration through one shared hook.
—Race dates show the same day everywhere: stored days format in UTC, so Fred Whitton reads 9 May 2027 in Chicago too, not 8 May.

New

—e2e on three races at 390 and 1280 in UTC, Berlin and Chicago: the hydrated hero date matches the served HTML and the page throws no error.

Known

—Signed-in riders can still hit #418 through the header, bottom nav and race actions; next race-page round.

v1.32.0

MinorNov 2, 2026

Changed

—One name for the rider's season: the page is "My season" in headings, titles, navigation, back links and calls to action; "Saved Races" becomes "My season"; saving reads "Add to my season" / "Remove from my season" everywhere through `lib/copy/save-verb.ts`. The route stays `/my-races`.
—The entry-dates agenda's empty state links to "Find races" instead of a save verb that saved nothing.

New

—An e2e check that `#entry-dates` lands under the sticky header at 390 and 1280.

Known

—Old wording remains in the help page, stories, the user menu and footer, and two mail lines; next copy round.

v1.31.0

MinorNov 2, 2026

New

—`/crew/join`: one page to join a crew by code, with a preview of the crew; the old `/community/groups/join` redirects there (308, query kept).
—12-character invite codes from an alphabet without look-alike characters; every existing code keeps working.
—Join limits per rider and per address, checked before any lookup or write.
—Create buttons open the new-crew dialog; navigation says "Crews"; crew copy rewritten in the brand voice.

Known

—An older crew route lets any signed-in rider read a private crew's race plans; fixed in 1.33.1.

v1.30.0

MinorNov 2, 2026

New

—Deep links into race pages: `#est-time`, `#results`, `#history`, `#reviews`, `#course`, `#claim` scroll to their section under the sticky header, also when the section loads late.
—One save wording: "Add to my season", "In my season", "My season" on every rider-facing web string, from one copy file (`lib/copy/save-verb.ts`).

Fixed

—The review form no longer causes a React hydration error (#418). Other session-gated race-page cards still throw #418 on RiderMan and Nove Colli, and the race hero shows the day before for riders west of UTC (pre-existing); both are fixed in the next race-page round.

Known

—Old wording remains in mails, settings, help, stories and legal pages; next round.

v1.29.0

MinorNov 2, 2026

New

—Mail choices in /settings: four switches (entry opens, entry closing, ballot steps, race week) and the rider's time zone, stored from the browser on first visit and never over a zone the rider chose.
—Ballot-step mails and a race-week briefing, sent at 07:00 in the rider's own zone, once per rider, race and step; three variants of one event make one mail. Both are held in production until `MAIL_TYPES_LIVE` names them.
—Notification sidecar ticks every 15 minutes (was 6-hourly), so 07:00 lands within a quarter hour in every zone.
—Migration 0032: `notification_setting` and `user.time_zone`; old opt-outs carried over, push follows the email switch.

Fixed (before release)

—New mail types gated, links checked as safe, retries bounded; the entry-window source line reads the stored day.

v1.28.0

MinorNov 2, 2026

New

—Entry timeline on race pages: each entry step (opens, closes, ballot) with its date, local time and offset and its source, or "expected" where not sourced, then race day. Races without entry windows show nothing.
—`/my-races/dates`: the entry steps of a rider's saved races in date order.

Fixed (before release)

—A last edition's close date no longer shows as a step of the next edition: legacy registration columns count only when an edition has no windows of its own, and only for future dates before race day (RiderMan, Bodensee-Radmarathon, Swiss Epic).
—Stored days read in UTC, so a date stays the same day in every server time zone.

v1.27.0

MinorNov 2, 2026

New

—App waitlist with double opt-in (`lib/waitlist/*`, `/api/waitlist`, `/waitlist/confirm` and `/waitlist/unsubscribe`, migration 0033): one mail when the iPhone app is out, an optional TestFlight invite. Confirm and unsubscribe change data only on POST.
—Caps per inbox: 3 confirm mails per 24 h and 5 per pending cycle, 30 days quiet after unsubscribe, a global ceiling counted on real sends, IPv6 counted per /64, and one row per inbox (`email_canonical`: plus tags and Gmail dots folded). Bot filter, admin tile on `/admin`.
—Shut until `WAITLIST_OPEN=true` and `WAITLIST_SECRET` are set. The form component (`components/waitlist/waitlist-form.tsx`) is for the v9 landing build to mount. Way back: revert the merge; down SQL in the 0033 header.

v1.26.1

PatchNov 2, 2026

Fixed

—Alpha no longer runs the notification cron. Alpha shares the production database: a run there claimed sends in `notification_log` while alpha's mail switch kept them from going out, so production riders would never have received them. `/api/cron/notifications` answers 503 on alpha.

New

—A deploy pipeline beside Dokploy, off for production: GitHub Actions builds the image to GHCR, `deploy/pp-deploy.sh` rolls it out on the VPS with a health gate, Swarm rollback, a per-target image cleanup and a Discord alert; `deploy/switch-prod.sh` moves production over and back. Proven on alpha (rollback in seconds). Report and way back: `docs/reports/hosting-deploy-2026-11/index.html`.

v1.26.0

MinorNov 1, 2026

New

—Sign-in for the iPhone app. A 6-digit email code and native Sign in with Apple through Better Auth (pinned to 1.4.3, which the Expo plugin needs), and account deletion through the API. The web settings page gets a working "Delete account" row.
—Deleting an account needs a session younger than 24 hours or the password; a rider without a password signs in again first. Apple's token and revoke calls end after 10 seconds.
—One address gets at most 5 codes an hour and 20 a day (Redis, with an in-memory fallback). Trade: anyone can spend an address's 20 codes and block code sign-in for that address for up to a day; Apple, Google and password sign-in are unaffected.
—An unverified password is cleared when its owner signs in with Google.
—Apple stays off until `APPLE_SERVICE_ID`, `APPLE_TEAM_ID`, `APPLE_KEY_ID`, `APPLE_PRIVATE_KEY` and `IOS_BUNDLE_ID` are set.

v1.25.0

MinorNov 1, 2026

New

—The Pain Pass on the server. `entitlement` table and an `entitlement_event` ledger (migration 0037), one rule `hasPass()` in `lib/entitlements/has-pass.ts` for web and app, a RevenueCat webhook and `GET /api/v1/entitlements`.
—The webhook checks its shared secret before reading the body, caps bodies at 64 KB, applies each event once (idempotent per event id), ignores an older event that arrives late, and ends a Pass at once on a refund. A transfer between accounts is recorded only; a purchase changes owner only through an event about that purchase in the same environment.
—Sandbox purchases (TestFlight, App Review) count as a Pass in production on purpose.
—Off in production: the webhook answers 503 until `REVENUECAT_WEBHOOK_SECRET` is set. Before the Pass goes on sale: a restore onto a new account needs a reconcile by latest transaction id (report `docs/reports/app-build-2026-11/`).

v1.24.0

MinorNov 1, 2026

New

—Data API for the tower (`/api/data/v1`: claim, heartbeat, result, health). One bearer token, compared in constant time; off on alpha and without the token. The tower holds no database credential and no server key.
—Server-side guards per kind (`lib/data-api/accept-*.ts`): results, routes, discovery candidates and rendered pages are accepted only after the same checks the admin tools use. A refused payload goes to review and writes nothing.
—One claim path for every runner: the data API claims, extends, closes and fails tasks through `lib/data-queue` (claim, finish, backoff), the same code as the VPS batch. A claim hands the tower a token (`claimed_at`); a heartbeat or result with an older token gets 409, also after a takeover under the same runner name. The tower's `data_run` opens at the claim and closes with the batch's last result.
—A discovery date is kept only when the evidence names it (`quoteContainsDate`, as for the VPS kinds since 1.22.1); otherwise the candidate is filed without a date and says why.
—Tower data worker (`scripts/tower-data-worker/`, `deploy/tower/`): finds results lists, route files, new events and pages that need a browser, one request per host every 3 s, robots.txt honoured on every redirect hop. Install files only; not installed yet.

Fixed

—The admin results upload withholds minors and checks plausibility, and the admin route tools check the distance; both had written without the pipelines' guards. A forced route upload is logged as such.
—The admin route processor writes the track, climbs and route year in one transaction: either all stand or none does.

Security

—The tower cannot be led into its own network. Every fetch, redirect hop and robots.txt request is refused when the host is an IP address or resolves to a private, loopback, link-local, CGNAT, unique-local, multicast or reserved address, and checked again when the connection opens, so a name that changes its answer in between (DNS rebinding) is refused too. The browser runs behind a local proxy that checks every connection and connects to the address it checked; a rendered page counts for the host it ended on.
—Wiclax result capture is off on the tower until its browser runs behind the same guard proxy; as it stands a page it opens could reach the tower's network. The worker is installed only once the tower VM's egress filter blocks private ranges: three code holes of one class (redirects, DNS rebinding, a second browser) say the network has to hold the line, not one more patch.
—Response bodies are capped at 20 MB on the tower, request bodies at 20 MB on the API (413). Authorization and cookies are dropped on a redirect to another origin; API calls refuse redirects. The systemd unit runs with a private /tmp and a read-only system and home.

v1.23.0

MinorNov 1, 2026

New

—Push channel for the iPhone app, server side. `push_device` table (migration 0035), `POST/DELETE /api/v1/devices`, an APNs HTTP/2 client with token auth and a Live Activity sender (`lib/push/*`). The four registration triggers send push as a second channel next to email, deduped per channel in `notification_log` (`push:<trigger>`).
—Off in production until `APNS_KEY_ID`, `APNS_TEAM_ID`, `APNS_PRIVATE_KEY` and `IOS_BUNDLE_ID` are set; a hardening round (retry cap, no late pushes on first enable, token-move abuse, logs without tokens, atomic rate limit) lands before the key does. Report: `docs/reports/app-build-2026-11/push-server.md`.

v1.22.2

PatchNov 1, 2026

Fixed

—Every map shows a map again. CARTO has refused raster tiles without a key since 25 Sep 2026, so the race map, every race page route, the row mini maps and the share story drew "API KEY REQUIRED" tiles. All five now draw one self-hosted basemap: OpenStreetMap data in the Protomaps schema, a PMTiles file (z0–13) served from our own VPS under `painplan.cc/tiles/`. No account, no key, no per-request cost.

Changed

—`lib/map/basemap.ts` is the one tile config: URL, zoom range, dark flavour and the OpenStreetMap credit the ODbL requires. `components/maps/basemap-layer.tsx` draws it in Leaflet, `components/maps/static-basemap.tsx` as a canvas for the share image, which now waits for the map before export.
—Maps show their attribution (they had hidden it); the share story prints "© OpenStreetMap contributors".
—Hosting, monthly update and the way back: `docs/reports/map-tiles-2026-11/README.md`.

v1.22.1

PatchNov 1, 2026

Fixed

—The first queue run wrote ten wrong dates, all reverted within the hour. A date without a source was "withdrawn" to whatever the page showed, also a future one: a ski-touring page (Supergiro Dolomiti → 22 Jan), another event of the series (BWR California → Querétaro's 22 Nov), a festival's first day (Shades of Speed, three routes → Fri 23 Jul), a side event (Säntis Classic). A withdrawal now goes only to an edition that already took place and that the organiser's sentence names; any other reading goes to review.
—Nine "confirmations" carried no date in their quote (Haute Route "is back in 2027", Leadville's lottery window): the page was recorded as the date's source. Confirming now needs the date in the quote; the nine were reverted to projections. A review's one-click proposal needs the same.
—Each revert is in `race_change_log` with a `data:revert:lead` note.
—A sourced upcoming date the organiser still shows is a recheck, not a review: the annual-cadence check measured it against itself ("0 days after") and sent 18 events to review.

v1.22.0

MinorNov 1, 2026

New

—One queue for race-data work (`data_task`, `data_run`, migration 0031; `lib/data-queue/*`). A scheduler sets a due date per event and field (entry windows daily around an opening, unsourced dates now, passed races 14 → 30 → 60 → 90 days), the sidecar `data-worker-loop.mjs` claims with a lease every 15 minutes, failures back off by HTTP status and go to review after four tries.
—Entry windows (`monitoring.registration`): pre-ballot, ballot, bundle, general, waitlist, each date stored only with the organiser's sentence that contains it. `registration_opens`/`closes` are derived from them, so the page and the mails keep working.
—Link check (plain HTTP, weekly; two dead readings go to review) and the race-desk eval as a weekly job (`lib/eval/*`, same counts as the Python runner).
—`/admin/data`: health per job, queue depth, overdue tasks and the review list with accept, reject and recheck.

Changed

—Large sweep of 1 Nov: organiser-sourced future dates 22 → 140, past-dated rows 109 → 89, stored entry windows 0 → 29, future openings 1 → 12; 250 change-log rows, each with its quote. Nove Colli opens 5 Dec, Fred Whitton has its pre-ballot, ballot and close, Tuscany Trail its three openings.
—The freshness sidecar is retired from the container start; `/api/cron/race-freshness` stays callable and runs the same code.

Fixed

—The freshness worker checked 42 of 147 events in a month: past-dated events were always eligible and sorted first, so the same twelve came back every six hours (1,944 checks, 4 rolls). Due dates now decide.
—Every deploy since 10:43 UTC on 1 Nov failed: concept code under `docs/` was typechecked with the app and imported an absolute path. `docs/` and `drafts/` are out of the typecheck.
—A waitlist reads as sold out on the race page instead of showing no state.
—An entry check never replaces a future opening with a past one, and writes nothing when the race moved to another edition while the page was read.
—A runner whose lease was taken over can no longer finish the task: a takeover always gets a later claim token, even in the same millisecond.

v1.21.0

MinorSep 20, 2026

New

—ENDU results adapter rewritten around the site's live API (`groups?slug` → editions → `results/events/{id}/settings` → paginated `results`). Verified by reproducing an existing import exactly: Nove Colli LUNGO 2024, 1,885 finishers.
—Wiclax adapter (`lib/results/providers/wiclax.ts`) and `scripts/results-capture.ts`, which opens a page in a browser and saves the payload it fetches — the only way past Wiclax's bot check and ENDU's runtime loading.
—Fixed-width listing reader (`lib/results/providers/text-table.ts`, `scripts/results-from-text.ts`, `scripts/results-text-sweep.ts`) for PDFs and Datasport's classic pages.
—`ascentFromPoints` — ascent measured on a full-resolution track rather than on the stored profile.

Changed

—Mont Ventoux 2026 imported: 523 + 1,158 + 2,444 finishers.
—The race page shows the organiser's climbing figure; the elevation profile now drives shape, bands and climbs only.
—The freshness worker sweeps weekly through the three months before a race (was fortnightly beyond 30 days).
—Eval: `route_gpx_url` compares by host and event (lead decision 12). 86.9% → 90.5%, wrong 12 → 7.

Fixed

—Ascent from the stored 150-point profile runs 20–48% under the real figure — Das Monument 1,628 m against 2,475 at full resolution. It had rejected three of the organiser's own GPX files.
—A `.clax` file's `<E h=…>` is a start time of day, not a finish time. Read as a result, a 2,466-rider field "finishes" between 07h33 and 07h57. Results live in `<R t=…>` and must be joined on bib.
—An e-bike field shares its course name ("Granfondo ELEC") and was being counted as finishers.
—Datasport writes H:MM.SS,t — "5:25.59,2" parsed as 5.4 minutes instead of 326.
—An edition whose entry has not opened can no longer be recorded closed or sold out. Ötztaler was live showing "closed" for a 2027 race 344 days out.
—Four route conflicts resolved and two candidate tracks rejected as the wrong route; the review queue is empty.

v1.20.0

MinorSep 20, 2026

New

—Results pipeline (`lib/results/`): provider adapters (RaceResult, ENDU, Sportmaniacs, ACN), category normalisation, aggregate statistics, a transactional writer, and a `race_results_source` registry recording where each edition's finisher list lives. One importer replaces five per-event scrapers.
—`/admin/results` — the harvest as it stands, with the reason on every failure. The admin dashboard now links `/admin/freshness`, `/admin/results`, `/admin/routes` and `/admin/ingest`, which were reachable only by URL.
—Route harvest (`scripts/route-harvest.ts`) — walks a race's own site for a GPX, Ride with GPS, Komoot or Strava route; `lib/routes/dem.ts` fills elevation for a route line without it from SRTM 30 m.
—Course analysis (`lib/routes/analysis.ts`) and `CourseDemands` on the race page — gradient bands, ranked climbs, course shape, measured ascent.
—Season-planning data (`lib/planning/demand.ts`) — demand score, recovery days, season-shape issues, travel distance.
—Migrations 0029 (results pipeline) and 0030 (planning fields).

Changed

—`estimateRaceTime` integrates a race's real elevation profile where one exists and reports which model it used.
—Test runner is `tsx --test`, so tests can import the codebase's extensionless modules. 64 → 124 tests.

Fixed

—Minors excluded from finisher results (`docs/legal/results-data-model.md` §1a): 220 rows in probable-minor categories withheld across 4 editions, archived rather than deleted, and filtered in every public read including the claim search.
—A signed gap column read as a finish time — made a 6:48 rider the 61-minute winner of a 214 km race.
—A disqualified rider imported as a race winner — a DSQ marker sits beside a real time, and a positional read never saw it.
—A list that parses but belongs to another contest — rejected by a speed plausibility guard (106, 750 and 5,280 km/h all reached production-bound code).
—An edition year assumed rather than sourced — Leadville Trail 100 was imported as 2026 and has been withdrawn (1,483 entries); the year must now come from the provider's own event name.
—A valley approach merged with the pass above it — a climb now ends on a sustained flat as well as on a descent.

v1.19.0

MinorSep 19, 2026

New

—A date without a source is a projection, and is now treated as one. 26 published events carried a future date with no organiser URL behind it — someone had added a year to last year's date. Each was checked against the organiser: 11 confirmed (source recorded), 4 corrected (the organiser states another day — Taiwan KOM was out by six days, Big Sugar by six, both L'Étapes by one), 8 withdrawn to the last edition that can be evidenced and shown as awaiting, 3 flagged where the page could not be read at all. Rhön Radmarathon, the example in the brief, held 2027-05-15 while its organiser still showed May 2026.
—The worker now does this itself. It claims a future-dated race whose `monitoring.dateSource` is empty as its own priority tier — behind wrong dates, ahead of merely-due ones, so an unverified claim cannot starve behind the backlog. The organiser confirms it → the source is recorded; states an older edition → the projection is withdrawn and the row shows "date not out yet"; unreadable → flagged, never guessed. Rolling a race forward now records its source too, so the check does not repeat.

Changed

—A stage race is one row carrying the whole week (total distance, total elevation), with the stages listed in `highlights` rather than split into separate race rows. Giro delle Dolomiti 400 km → 540 km / 14,000 m across five stages; RiderMan's elevation 6,000 → 2,985 m across three; Engadin Radmarathon already fitted and gained the same stage list. The golden set was adjusted to match, with the reason recorded on each entry. Accuracy 86.7% → 88.1%.

v1.18.0

MinorSep 19, 2026

New

—A race awaiting its next date says so. 79 published rows held the date of an edition that had already run, because their organiser has published nothing for 2027. To a rider planning a season that reads as a real date in the past. Those races now show "2027 · date not out yet · usually June" on the race page, the year with the usual month in the explorer's date block, and they sort with the other undated events instead of down among the past ones; the region hubs move them out of last year's month into a trailing section. The stored date stays as the anchor the usual month is read from, and the freshness worker clears the flag the moment it rolls a race forward (`lib/races/awaiting-edition.ts`, 8 unit tests).
—An unannounced edition also has no registration state to show — every stored value describes the edition that ran, so "closed", "open" and last year's opening date are all suppressed in favour of "See website for dates".

Fixed

—Three more festival day-per-route errors, all pre-dating the sweep: Granfondo Colnago 2027-04-09 → 11 Apr ("Granfondo/Mediofondo Domenica 11 aprile"), Top Dolomites 2027-06-04 → 6 Jun (the 4 Jun entry is the Brenta Bike Experience), UNBOUND Gravel 2027-06-03 → 5 Jun (window 3–6 Jun, race day the 5th; our four variants are all Saturday distances). Black Forest ULTRA's four marathon rows set to Sunday 25 July 2027 and kept flagged — the organiser has not published a 2027 day schedule.
—35 high-confidence fields corrected against the independent auditor's golden set: 9 registration states, 2 opening dates, 18 distances the organiser no longer runs. Two variants the organiser has dropped are archived rather than deleted; ten medium-confidence findings went to the review list instead of being written blind. Catalogue accuracy against the set 62.2% → 86.7%.
—Gran Fondo Istanbul and Monaco di Baviera Classic archived (reversible, nothing deleted) — both organiser sites are gone. The two Portuguese races now point at their own event pages instead of the organiser's event list, which was answering with a neighbouring race.

Changed

—8 of the 14 discovery events re-added with verified data (Alpenbrevet, Säntis Classic, Engadin Radmarathon, Kitzbüheler Radmarathon, BGY Airport Granfondo, Allgäu Radmarathon, La Fausto Coppi, Race Across Austria — 22 rows). Distances and elevation come from each organiser's own route page, pain levels calibrated against comparable races already in the catalogue. The other six did not reach a complete verified data set and stay out.

v1.17.1

PatchSep 19, 2026

Fixed

—Festival dates are no longer stamped onto every distance. An independent audit of the 39 rolled rows found 32 correct and 6 wrong, all one failure: where a weekend festival gives each route its own day, the sweep wrote the *first day of the window* on every variant. Colnago GF Mont Ventoux's three cyclosport routes were dated as the gravel Saturday (now Sunday 6 Jun 2027); Shades of Speed's Wendelstein and Gravel 90 ride the Saturday (now 24 Jul) and Das Monument the Sunday (now 25 Jul), not the Friday the festival opens. Corrected in production against the organiser pages, with change-log rows; a one-day route inside a festival no longer carries the festival's `date_end`.
—The worker now refuses this roll rather than guessing it. The scrape classifies an event as `single_day`, `stage_race` or `festival_multi_route` and, for a festival, captures which route rides which day. A festival goes to the review queue with the day list, because a distance variant cannot be matched to an organiser's route name reliably. A stage race — which lists one entry per stage — still rolls to its window start and keeps its end date; verified live against Haute Route Alps, Mont Ventoux and Shades of Speed. An end date is now kept only for a stage race, never for a bare weekend window.
—Black Forest ULTRA Bike Marathon flagged (4 rows): it holds the Friday window start, but the organiser's own schedule puts the marathon on the Sunday and the Friday evening is the Bambini Trophy. The 2027 day schedule is not published, so the day is not guessed.
—Migration Gravel Race confirmed at 2027-06-15 — the audit could not verify it (JS shell); a rendered fetch returns "June 15 - 18 2027".

v1.17.0

MinorSep 19, 2026

New

—Race freshness worker — races no longer go stale silently. A sidecar loop (`scripts/freshness-worker-loop.mjs`, started from the Dockerfile CMD alongside the notification sidecar) POSTs `/api/cron/race-freshness` every 6 hours. Each run claims a small batch of events that are past their date or due for a re-check, asks the organiser's own site what the next edition is, and takes exactly one action per event: roll the whole distance-variant family forward, flag it for a human, or just reschedule the next look. Overlap-safe by construction — work is claimed in the same statement that selects it (`FOR UPDATE SKIP LOCKED`), so a manual run during a scheduled one cannot double-process. Disabled on alpha, which shares the production database.
—Four cross-checks before any date is written (`lib/freshness/verify.ts`, 43 unit tests on `node:test`). Organiser sites routinely leave last year's edition up, so a scraped date must survive all of: the page's own edition year matches the date's year; a named weekday matches the weekday the date really falls on; the gap to the previous edition sits in the 300–430 day annual window; and the evidence quote actually mentions the year. The cadence check is what catches a scrape that answered for a *different* race — the other event's date is internally consistent, so nothing else can see it.
—`/admin/freshness` — the review queue: what the worker refused to decide, with the evidence and a link to the organiser page, plus the last runs and whether the worker is running at all (`freshness_run` table, migration `0028`).

Changed

—Registration state is no longer trusted blindly. A "closed" reading for a race still months away is a stale page describing the edition that just ran; writing it would tell riders a race is shut before it has opened. Those readings are now discarded, and a page whose state is untrusted has its dates discarded too — one page, one verdict.
—On a roll-forward, a registration window that can only belong to the previous edition is cleared instead of carried over.

Data

—2026-09-19 freshness sweep applied to production: 23 events rolled forward (39 rows), 5 flagged for review, 51 bookkept. Past-dated published rows 123 → 84; 105 change-log rows written, 23 rider-visible. Eight of the 23 were hand-checked against the organiser page (Ötztaler, RiderMan, SBT GRVL, Swiss Epic, L'Etape Denmark, Leadville, two Shades of Speed variants).
—Registration sweep: 14 state changes across the upcoming races that were `unknown`/`none`.
—Registration window cleanup: 100 opening dates and 21 closing dates left over from editions that had already run were cleared, along with 12 impossible windows where the closing date preceded the opening date. 44 legitimate windows kept.

v1.17.1

PatchSep 19, 2026

Fixed

—Festival dates are no longer stamped onto every distance. An independent audit of the 39 rolled rows found 32 correct and 6 wrong, all one failure: where a weekend festival gives each route its own day, the sweep wrote the *first day of the window* on every variant. Colnago GF Mont Ventoux's three cyclosport routes were dated as the gravel Saturday (now Sunday 6 Jun 2027); Shades of Speed's Wendelstein and Gravel 90 ride the Saturday (now 24 Jul) and Das Monument the Sunday (now 25 Jul), not the Friday the festival opens. Corrected in production against the organiser pages, with change-log rows; a one-day route inside a festival no longer carries the festival's `date_end`.
—The worker now refuses this roll rather than guessing it. The scrape classifies an event as `single_day`, `stage_race` or `festival_multi_route` and, for a festival, captures which route rides which day. A festival goes to the review queue with the day list, because a distance variant cannot be matched to an organiser's route name reliably. A stage race — which lists one entry per stage — still rolls to its window start and keeps its end date; verified live against Haute Route Alps, Mont Ventoux and Shades of Speed. An end date is now kept only for a stage race, never for a bare weekend window.
—Black Forest ULTRA Bike Marathon flagged (4 rows): it holds the Friday window start, but the organiser's own schedule puts the marathon on the Sunday and the Friday evening is the Bambini Trophy. The 2027 day schedule is not published, so the day is not guessed.
—Migration Gravel Race confirmed at 2027-06-15 — the audit could not verify it (JS shell); a rendered fetch returns "June 15 - 18 2027".

v1.16.0

MinorJul 31, 2026

New

—Admin route worklist (`/admin/routes`) — the human last mile for elevation profiles: every published race that has a route *source* (GPX link, Strava/Komoot/RWGPS id, route page) but no real profile, listed with clickable source links. Download the file by hand where automation can't (login walls, JS download buttons), upload it per row — the upload runs through the exact same pipeline as the automated backfill (`lib/routes/track.ts`, now shared: parse → resample → distance guard → change-log entry), returns the parsed km for a sanity check, and a distance mismatch warns first with an explicit "Save anyway" override. Backfill script consolidated onto the shared lib.

v1.15.0

MinorJul 31, 2026

New

—Live registration states in the explore table. The scraped page state (`monitoring.registrationStatus` — a field the squad design documented but the UI never read) now drives the registration column and stats sheet: "Sold out", "Closed" and "Opens soon" from the organiser's actual page beat date arithmetic. Priority is honest about time: a future opening date wins over any stored negative state (states are snapshots of the old edition), and a live "open" state beats a stale past closing date. Squad vocabulary (`opens_later`) is normalised on read.
—Two Firecrawl sweeps (JS-rendered pages plain fetch couldn't read): 29 fresh registration states for upcoming races (1 sold out, 6 closed, 7 scheduled — Arlberg, Ötztaler, Istria300 among them) applied family-wide with per-row scrape timestamps, plus the Taiwan KOM registration window. A validated RWGPS search recovered 4 of 18 dead route sources (Amstel Lungo, Maratona/Sellaronda, Munich–Milan, Stoneman Miriquidi) — and the day-long source march (Komoot public API as a third backfill source, an organiser-website link crawl over 154 source-less races, a validated RWGPS search over the remainder, ~21 wrong tracks rejected by a new distance guard) ends at 130/274 races with real profiles (was 87 at dawn).

Changed

—Firecrawl ingest calls use `maxAge` caching (48 h) — repeat drops, prechecks and variant re-follows of the same URL stop paying for a fresh render.

v1.14.0

MinorJul 30, 2026

New

—The notification scheduler is a plain-Node sidecar in the app container — no n8n, no host crontab, nothing outside git. The Dockerfile starts `notify-worker-loop.mjs` next to the server: 30 lines of boring Node that POST the app's own cron endpoint 5 minutes after boot and every 6 hours, logging status + sent/error counts. (The idiomatic Next routes — `instrumentation.ts` register and a layout-render kick — verifiably never execute in the Next 16 standalone runtime; both attempts were removed rather than left as code that looks alive.) Alpha never runs it (no `CRON_SECRET` there → loop exits); overlapping runs, including manual endpoint POSTs, are safe via the claim-then-send dedupe.

Data

—Registration-window harvest applied: 7 new closing dates (Bodensee ×3, Stelvio Santini ×3, Swiss Epic — all high-confidence, weekday-verified) plus 3 corrections (Stelvio placeholder opens → documented 2026-06-16, TORTOUR ×4 placeholders cleared, Colnago stale opens → 2026-08-27), each with a race_change_log entry. Harvest insight: only 24 of 135 reachable organiser pages publish an explicit registration window — the structural next step is watching the register-button state flip during ingest re-checks, not more date scraping.

v1.13.1

PatchJul 30, 2026

Fixed

—A stale `registration_closes` from last year's edition no longer masks a future opening date — a future `registration_opens` wins, so next-season races show "Opens {date}" (and the notify promise) instead of a false "Closed". Found live on the Amstel family (closes 2025, opens 2026, race 2027).

v1.13.0

MinorJul 30, 2026

Fixed

—The registration-notification pipeline actually fires now. A two-model audit (Claude agent + Codex, independently) found the whole chain inert: triggers read audience and dates from two tables nothing ever writes (`race_notification`, `race_registration`), so planning a race never subscribed anyone and the cron always found zero races. Rewritten: the pain list (`favorite_race`) is the audience, dates come from the race table itself, and a previously unreachable "registration is open" trigger now runs. Dedupe is claim-then-send with a unique index (migration `0027`), keyed per event family so variants don't double-mail and next year's edition isn't suppressed by last year's log row. Emails lose the emoji subjects, gain a dry spec line, and every primary CTA is the organiser's `registration_url` (race page as fallback). The cron endpoint now refuses to run when `CRON_SECRET` is unset instead of failing open.
—Design-sweep fixes (from codifying the system to v0.2): the List⇄Map pill no longer hides under the bottom nav on notched iPhones (safe-area + nav-aware offset); the mobile sort control is a cycling button — the native select was being forced to 16px by the iOS zoom guard, which is why "Sort DATE" still rendered huge on phones; a legacy sparkline rule was dimming the new profile chart's fill to ~1%; facet chips and the sheet close button meet the 44px touch minimum; the table header's sort marker is desktop-only (sort state lives once per breakpoint).

New

—"We'll email you" surface in the expand: races with a future opening date show, under the CTAs, "On your plan — we'll email you when registration opens." (planned) or "Get notified when registration opens." (not yet planned).
—Design system v0.2 — nine explore-sprint patterns codified in `docs/planning/design-system-feldbuch-v0.1.md` (facet chips, segmented control, spec-sheet rows, variant selector, sort placement, mobile row anatomy, honest-data rule, scroll-on-expand, floating pill), each with spec + research source.

Ops

—The notification cron has no production trigger yet — n8n workflow needed: POST https://painplan.cc/api/cron/notifications with Bearer CRON_SECRET, schedule 0 5,11,17,23 * * * (no retry-on-fail). First run should be manual with the response inspected.

v1.12.0

MinorJul 30, 2026

New

—Distance selector in the expanded row. Race families (60/100/160 km …) get tappable distance chips between the preview panel and the description — and the entire dossier follows the selection: the profile chart redraws with that variant's real GPX track, the map fetches that variant's route line, stats show that distance's climbing/pain/fee, and both CTAs (Race page →, + Add to plan) target the selected variant. Tabs stay honest per variant — a distance without real GPX data simply has no profile tab and falls back to the map.

v1.11.3

PatchJul 30, 2026

Changed

—The profile tab reads like a proper elevation chart now: the highest and lowest point are drawn and labelled, with one or two nicely rounded reference lines in between (dynamic — as many as the range supports), and total climbing/descent computed from the actual track sits underneath (↑ 1,890 m · ↓ 1,850 m). Dedicated Feldbuch chart component; the shared sparkline is untouched.
—Distance lists drop the repeated unit — "60 / 100 / 125 / 150 / 240 km" instead of five "km"s, in the expand line and the stats sheet.

v1.11.2

PatchJul 30, 2026

Changed

—Stats read as a spec sheet on phones — label left, value right, hairline per row (the Polestar specifications pattern); desktop keeps the two-column grid.
—Expanding a row parks it under the toolbar. On expand the row scrolls to sit right below the sticky search/filter bar (`scroll-margin-top` + `scrollIntoView`, honours `prefers-reduced-motion`), so the dossier gets the screen instead of whatever happened to be above it.

v1.11.1

PatchJul 30, 2026

Changed

—The expand's preview switcher is a real segmented control (the F1-app pattern, via Mobbin): full-width equal segments, 44 px tall, active segment filled lime — instead of three tiny text labels nobody could hit with a thumb.
—Cleaner mobile rows: the date now leads the row flush left and the ＋/× disclosure sits on the right edge (the iOS list convention — Polestar/Qantas/Peerspace all do this); the pain score column is desktop-only, giving the race name the space back.

Fixed

—"Sort DATE" rendered in system-default size — native `<select>` elements don't inherit font size; it now matches the crumb line's mono 10.5 px.

v1.11.0

MinorJul 30, 2026

New

—Real elevation profiles for 87 races (was 21). A new backfill pipeline (`scripts/backfill-elevation-profiles.ts`) pulls actual GPX tracks from RideWithGPS route IDs and organiser GPX URLs, resamples them to 150 distance-anchored points plus a 250-point route line, and writes them to the database with a `race_change_log` audit entry per race — idempotent, never touching curated fields like distance or total climb. 65 races gained real profiles in the first run; the 18 remaining failures have dead source links and are queued for enrichment.
—The expanded row is now a small dossier. Three preview tabs — Profile (the real GPX curve with its max altitude; this tab simply doesn't exist for races without real data — the synthetic sine-wave sparkline is gone from the table), Map (a mini dark map that draws the actual route line on demand, or a pain-colored location marker as fallback), and Stats (distances, climbing + m/km, pain with label, registration with fee).
—`/api/races/[slug]/route-line` — serves the route polyline on demand so the list payload stays light: list props ship a 48-point profile and no coordinates (full data would have added >1 MB of SSR JSON after the backfill).

Changed

—The primary action in an expanded row is now "Race page →" — a full lime bar (it was a barely-visible underlined link on phones); "+ Add to plan" moves to a quiet outlined secondary. Clearer words than "pain list" for first-time visitors, same mechanism underneath.
—One row open at a time — expanding a race collapses the previous one, and the floating List⇄Map pill hides while a row is open so it never covers the row's actions.

v1.10.0

MinorJul 30, 2026

Changed

—The explore controls now explain themselves. The generic Filter button and the ambiguous sort dropdown are gone from the toolbar. In their place (phones): a horizontally scrollable facet chip row — Discipline, Region, Distance, Profile, Season, Pain, Results — where an untouched chip shows its name and an active chip turns lime and shows its value ("Road", "Germany +1", "≤3"). Tapping a chip opens the filter sheet scrolled straight to that section; the sliders icon opens the full sheet. (The Strava segment-explorer pattern, via Mobbin.) Active filters live in one place per breakpoint: the chip row on phones, the crumb chips on desktop.
—Sort sits on the list it orders. "Sort DATE" is part of the crumb line directly above the table on phones (native select under the hood); desktop keeps the clickable column headers. Nothing about sorting lives next to filtering anymore.
—Two views instead of four. Grid and calendar are gone from the explore UI (their `view=` URLs still render for old links). What remains is List ⇄ Map — a floating pill at the bottom of the screen switches between them, and the map is now a first-class Feldbuch view: same toolbar, same facet chips, same crumb, same client-side filter engine, with one pain-colored marker per event family. The desktop toggle reads Table | Map next to the search field; the filter rail drives the map exactly like the table.

Fixed

—`view=map` used to fall through to the legacy grid world with its own filter UI; it is now rendered by the Feldbuch explorer, so switching views never changes how filtering works.

v1.9.0

MinorJul 30, 2026

Changed

—The explore page finally works one-handed. The mobile toolbar is a single sticky row under the search field: a Filter button with a live active-count badge, a compact sort select (Date / Km / Hm / Pain), and an icon view switcher (table / grid / calendar) — all inside 375 px with zero horizontal overflow. The crumb line compacts on phones ("Plan 3" instead of "Filters: … Pain list"), and expanded rows drop the desktop indent: the elevation profile runs edge-to-edge and "+ Add to pain list" becomes a full-width lime bar.
—The filter bottom sheet now carries the full facet set — the desktop rail's Profile (flat / rolling / mountain, derived climb-per-km) and Data ("With finisher results") pivots join Discipline/Region/Distance/Season/Pain, and the live "Show N races" count respects both. Opening the sheet from the table no longer pushes a history entry, so closing it never reverts your filters.
—The mobile hero is one sentence again. The tagline shortens to "Every race worth doing — with real finisher times." on phones (the action lives in the CTA right below it — no duplicated "See where you'd place"), and the three-beat "how it works" strip is desktop-only. Kicker → wordmark → lime band → sentence → two CTAs; nothing else.

Fixed

—Unknown `discipline` URL values (typos, stale links) are dropped at parse time instead of producing a blank filter chip and a silently wrong result count; crumb chips use stable category-prefixed keys.
—The hero tagline's color class was one of the dead Tailwind-v4 JS-config utilities (`text-foreground-secondary`) — it now uses the token var explicitly.

v1.8.0

MinorJul 30, 2026

New

—German region hub pages (`/kalender` + `/kalender/{region}`) — the season-planning money queries ("Radmarathon Kalender Österreich 2027") finally have a home: month-sectioned upcoming race listings (one row per event family) for Deutschland, Österreich, Schweiz, Italien, Benelux and Frankreich, with German titles/descriptions, `ItemList` JSON-LD, cross-region links, a marker-count intro line and a hand-off into the Race Finder pre-filtered by country. Linked from the footer ("Rennkalender (DE)") and the sitemap (priority 0.8). Copy in du-form, dry: "Du planst deine Saison, wir liefern die Daten. Der Rest ist dein Problem."

Fixed

—Tailwind v4 scans Markdown files for class candidates — a documentation line containing a wildcard arbitrary-value class corrupted the generated CSS in dev. The line is defused and the trap documented.

v1.7.0

MinorJul 30, 2026

Changed

—The landing hero now passes the five-second test. A plain-language kicker ("Where amateur bike racing lives") sits above the wordmark, the tagline leads with substance ("Every road, gravel and MTB race worth doing — with real finisher times…"), and a three-beat "how it works" strip (Find your race · See the field · Plan the season) lands right under the CTAs. The marquee loop is retired — the iconic lime band stays, static (motion answers actions, it doesn't loop).
—Sitemap sends honest crawl signals — race URLs now carry their real `updated_at` as `lastModified` instead of "now" on every request.

New

—Umami event taxonomy for the core loop — explorer filters/sort/search (debounced, counts only — no query text), row expands, view switches, pain-list adds/removes (central, in the favorites hook), placement-calculator pace commits, "use estimate", and FTP saves. The relaunch funnel (visit → filter → expand → track) is now measurable; no PII in any payload.

Ops

—`FIRECRAWL_API_KEY` set on the production app via the Dokploy API (+ redeploy) — `/admin/ingest` is live.

v1.6.0

MinorJul 30, 2026

New

—Feldbuch table view — the new `/races` default. The discover page leads with a dense, calm table (the "field book" from design-system v0.1): date block, race + one-line meta, course, registration status, pain score. Rows open in place (＋→× affordance, whole row clickable) into an elevation profile, description note, distance variants, and a labelled next step ("+ Add to pain list" / "Race page →"); siblings dim while a row is open; races on the pain list carry a persistent lime marker edge. Desktop gets a typography-only filter rail (discipline, derived climb-per-km profile facet, top countries with counts, distance, season, pain cap, data toggles) plus a comfort/compact density switch; mobile gets two-line rows and the existing filter bottom sheet. Grid/calendar remain one click away (`view=grid|calendar`).
—Client-side filter engine (`lib/races/client-filter.ts`) — the full grouped list ships once; every search/filter/sort answers instantly in memory while the URL stays the shareable state (replaceState + external-store sync; back/forward and race-page returns keep filters truthful; non-owned params like `utm_*` survive). The crumb line above the table answers every action: removable filter chips, a live result counter, "Clear all", the pain-list count, and a progressively disclosed "View season →".
—Search that finds Ötztaler when you type "otztaler" — diacritic-folded matching across name, city, country code *and* country name ("germany" works), applied to both the new table and the legacy server filter.
—Empty state with effective rescues — zero results names the culprit and offers only one-click fixes that actually rescue ("Drop 'MTB' → 4 races"), never dead-end suggestions.
—Honest Est. Time on race pages — the flat 25 km/h guess is gone. With FTP + weight on your profile (new fields, migration `0026`, Strava-independent inline editor right in the card) you get an FTP-anchored *range* (`7:05 ±45m`); without, an em dash and "Add your FTP →". The placement calculator shows a "Your estimate" marker with a one-tap "Set slider to estimate", and its result block now ends in "+ Add to pain list" instead of a dead end.
—Feldbuch design tokens + type trio — Papier/Graphit token layer (`--fb-*`, light-mode-ready via `data-theme`), Archivo / IBM Plex Mono / Newsreader self-hosted via `next/font`.

Changed

—Race-page stat grid cut to the four decision stats (Distance / Elevation / Est. Time / Terrain) — Weather, Avg Grade, Intensity and the Participants card are gone per the product review; weather returns later inside pre-race reminders where a forecast is honest.
—Reviews render before the review form on race pages.
—`/races` fetches the catalogue once (legacy server-filtered props are only computed for legacy views), season presets cover the 2026 *and* 2027 planning horizon in both filter engines.

Removed

—The green cursor circle. Lime is a signal, not ambience (design-system law #2). The cursor context stays for consumers; the system cursor is back.

v1.5.6

PatchJul 16, 2026

New

—`/admin/ingest` — URL-drop race ingestion. Paste an organiser URL: it's checked against the catalogue (locale-insensitive URL matching), verified as a cycling event, scraped and structured via Firecrawl JSON extraction, and landed through the ingest engine — existing races get a protected enrichment update (with per-field diffs in the result card), new events get created per distance variant, non-race pages get an honest rejection with a reason. `ingest_job` queue table (`drizzle/0025_ingest_job.sql`), `after()`-driven worker with a self-healing re-kick and a `CRON_SECRET` backstop route (`/api/cron/ingest-worker`). Requires `FIRECRAWL_API_KEY` in the app environment.
—Ingest engine hardening — enrichment updates now write `race_change_log` rows for every rider-relevant field change (date, registration/website URL, distance, elevation, GPX) and report completeness of the *merged* row instead of the sparse scrape input; `IngestResult.changedFields` exposes the diff.
—Data: 3RIDES 2025 finisher results — 743 finishers of the UCI 3RIDES Gravel Race 122km (Aachen 2025) imported as the 2025 edition of the Winterberg UCI Gravel Race; placement calculator live, venue provenance noted in the race changelog.

v1.5.5

PatchJul 16, 2026

Fixed

—Race explorer now leads with upcoming races — listing order across `/races` (grid + calendar), featured, and related races is now *upcoming (soonest first) → date-TBD → past (most recent first)* with a name tie-break, instead of raw date-ascending that buried every plannable race under finished ones. Calendar view stays strictly chronological (it re-sorts its month buckets); the Instagram calendar story sorts its 1–5 list chronologically; featured skips date-TBD races so the homepage never leads with a dateless card.
—Register redirect fallback no longer leaks the container origin — races without a registration/website URL redirected registrants to `https://0.0.0.0:3000/...` behind Traefik/Varnish (`req.url` carries the bind address). The fallback now builds on `APP_URL`.
—`computeEventKey` understands Italian distance variants — `gran/medio/lungo/corto` name suffixes are now stripped (end-anchored, so "– Gran Fondo X" / "(Gran Canaria)" stay intact), preventing future ingests from splitting one event into per-variant lineages.

Changed

—Data: freshness sweep applied to production — all 113 past-date events audited via Firecrawl: 65 rolled to confirmed 2026/27 dates, 46 re-check-scheduled, Crusher in the Tushar marked cancelled (wildfire), Gran Fondo Istanbul + GFNY Toscana-Pistoia flagged as likely defunct, Saimaa flagged for 2027 distance remap. 44 per-variant `event_key`s normalized to family keys; 18 organiser-confirmed dates cleared of `date_tbd`. Full trail: `docs/planning/handoff-2026-07-16/`.

v1.5.4

PatchJun 20, 2026

New

—Cancelled-race state — a race whose edition is called off now stays listed with a clear CANCELLED treatment instead of being hidden, so riders who look it up learn it's off. New `cancelled` / `cancelled_reason` / `cancelled_at` columns (`drizzle/0024_race_cancelled.sql`); CANCELLED badge + dimmed card + struck-through date in the grid; a cancellation banner on the race page; the commit bar shows "Race cancelled" (no register/track CTAs). The PainPlan squad can set it via the MCP after a verified cancellation is approved. First live example: Styrkeprøven 2026 (Trondheim–Oslo 540 km — permit rejected), which the squad detected autonomously.

Changed

—Catalogue cleanup (data) — deduped the catalogue (archived 7 stale duplicate rows from a Dec-2025 import batch), backfilled `edition_year` on 286 races (was NULL, broke dedup + lineage), corrected 3 verified data errors (Mondsee/Supergiro dates, Alb Extrem distance), and published 12 complete, real races that were stuck hidden (Salzkammergut Trophy, Stoneman ×2, Munich-Milan Gravel, Cowlands, Monaco di Baviera Classic, Gran Fondo Schleck/Vogesen, …). Visible races 262 → 274, 0 duplicates.
—Scraping knowledge base — documented Wiclax + EvoData providers and the WAF/browser-only rule (`docs/scraping/README.md`).

v1.5.3

PatchJun 19, 2026

New

—`race.monitoring` jsonb column (`drizzle/0023_race_monitoring.sql`) — bookkeeping the PainPlan maintenance squad owns to schedule pragmatically instead of blind-polling: `awaitingNextEdition` + `nextEditionCheckDate` (a passed race stays visible and is not degraded until the organiser actually posts the new edition), `registrationCaptured` / `registrationStatus` (capture the registration window once, then stop watching), `firecrawlMonitorId` (retire the watch once captured), `lastChangeHash` (skip unchanged pages via change-tracking), `checkBackoffDays` (adaptive cadence), `resultsAttempts` (settle finisher harvest). Partial index on `awaitingNextEdition`. No UI/behaviour change — infra for the squad's cron jobs, which report into the existing Crew channel + a Discord admin channel. Squad role + cron catalog live in `pocket-claude/roles/painplan/`.

v1.5.2

PatchJun 19, 2026

Fixed

—Lists and tracked races now persist to the database — previously only favorites synced server-side; custom lists and race-status (interested / planning / committed / completed) lived only in `localStorage`, so they never followed a rider across devices and were lost on cache-clear. Logged-in mutations now sync in the background and merge on login, mirroring the proven favorites pattern (optimistic local update + fire-and-forget server write).

v1.5.1

PatchJun 18, 2026

Changed

—Design-system rollout across the rest of the app — the secondary and account pages now match the new homepage look (single lime accent, sharp corners, mono labels, hairline lattice):

v1.5.0

MinorJun 18, 2026

New

—Crew channel (admin) — an in-app squad cockpit that opens like the notifications channel: a right-side slide-in panel with one unified timeline mixing the squad's reports, the chat, and inline approve/reject items, plus a composer to send tasks to the squad. Admin-only, reachable from a header "Crew" trigger (desktop) and a bottom-nav "Crew" tab (mobile). Polls every ~4s. Lets the crew be run from the PWA instead of Telegram.

v1.4.3

PatchJun 18, 2026

New

—Sign in with Google — one-tap signup/sign-in alongside email.
—Richer homepage bento — the cells are now live: drag the speed slider to see where you'd place, a real finishing-time histogram with All/Men/Women, an animated pain meter, a season month-strip, an editions timeline, and a race-pin map — in a Stripe-style layout. The crafted glitch PAINPLAN hero is back, carrying the new "plan your season / where you'd place" message.

Fixed

—Filtering is reliable again — applying filters from the bottom-sheet no longer occasionally showed a blank grid (a cache layer was serving stale navigation data).
—"Embrace the Pain" now opens signup correctly (was hitting a dead page).
—Faster first paint — removed a loading-splash edge case that could hang for several seconds.
—Accessibility + polish: full keyboard control on the placement slider, the field-data summary now tracks the gender toggle, the desktop placement cell renders fully, and assorted layout/contrast refinements.

v1.4.2

PatchJun 17, 2026

New

—Mobile filter sheet — the race filter is now a draggable bottom-sheet with five accordion sections (Discipline / Region / Distance / Pain / Season), sharp lime chips, a live "Show N Races" count that updates as you toggle, and Back-gesture/Escape to dismiss.
—New homepage — rebuilt as a "bento" landing that actually shows what PAINPLAN does: a placement-calculator teaser, real field-data, the pain scale, season planning, editions/history and claim-your-result — plus a live stats band and curated discovery shortcuts (Gravel marathons, High-altitude sufferfests, Road monuments…). New line: "Every race. Rated by pain."
—Field Data badge — races with real finisher results now carry a lime "Field Data" badge in the grid, so the placement calculator + finisher histogram stop being a hidden feature.
—Motion foundation — appear-on-scroll reveals, animated count-up numerals, and a proper button loading state, all respecting your "reduce motion" setting.
—Sitemap + robots — the site is now properly crawlable (every race has a URL in the sitemap).

Changed

—One status vocabulary everywhere — Interested → Planning → Committed → Pain conquered, in a single lime accent (no more mixed blue/yellow/green or "Registered" vs "Committed" on the same card).
—Tracking a race from the commit bar now also adds it to your saved list — your pain list and favorites are finally the same thing.

Fixed

—Distance variants no longer show up as "past editions" — a race's other distances were being listed as prior-year editions; history now shows one real edition per year.
—Install prompt no longer covers the action bar on race pages (it was untappable on iPhone), and waits until you've looked around.
—Status picker is now a proper sheet — closes with the Back gesture or Escape, traps focus, locks scroll.

v1.4.1

PatchJun 17, 2026

New

—Race commit bar — a persistent action bar on every race page (mobile) whose primary button moves with you through the lifecycle: Add to pain list → Interested → Planning → Committed → Pain conquered. Once you're tracking a race, Register becomes the prominent call to action. Pick your status from a quick sheet; remove anytime.
—Install prompt — a tasteful "Install the app" affordance (one-tap on Android, guided Add-to-Home-Screen on iPhone) answering the most-asked question: yes, you can keep PAINPLAN on your home screen.

Changed

—The public changelog is now driven straight from this file — every shipped change shows up, nothing to maintain twice.

Fixed

—Accessibility — text contrast now meets WCAG AA, and the whole app honours your "reduce motion" setting (no more decorative glitch/marquee/shimmer if you've asked the OS to calm things down).
—Defined the brand accent and surface design tokens that several newer panels referenced but that were silently falling back — colours now render as intended.
—App-shell polish: dark status bar when installed, no rubber-band overscroll, no accidental text-selection on navigation chrome.

v1.4.0

MinorJun 17, 2026

New

—Editions & History — race pages now show past editions (with finisher counts, median time and DNF rate) and a rider-facing "What's changed" changelog (route, date, distance, registration changes) across an event's editions
—Claim your result — find your name in a race's finishers and claim it; consent-first, with an optional Strava activity link as soft proof
—Pain Resume — a shareable card of your claimed result (time, percentile, place, pain) with download/share, at `/r/[id]`
—Ratings & reviews — rate races on safety, route, organization, feed stops, value, scenery and vibe, with photos and a "Verified finisher" badge
—Registration referrals — the Register button now hands off to the organiser and tracks the referral (bot-filtered, GDPR-clean)
—Race ingestion engine — normalises, de-dupes and completeness-gates new races, auto-noting notable route changes between editions
—Season persona on the share card — your planned season earns an identity (The Climber, Gravel Grinder, …)

Changed

—Country names now show in full ("Germany", not "DE") across cards, calendars, share images and the season map
—Backfilled cross-year event lineage so 69 multi-edition events surface their history

Fixed

—Closed several country-code display leaks (race-briefing email, submission form)
—Guarded `getCountryFlag` against null input; hardened country-name resolution for ingestion

v1.3.5

PatchMar 13, 2026

New

—Gender filter tabs on finishing times histogram — switch between All, Men, Women distributions
—Category display normalization — `formatCategoryLabel()` maps raw provider codes (ENDU, RaceResult, Sportmaniacs, ACN-Timing) to human-readable labels across 80+ category codes
—Admin results tracking — "Results" column in All Races table shows edition count with finisher totals tooltip
—Shared `isWomenCategory()` helper — consolidated from duplicated local functions

Fixed

—Year-switching for distributions — gender distributions now fetched for ALL editions, not just latest year
—Custom placement slider — replaced native `<input type="range">` with pointer-based custom slider; fixes Tailwind `bg-lime` resolving to transparent inside framer-motion
—Removed bottom progress bar — was confusing and redundant with the percentile text

Data

—Published Gran Fondo Strade Bianche (long + short) — was stuck in `needs_enrichment`
—Fixed Strade Bianche date from 2027 → 2026
—Normalized Dreilandergiro categories (removed full contest name with km/hm)
—Cleaned 28 empty/malformed categories across 5 races (M-, M--, F--, F-)
—Fixed 1 misgendered entry (F-Snior-Mascul → M-Senior)
—Normalized all Sportmaniacs categories: Spanish truncated names → English (10k+ entries)
—Normalized Mallorca 312 GENERAL categories across 2024/2025

v1.3.4

PatchMar 12, 2026

New

—Speed slider — Hero slider mapped to the actual field range (P90 to winner speed), with field density zones and reference ticks (Slow 25%, Mid-field, Fast 25%, Winner) on the track
—Bidirectional sync — Slider and text input stay in sync; drag to explore, type for precision
—FTP teaser — Info note explaining power-based prediction is in development, with course profile integration
—Dual finisher tables — Women and Men side-by-side on desktop, stacked (women first) on mobile; guarantees equal visibility
—Reusable FinisherTable component — Extracted for split/category/PAINPLAN views

Changed

—Placement calculator completely redesigned with slider as hero element, prominent 2-column result layout (Top X% + estimated time)
—Finisher default view changed from single table to gender-split dual tables
—Mobile finisher layout shows Women table first, then Men (stacked)
—Category tabs now switch between split view and single-category view

v1.3.3

PatchMar 12, 2026

New

—Men / Women filter tabs — Gender-split tabs in finisher table; ensures top women always visible alongside men
—Prominent user marker on range bar — Callout box above bar showing estimated time and avg pace; marker color matches percentile (lime/coral)
—Enhanced calculator result — Large "Top X%" display with rank and estimated time

Changed

—Removed effort slider from placement calculator — pace-only mode for now; effort slider reserved for future FTP integration
—Finisher table limit raised from 10 to 20 (desktop) and 10 (mobile)
—Finisher fetch limit raised from 25 to 100 entries for better gender representation
—User marker on range bar now uses thicker 3px line instead of 2px, colored by percentile
—Calculator layout simplified to single-column flow: input → reference → result

v1.3.2

PatchMar 12, 2026

New

—Pace-based Placement Calculator — Replaced time input with avg pace (km/h); reference paces show winner, fast 25%, mid-field, slow 25% speeds
—Rich Stat Cards — 3-tier layout with icon+label, primary value (large mono), secondary hints (finish rate, avg speed, delta vs winner)
—Winner card — Name + winning time in lime + avg speed as hint
—Median card — Time + "+X:XX vs winner" + calculated avg speed from distance
—Edition label — "Edition" hint next to year PillToggle selector
—Category filter tabs — Dynamic tabs per category (M-Elite, M35, F, etc.) with entry counts
—PAINPLAN Users tab — Filter finisher table to community members only
—Strava activity links — Branded Strava icon per finisher row (when URL exists)
—PAINPLAN user badge — Lime dot indicator on linked entries
—"Claim your result" teaser — Future claim flow placeholder in finisher footer
—Source link in finisher section — "View all results on {source}" with ExternalLink icon

Changed

—Placement calculator input changed from hours:minutes to avg pace in km/h
—Effort slider now adjusts pace down instead of time up
—Calculator shows estimated finishing time in result output
—Finisher table source attribution moved from standalone footer into finisher section
—`distanceKm` now piped through component chain for pace-to-time conversion
—`getTopFinishers` now returns `stravaActivityUrl` and `linkedUserId` fields

Data

—Weather data populated for all races missing it (Nove Colli and others)
—`rank_overall` fixed to true global rank by finish time (was per-category)

v1.3.1

PatchMar 12, 2026

New

—Race Results Frontend — Full visualization suite for race edition statistics, renders automatically on race pages that have results data
—Percentile Range Bar — Field position visualization showing where riders cluster: winner, fast 25%, mid-field, slow 25% zones with animated user marker
—Placement Calculator — "Where would you place?" tool with hours/minutes input and effort slider (60-100%), shows estimated rank and percentile
—Time Distribution Chart — Histogram of finishing times in 30-min buckets with median marker and user bucket highlight
—Finisher Preview Table — Top 10 finishers with rank, name, time, speed, category; responsive (top 5 on mobile)
—Year Selector — PillToggle for switching between edition years when multiple exist
—Stat Grid — 4-stat summary: starters, finishers, winner time, median time
—Effort adjustment formula — `adjustedTime = baseTime / (effortPercent / 100)` for what-if scenarios

Fixed

—Percentile overflow capped at 99% (was showing "Top 131%" when adjusted time exceeded P90)
—Effort slider result text now updates immediately (removed AnimatePresence exit animation delay)

Technical

—Split `race-results-types.ts` from `race-results.ts` to avoid `pg` module in client components
—Server component (`RaceResultsSection`) fetches data, client component (`RaceResultsClient`) handles interactivity
—All visualizations use custom CSS/div-based rendering — no chart libraries
—Components: `race-results-section.tsx`, `race-results-client.tsx`, `percentile-range-bar.tsx`, `placement-calculator.tsx`, `time-distribution-chart.tsx`, `finisher-preview.tsx`

v1.3.0

MinorMar 11, 2026

New

—Admin "All Races" table — Full race management with sortable columns, search, pagination (50/page), and 4 quick filters (Missing GPX, Past Races, Needs Review, Needs Rollover)
—Race detail side panel — 420px fixed panel with Details, Comments, and History tabs; inline editing for key fields
—Race flagging system — Field-level jsonb flags with notes for enrichment agent awareness; flag/unflag from side panel or dedicated modal
—Race cloning — Clone race to new edition year; replaces year in slug, bumps date, copies route data, archives source race
—Change audit log — `race_change_log` table tracking all mutations with user, timestamp, old/new values
—GPX completeness scoring — 4-criteria scoring (route coordinates, elevation profile, climbs, route source ID) displayed as 0-100% in table
—Database schema for race results — `race_edition_results` (aggregate stats per edition) and `race_result_entry` (individual finisher records) tables created
—Race lifecycle columns — `edition_year`, `next_check_date`, `last_scraped_at`, review flag columns on race table
—6 new API routes — `/api/admin/races/all`, `/flag`, `/clone`, `/history`, `/comments`, enhanced `PATCH /[slug]`

Changed

—Admin dashboard now has "All Races" as first tab (before Issues, Suggestions, Routes, Needs Enrichment)
—Race PATCH endpoint now logs all field changes to audit log

Database Migration

—Migration `0015_talented_old_lace.sql` — 3 new tables, 8 new columns on race, 1 new column on race_result

v1.2.9

PatchJan 15, 2026

Changed

—PostgreSQL Migration — All race data now stored in PostgreSQL (263 races migrated from JSON catalog)
—Removed JSON-based race catalog in favor of single database source
—Updated `/add-race` skill to insert directly into database
—Races added via `/add-race` are immediately available (no deployment needed)

v1.2.8

PatchDec 20, 2025

Fixed

—Grid layout reset on filter change
—Restored icons in view toggle

New

—New server-ops skill
—Added stackedLabel/stackedMode to SegmentedControl

v1.2.7

PatchDec 15, 2025

New

—Real detection-based loading screen (`AppLoaderProvider`, `useReportReady`)
—Branded loading UI with progress bar

v1.2.6

PatchDec 10, 2025

New

—Self-hosted Umami analytics at `analytics.madisonhofer.cloud`
—GDPR-compliant tracking (runs under legitimate interest)

v1.2.5

PatchDec 5, 2025

New

—Beta feedback widget system
—Feedback API endpoint with Discord webhook

v1.2.4

PatchDec 1, 2025

New

—Accordion, Skeleton, Toast UI components
—Help page FAQ accordion

v1.2.0

MinorDec 1, 2025

New

—Group race sharing and commitment tracking
—Community hub (hidden)

v1.1.0

MinorNov 15, 2025

New

—Groups feature with invite codes
—Navigation updates

v1.0.0

MajorOct 1, 2025

New

—Initial launch
—Race discovery with filtering
—User accounts with Google OAuth
—Favorites system
—Race calendar
—Dashboard
—Pain level ratings