EDITORIAL NOTE

Warhammer 40,000 11th edition launches Saturday 20 June 2026. The Archive is pausing weekly data ingestion (Performance pulls, ELO updates, Attention snapshots) through the transition and resuming with the first post-launch competitive weekend. Existing W23 data remains visible on every signal; the next data cycle lands the week of 3 July 2026, capturing tournaments held on 27–28 June — the first competitive weekend of 11th edition play. The Editor is using the gap for site refinements.

CHANGELOG

CHANGELOG

What changes on the Archive — and when.

The Archive logs everything it ships: features added, updates to published work, corrections to errors caught after the fact, and data refreshes that bring the dashboards forward. Corrections are flagged plainly — accountability is the price of trust, and an analysis site that quietly edits its own past is one that should not be trusted.

2026-06-08 UPDATE
2026-06-08 UPDATE
BCP scrape pipeline — operational tuning bundle (5 fixes). (1) Silent-skip warnings: every roster player whose list isn't fetched now surfaces a structured `list_fetch_skipped` warning (reason `no_list_id` or `fetch_failed`) in scraped.json + scraped-summary.md — the prior behavior silently dropped missing lists. (2) Subscription tier detection: rewritten to check for the `Active Plan` affordance first; falls through to a free-tier warning only if no Active Plan is present (the prior logic false-positived paid accounts as free). (3) Snapshot trim: projectToSnapshotShape now builds a minimal projection (provenance + meta + canonical games[]/events_summary[]) rather than deep-cloning the entire scraped object — the raw scraped arrays (roster, pairings, placings, lists) stay only in the gitignored audit file, dropping per-snapshot repo weight and making list_name absence structural rather than per-field. (4) Tuesday cadence: weekly routine docs rewrote FRIDAY MORNING → TUESDAY MORNING. Tuesday lands the prior weekend's data ~36-48 hours after events end, leaving 3-4 days for the audience to absorb before the next weekend's list-building. (5) `--include-overflow N` flag: extends the scrape's search end-date by N days beyond the ISO week's Sunday so Sun-into-Mon (and rare Thu-Mon) bleed events get picked up; recorded explicitly in the published snapshot's `meta.date_range_used`. Tuesday + `--include-overflow 2` is the recommended pairing. verify:digest grew 222 → 270 with new scenarios covering the trim, the silent-skip warning emission, the ISO-week date math, and the date_range_used provenance.
2026-06-08 FEATURE
2026-06-04 UPDATE
2026-06-04 FEATURE
2026-06-03 FEATURE
2026-06-03 UPDATE
2026-06-02 UPDATE
2026-06-02 UPDATE
2026-06-02 UPDATE
2026-06-02 UPDATE
2026-06-02 FEATURE
2026-06-02 FEATURE
2026-05-29 FEATURE
2026-05-29 FEATURE
2026-05-29 FEATURE
2026-05-29 FEATURE
2026-05-29 CORRECTION
2026-05-28 CORRECTION
2026-05-28 FEATURE
2026-05-28 FEATURE
2026-05-26 UPDATE
2026-05-26 UPDATE
2026-05-26 UPDATE
2026-05-26 CORRECTION
2026-05-26 CORRECTION
2026-05-26 FEATURE
2026-05-26 FEATURE
2026-05-26 CORRECTION
2026-05-26 CORRECTION
2026-05-26 UPDATE
2026-05-26 CORRECTION
2026-05-25 CORRECTION
2026-05-25 FEATURE
2026-05-25 FEATURE
2026-05-25 CORRECTION
ELO engine — two identity-resolution bugs fixed. The name normaliser now strips combining accents, so registry aliases stored with accents (`Damian Flores Díaz`, `Víctor León`) exact-match the ascii forms BCP pairings sometimes render, ending the weekly drag of manual alias_of: resolutions for international competitors. And `name_to_id` is now keyed by the normalised name (rather than the first-observed raw spelling), with the game-log builder normalising each game's player names before the lookup — so a competitor whose pairings render with mixed case across events resolves to one id rather than crashing the engine with a KeyError (the cause of last night's W22 run failure). The alias-index builder also emits a stderr WARN when two distinct registry players collide on a normalised key. Math and ratings are unchanged; ratings_current.json and ratings_history.json are not touched by this patch.
2026-05-25 FEATURE
2026-05-25 FEATURE
2026-05-25 FEATURE
2026-05-25 FEATURE
2026-05-25 FEATURE
2026-05-25 FEATURE
Visual redesign — Phase 3 (the redesign is complete). The three UI kits ship as shared classes in the stylesheet: Quantum surfaces (matchup matrix with the seven-stop diverging heatmap, Vital Signs freshness panel, dispatch list), the Awakenings dispatch reader (Inter prose with the emerald drop-cap, display-face pull-quote, stat callout, sticky TOC sidebar, reading-progress bar), and the Matrix leaderboard family (sortable ELO table, RAW / THEORY-ADJ / PERF-ADJ segmented control, provisional banner, mover lists, skill-premium cards, Captain Decision retrospective card). Two shared inline motion controllers — the Reanimation counter (numbers tick up to value on enter-viewport, prefers-reduced-motion honoured) and the reading-progress bar — load site-wide; both are data-free and the eight long-form pages opt into the progress bar today. The Phase 1 alias bridge is now deleted; the stylesheet reads exclusively against the new design-system tokens.
2026-05-25 FEATURE
Visual redesign — Phase 2. The shared component layer migrates to the design system: sharp-cornered chrome with border-driven hierarchy, the two-line nav with an emerald left-edge mark on the active section and a top-edge ignite on hover, the four-way theme control as monolithic display-face buttons, and the full design-system component class library (cards, tables, buttons, chips, fields, tabs, faction rows, tier buckets, status bar, footer) added to the stylesheet. Every alias-bridge reference across the site rewrites onto the real new tokens; the bridge is kept as a safety net for the final Phase 3 cleanup.
2026-05-25 FEATURE
Visual redesign — Phase 1. The token layer is rebased onto the Claude Design handoff bundle: pure-black OLED ground with a single Cryptek-emerald accent, sharp monolithic corners, and the Orbitron display face. Four themes ship — Nebula (the new default) / Graphite / Light (all three sharing the emerald chrome) / Theme (the launch phosphor data-terminal, retained and re-expressed in the new token system, scanline overlay kept). An alias bridge keeps every existing rule rendering correctly in the new palette while components migrate in Phases 2 and 3.
2026-05-24 UPDATE
2026-05-24 FEATURE
Theme system overhauled. Graphite (slate-grey / indigo) is the new default; the phosphor-green data-terminal aesthetic moves to a dedicated 'Theme' option and renders byte-identical to before; Light is rewritten in a blue-accent palette; a fourth option, Nebula (near-black / purple), joins the toggle. Heading and body fonts split — DM Sans for headings, Inter for body across the three proportional themes; 'Theme' keeps its monospace stack. Reader is retired; a saved Reader preference falls back to Graphite, a saved phosphor selection lands on the relabelled 'Theme'.
2026-05-24 FEATURE
2026-05-24 FEATURE
2026-05-22 FEATURE
2026-05-22 FEATURE
2026-05-22 CORRECTION
2026-05-22 FEATURE
2026-05-22 FEATURE
2026-05-22 FEATURE
2026-05-22 FEATURE
2026-05-22 FEATURE
2026-05-22 FEATURE
Added a small Archivist data-stream easter egg, hidden behind a triple-click on the Quantum dashboard's status-bar cube.
2026-05-21 FEATURE
Added Reader — a third site theme — alongside Dark and Light, with a three-way segmented control in the header.
2026-05-21 FEATURE
2026-05-21 FEATURE
2026-05-21 CORRECTION
2026-05-21 UPDATE
2026-05-21 DATA
2026-05-21 FEATURE
The Archive flipped from pre-launch posture to public launch — stale 'pre-launch' labels removed, data-provenance lines added across the dashboard.
2026-05-20 FEATURE
2026-05-20 FEATURE
2026-05-20 FEATURE
2026-05-20 FEATURE
2026-05-20 DATA
2026-05-19 FEATURE
2026-05-19 FEATURE
2026-05-17 FEATURE
2026-05-16 FEATURE
2026-05-15 FEATURE
2026-05-15 FEATURE
Site Phase 1 complete: shared base layout, the six section landings (Quantum, Awakenings, Protocol, Dossiers, Matrix, Wayfinder), and the phosphor data-terminal design language.
2026-05-14 FEATURE
Initial repository scaffold — the Pairings Tool, the WTC-solver reference implementation, and the early dispatch-page convention that the rest of the site grew from.