This log records material changes that affect published content, catalogue coverage, methodology or how public pages are delivered. It does not list routine dependency updates or unpublished work.
Leaderboard submission and results-screen fixes
A production gameplay check identified and corrected two issues affecting legitimate daily-result publication and recap visibility.
Both slider endpoints now remain aligned to the product step after either handle moves or constrains the other handle.
The server continues to reject malformed brackets, while normally played daily rounds can now be published reliably.
Completing the fifth round now returns the viewport to the top of the results screen instead of preserving the previous bottom-of-page position.
Validated public daily-challenge leaderboard
Players can optionally publish a server-recalculated daily result and compare real submissions by day, month or all time.
A new leaderboard page shows up to 100 pseudonymous rankings for a UTC day, month or the full period since launch.
Only daily challenges are eligible; the server rebuilds the deterministic deck and recalculates all five submitted brackets before accepting a result.
Each browser keeps one best score per UTC day, with a five-submission daily limit and no seeded, synthetic or invented entries.
Players can remove all public scores linked to the anonymous device identifier retained in their browser.
Daily challenge and device-local progress
The game gained a deterministic daily mode and optional progress stored only in the visitor’s browser.
A daily five-round challenge now uses the same UTC seed for every visitor without requiring an account.
Completed-game totals, best score, best streak and daily first/best results can be kept locally on the device and cleared at any time.
Each bracket now requires an intentional slider movement before it can be submitted.
Players can report a specific product reference or share a spoiler-free result from the recap.
Catalogue claim and review audit
Catalogue wording and validation were revised so gameplay values are not presented as retailer observations or live market prices.
All catalogue values are now classified visibly as rounded editorial gameplay anchors.
Product counts are derived from the catalogue instead of being repeated manually in page copy.
Temporal wording, scoring precision and duplicate object keys were reviewed and corrected.
The production build now checks identifiers, country coverage, educational fields, local images, review metadata and duplicate value patterns.
Routing and discovery reliability
The public pages now share one route definition across browser navigation and static rendering.
Guide pages are prerendered through React Router, so each slug resolves through the same useParams path used in the browser.
The sitemap and llms.txt are generated from the concrete public route manifest instead of source-code pattern matching.
Sitemap entries now carry route-specific last-modified dates and omit speculative change-frequency values.
The production build now validates every canonical route, including every guide page, before it succeeds.