Updates

Changelog

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

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