feat: the redesigned Event Clock

The new reader app replaces the old UI: Checklist with a rail (focus
pills, Next to expire, today's dailies, pinned routines), Timeline in a
new and a classic look, Routines, Archive and a Settings area, in a
Structured (default) and a Relaxed interface. It follows the approved
Round 6 B and Round 7 mockups, corrected screen by screen with the owner.

Reader data moves to a v2 store (gacha-tracker:v2:*). Existing v1 data
is migrated on first load, a recovery copy is written first, and the v1
keys are never removed, so a rollback finds them unchanged. Redeem codes
for Genshin arrive as their own feed.

Also: live's urgency ramp, editable per theme; completion and
section-complete fireworks; a returning-user tour; the design mockups,
specs, plans, reviews and handoff record.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/design-reviews/2026-10-16-redesign-implementation.md

@@ -0,0 +1,125 @@
+# Approved redesign — implementation review, 2026-10-16
+
+**Status: rejected by the owner for substantial divergence from the approved Round 7 markup.**
+The completion claims below describe the earlier implementation report and are withdrawn as
+evidence of design acceptance. Functional tests and overflow checks did not establish visual or
+interaction fidelity. A faithful markup-to-component correction is still required.
+
+The approved [spec](../superpowers/specs/2026-10-16-ui-redesign-design.md) and
+[16-task plan](../superpowers/plans/2026-10-16-ui-redesign.md) are implemented in the working tree.
+Execution was Native. Nothing has been committed, pushed or published.
+
+## Delivered
+
+Relaxed (Round 7, default) and Structured (Round 6 B rail) share one reader/component tree; Appearance
+switches between them independently of theme, palette and Standard/Compact density. The redesign
+includes Routines and view pins, direct daily ticks, configurable grouping, multi-server progress,
+reset override/revert with accessible clock history, game colours/source credits, custom palettes,
+Automatic/IANA timezone, new and returning onboarding, compact source/new-event/code notices,
+Archive/story statistics, timed Done/Ignore/Undo, local rolling backups and recoverable restore.
+Settings About preserves the colophon; Changelog has its own page and no footer link.
+
+The codes feed contains ten real Genshin codes from the pinned Game8 capture. Source fetching remains
+deterministic and shares the existing conduct gates; no additional community requests were needed
+while implementing or reviewing. Unstated expiry stays unknown. Codes newness and per-server
+redemption are separate. Manual refresh checks both feeds and discloses partial code-feed failure.
+
+## Verification
+
+- **1,587 tests pass**, zero failures, across 74 files. Strict TypeScript and whitespace checks pass.
+- The suite also runs without `public/` or `docs/` in the Docker COPY layout: 1,586 pass, one
+  intentional README-only skip, zero failures. No tests depend on a preceding build.
+- Full offline build passes: 209 events across 20 games, ten codes, production JS/CSS/static shell.
+  Final shell build `f5b25675010f` was loaded on a fresh origin (port 41880).
+- Chrome checks cover both interfaces, both themes, 1440/390 widths, Standard/Compact, reduced motion
+  and an effective 200% CSS viewport. No horizontal page overflow or page errors in that matrix.
+- Browser journeys pass for migration, saved preferred Timeline, events-only setup, selectable empty
+  tracking kinds, upcoming placement, isolation from unselected games, extra server with fresh state,
+  direct ticks, reset override/revert/history, per-server redemption, Done/Ignore/Undo, unknown-end
+  custom creation, real export download/upload/restore, backup preview/restore/Undo, custom palette,
+  timezone selection/search, offline reload and the real service-worker update/reload handshake.
+- Two real browser tabs save concurrently with Web Locks explicitly disabled: IndexedDB serialization
+  preserves both edits. Unit regressions cover stale progress fields and independent routine pins.
+- A fresh independent reviewer completed whole-change review and focused re-reviews. All important
+  findings were fixed with reproductions; final review reports no remaining important findings.
+
+## Review fixes and durable decisions
+
+Deleted custom definitions no longer reappear from seen snapshots. Progress imports preserve local
+active reset configuration, retain imported clocks as history, and reuse those revisions on repeated
+imports. Opaque extensions survive subsequent transfers without duplicate accumulation. Timeline
+focus applies to routines as well as events; Ending soonest uses one global queue when reset strips
+are off. The browser fallback uses an IndexedDB transaction rather than unlocked whole-envelope
+writes. Account rebase preserves independent routine/pin edits and explicit retirement removal.
+
+Original v1 bytes remain available after migration. Restore validates account/clock references and
+saves recovery before replacement. Setup completes before seen-history capture. Source diagnostics
+state what the feed records; absent failure reasons are described as unavailable, never guessed.
+
+## Practical limits
+
+Backups are browser-local and created while the app is used; they cannot recover storage a reader
+clears. Older completion IDs whose metadata was never retained remain recoverable raw data, but
+cannot produce invented archive descriptions or historical statistics. Codes currently have one
+registered game/source. External fonts have system fallbacks offline. Calendar-date code expiry is
+shown as a date without an invented instant. No accounts, remote sync or push notifications added.
+
+## Captures inspected
+
+[Relaxed, light, desktop](assets/2026-10-16-redesign/relaxed-light-1440.png) ·
+[Structured, dark, desktop](assets/2026-10-16-redesign/structured-dark-1440.png) ·
+[Structured, dark, phone](assets/2026-10-16-redesign/structured-dark-390.png)
+
+Additional transient browser logs and captures are in `/tmp/redesign-browser-*` and
+`/tmp/redesign-final-*`; the facts above and representative images are recorded here for handoff.
+
+
+## Follow-up: first-visit HTTP/WireGuard startup failure
+
+The owner reported the recovery screen on first visit through WireGuard `10.20.20.2`. The precise
+failure reproduced in Chrome at an ordinary HTTP hostname: `crypto.randomUUID` was undefined,
+initial account minting threw, and initialization returned the generic unavailable/saved-data error.
+Localhost-only verification had missed this because localhost is a browser secure context.
+
+All reader ID consumers now use 128-bit `crypto.getRandomValues` through `state/reader/ids.ts`.
+Three new regressions failed before the fix and pass afterwards. Browser verification on an actual
+insecure HTTP origin passes both existing-save migration and fresh setup, ordinary edits, adding a
+server, reset override/revert, backups and reload; the original v1 bytes remain unchanged. Focused
+independent review found no important issues. The full suite now passes **1,590 tests** across 75
+files. Typecheck, production rebuild and whitespace checks pass. Rebuilt shell: `9752bd6bf1d2`.
+
+The existing preview serves the rebuilt files; hard-refreshing bypasses the browser's cached JS.
+No storage deletion or identity remapping was performed.
+
+
+## Owner rejection: markup fidelity
+
+Direct comparison confirms substantial divergence despite matching outer gutters/panels/fonts:
+
+- Round 7's event-entry structure separates event content, a large deadline with supporting text,
+  and chevron. Production reused EventRow's prior internal structure and decorated it with CSS.
+- Round 7's Routines uses game bands and aligned columns for progress, cycle/reset, pins and menus.
+  Production renders a flattened library with checkbox options and no equivalent table structure.
+- Round 7's settings sidebar includes individual game entries with descriptions, leading into their
+  profiles. Production substitutes a generic Your games page and game selector.
+- Round 7's Timeline places routine periods/progress/reset markers on the shared time axis.
+  Production appends ordinary routine controls below event timelines and uses textual reset strips.
+- Round 7's Archive story includes interactive per-game outcome breakdowns. Production substitutes
+  per-game text totals.
+- The approved header has navigation counts and a dedicated Settings placement. Production uses
+  the simpler generic navigation and a different header summary.
+
+References: design/mockups/round7/converged.html (final CSS from line 1003 onward and final renderer
+overrides); production ReaderApp.tsx, EventRow.tsx, TimelinePage.tsx, RoutinesPage.tsx,
+SettingsLayout.tsx, GameSettings.tsx, ArchiveStory.tsx. Earlier render functions/CSS in the mockup
+are superseded by later overrides and must not be used in isolation.
+
+Root delivery error: the implementation preserved/reused existing presentation components and
+added selected reference styling instead of faithfully translating the approved rendered markup.
+Verification checked functionality and overflow without comparing equivalent reference/production
+screens and interactions. The final review concentrated on data preservation and did not close that
+design-fidelity gap. The owner should not have had to identify it after a completion claim.
+
+No implementation edits or data resets were made during this rejection audit. Existing storage and
+HTTP fixes remain in place. Required correction: use the approved rendered markup, hierarchy and
+interactions as the presentation contract, then connect real reader data and compare matching states.

docs/design-reviews/2026-10-16-redesign-round4.md

@@ -0,0 +1,167 @@
+# Routine redesign: Round 4 review
+
+This records the owner's decisions from three mockup rounds and the subsequent review on
+2026-10-16. These are proposed product changes, **not shipped behaviour**. The implementation spec
+and migration plan come after review of this combined prototype.
+
+## Review artifact
+
+Open [the standalone Round 4 prototype](../../design/mockups/round4/converged.html) in a browser.
+The review copy is also placed in `~/gacha-mockups/round4/converged.html`, linked from the existing
+Samba index. Earlier rounds remain intact there.
+
+The prototype extends the Round 3 archive variant, keeping its ruled timetable visual language and
+routine library. It is deliberately separate from the production app. Its storage namespace is
+`event-clock:mockup:round4:v1`, never a production `gacha-tracker` key. Reset demo restores sample
+state; reloading otherwise keeps density, choices and progress where browser storage is available.
+
+## Decisions to preserve
+
+- Checklist and Timeline retain their names. Routines and Archive have their own tabs, as does
+  Settings. Settings uses a sidebar with General first.
+- Routines owns follows, individual editing and independent Checklist/Timeline pins. Built-ins do
+  not appear under Your own events and games. The library puts Create your own routine first.
+- Checklist keeps compact per-game routine summaries in its rail. Focusing a game expands its
+  routines; All collapses them. Remove the unrelated Your own events callout from the rail.
+- The main event list has two densities: Standard by default, with wrapping titles, breathing room
+  and supporting copy, and Compact using the dense table. Density is remembered and independent of
+  routine pins, filters, sort order and Timeline. Both densities open the same event detail.
+- Game setup offers composable Events / Dailies / Weeklies & monthlies / Cycles shortcuts; individual
+  follows remain editable in Routines. Events is a visibility choice, rather than a routine.
+- Each game can have multiple servers, with separate routine and daily progress. An additional
+  server starts with events only and fresh routine choices; it does not copy the first server's
+  follows, pins or ticks.
+- Onboarding begins with events only. Explain each type in plain language, especially cycles:
+  routines following the game's own cadence, such as a mode resetting every fourteen days. Ask
+  whether Checklist or Timeline should open first. Defer pin placement until readers have seen the
+  views.
+- Returning readers receive an introduction to the new layout in either main view, with existing
+  choices and progress preserved. Changelog remains accessible afterward.
+- Codes and About live beside Setup in the game's settings area. In-app notices appear in both
+  main views. New means discovered since the reader last viewed that game's codes, not unredeemed.
+  Viewing clears the new indicator without marking redemption. Redemption is separate per server.
+- Archive defaults to per-game groups, with the ledger's story panel and small statistics above
+  them. History timeline is an additional view. Records remain in the save, with description,
+  source and progress available after the live source changes.
+- Done and Ignore immediately save an archive record, then retain the active row for about 1.5
+  seconds with Completed/Ignored · Moved to Archive before fading and closing the gap. Undo remains
+  available afterward; Restore also lives in Archive. Reduced motion keeps the confirmation delay
+  and removes the fade. Unknown end dates stay unknown in archived records.
+- Expired unfinished events belong in Archive as unfinished, rather than silently disappearing.
+- Timeline uses full rows for routines. It offers Ending soonest and By game. Separate reset strips
+  are optional and sit directly below their own game's events on the same axis. In separate-strip
+  mode, Ending soonest orders game groups by their next deadline to preserve this adjacency.
+
+## What to review
+
+1. Compare the same 21 events in Standard and Compact; focus Genshin and inspect its routine rail.
+2. Complete or ignore an event, observe confirmation/fade, Undo, then open its saved Archive detail
+   and Restore it. Try an event with no announced end.
+3. Follow/unfollow a routine from the library and pin it independently to each view.
+4. Add a server in game settings and confirm the other server's choices and ticks stay separate.
+5. Open Codes, mark one redeemed on a single server, and simulate a new arrival from the demo bar.
+6. Compare the per-game Archive with History timeline, and check both timeline reset layouts.
+7. Walk through New user, then Returning user with Timeline as the default.
+
+## Owner's feedback after Round 4
+
+The combined prototype was received positively. Further requirements:
+
+- Restore the richer statistics from Round 3 H's Ledger with a story. Round 4 reduced that panel
+  to completed/ignored/unfinished counts, which lost what the owner liked. Keep the per-game
+  archive as the default body, but restore the completion percentage for the current month with
+  an overall comparison, current/best completion run, logged event check-in days, and unfinished
+  events with near-miss detail. Retain the compact per-game outcome breakdown from that panel.
+  Ignored events must not be counted as failures in the completion percentage. Definitions and
+  scope labels must be explicit: recorded archive history is not all play history, event check-in
+  totals are not unique calendar days, and incomplete/unknown progress cannot support a fabricated
+  near-miss claim. These statistics should use saved progress and dates, not invented telemetry.
+
+- Keep the colophon, potentially in Settings, and add an app-level About section distinct from a
+  game's About tab. Preserve source/studio credits, author and contributor acknowledgements and
+  useful project links. Moving credits must not hide the feed-age and stale-source disclosures
+  that readers need while looking at deadlines.
+- The grouped routine summaries are easier to scan but add friction to ticking daily chores.
+  Explore a separate daily panel with directly available one-click ticks, selectable as an
+  alternative to grouping dailies with the other routines. Keep server progress separate and
+  avoid showing the same tick in both panels. Placement and default are not yet settled.
+- Appearance should support colour schemes in addition to dark/light/system. The choice between
+  curated palettes and reader-edited colours remains open. Any scheme must preserve game identity,
+  urgency meanings, and readable contrast in both modes.
+- Each game's Settings → Setup includes a custom game-colour control, a preview and Reset to
+  default. Remember the override and apply it consistently wherever that game appears, including
+  Checklist, Timeline, Routines and Archive. It belongs to the game, shared across its servers,
+  separately from the global interface colour scheme. Use the existing readable-hue approach to
+  preserve legibility in dark and light appearances without changing the reader's saved base
+  colour. Game colour expresses identity; urgency colours retain their meaning. Export/import
+  must retain these overrides in the eventual implementation.
+- Clarify the additional-server action as simultaneous account tracking. Use “Track another
+  server” with helper text: “Play on more than one server? Add your other server to track both
+  accounts separately.” Keep changing the existing server as a distinct control. The added-server
+  setup still starts with fresh routine choices and separate progress, as previously agreed.
+- Standard event rows without descriptions currently feel too empty. Size rows to their actual
+  content: reserve no description line when absent, reduce vertical padding for title-only rows,
+  and keep the countdown/meter stack from imposing a description-sized minimum height. Preserve
+  wrapping titles and comfortable tap targets; Standard remains roomier than Compact without
+  forcing every event to the same tall height. Do not invent fallback description text to fill
+  the space.
+- Region & time must let the reader select their display timezone. Automatic, using the browser's
+  timezone, is the default; a manual selection is remembered and can be returned to Automatic.
+  Display named IANA zones with their current UTC offsets, so daylight-saving changes follow the
+  selected zone rather than a fixed offset. This affects displayed dates/times, not the server
+  clocks that determine deadlines, reset boundaries and stored game-day keys. Reader-authored
+  event entry must explicitly identify the timezone used to interpret its input.
+- In onboarding's What do you want to track step, all type choices stay selectable even when a
+  game has no current matching routines or windows. Explain the empty state beside the choice;
+  distinguish no current active window from no supported built-in routine. An empty result is not
+  a disabled control. Retain the reader's selected tracking intent rather than deriving it solely
+  from which routines happen to exist today. The implementation spec must reconcile this intent
+  with the earlier shortcut-only composition model and define how newly supported routines are
+  offered without silently expanding what existing readers track.
+- Initial setup also asks for default game server, preferred appearance and whether to show
+  events that have not started. The selected server initializes game setup and individual games
+  can override it. Appearance includes Dark / Light / System and the agreed colour-scheme choices
+  once those are settled. Upcoming events remain off initially, consistent with the existing
+  default, until the reader selects otherwise. The previously agreed Checklist/Timeline default
+  question remains. Present these as a short preferences step rather than crowding the tracking
+  matrix with unrelated controls.
+
+## Prototype boundaries and implementation work still ahead
+
+- “Now” and reset clocks are fixed for review. The final app must use the existing per-game reset
+  rules and actual region-specific end times.
+- Most event content was carried over from the earlier prototypes. Codes, historical archive
+  records, version groups and some descriptions are illustrative. No new source fetch runs here.
+  Live-list source links are matched by title against the existing local feed; unmatched sample
+  events receive no invented source URL.
+  Game8's supplied Genshin code page is a source-shape reference, not an implemented adapter.
+- Only in-app code notices are proposed. Push, email and background notifications remain outside
+  the product scope.
+- Some inherited controls remain placeholders: backup and portions of own-event/routine editing.
+- The archive snapshot works within this prototype's save. Production needs an explicit snapshot
+  retention/export format and a policy for capturing events before they drop from the feed.
+- Production needs a reviewed migration for existing progress into per-server storage; no existing
+  event ID, daily ID or day key may be changed casually. The archive and code state also need a
+  documented export/import contract. This artifact is not a storage implementation to copy.
+- `docs/PRD.md`, `docs/DATA-MODEL.md`, `docs/ARCHITECTURE.md`, `docs/DESIGN.md` and the matching
+  AGENTS guidance must be updated with the eventual implementation. They describe the shipped app
+  today, so this review record does not rewrite them as though the redesign had landed.
+
+## Verification
+
+Browser verification and screenshots are performed with scratch-installed puppeteer-core and
+Chrome, at 1440px and 390px. The prototype needs no Bun build or production feed changes. The test
+journeys cover density parity, navigation, completion/ignore delay and Undo, archived detail and
+Restore, separate code visibility/redemption, server setup, reset-strip adjacency, onboarding,
+returning users, persistence, reduced motion and unknown end dates.
+
+Both width passes completed with no JavaScript errors and no page-level horizontal overflow in
+the checked screens. The initial mobile pass caught a confirmation notice intercepting Archive
+row taps; informational notice surfaces now let pointer events through while Undo remains a real
+button. An early verification-script failure also tried to open a Star Rail event after onboarding
+had selected only Genshin; the scenario now resets sample state before testing an unknown end.
+
+Impeccable's mechanical detector reports palette, typography and size differences against the
+**shipped** DESIGN.md, plus inherited stripe treatments. The new Barlow timetable appearance is
+intentional and selected in earlier rounds; this prototype does not rewrite the shipped design
+reference or add detector suppressions. Its visual language remains subject to this review.

docs/design-reviews/2026-10-16-redesign-round5.md

@@ -0,0 +1,112 @@
+# Routine redesign: Round 5 review
+
+This is a review prototype, not a production release or an approved implementation spec. It
+combines the owner's feedback after Round 4, recorded in
+[the preceding review](2026-10-16-redesign-round4.md), and the subsequent freshness, backup and
+focus-bar requests.
+
+Open [Round 5](../../design/mockups/round5/converged.html), or its copy at
+`~/gacha-mockups/round5/converged.html` through the shared index. Earlier rounds remain unchanged.
+
+## What changed
+
+- **One-click dailies:** an optional panel exposes daily ticks directly, separately per server.
+  The alternative groups dailies with the routine summaries. A daily appears in only one place;
+  pins still decide which dailies appear. The separate panel is the prototype's starting choice,
+  to test the owner's request for immediate access; this default remains reviewable.
+- **Focus alternatives:** a labelled game toolbar is the starting choice. The review bar's Focus
+  selector also offers a compact game switcher and a picker at the top of the Checklist rail.
+  Each changes the same focus state and counts, and preserves auto-expanding focused routines.
+  Timeline retains a visible toolbar/switcher rather than acquiring a Checklist rail.
+- **Content-sized Standard rows:** events lacking descriptions use less vertical padding and
+  omit the segmented meter. They retain a wrapping title, countdown and tap target. No filler
+  descriptions are added.
+- **About and colophon:** Settings → About Event Clock retains the author, source communities,
+  studio credits, acknowledgements, reset-clock reference, disclaimer and project links. The
+  footer links there. Source credits come from the existing local feed, not the selected games.
+- **Freshness:** Checklist and Timeline visibly state data age and warn about older schedules for
+  the games switched on. Source breakdown distinguishes last successful check from last content
+  change and explains unchanged pages, overdue pulls and never-fetched data. Unknown causes are
+  described as unreported, not invented. Settings → Data & sources exposes the same information.
+  The review bar offers Current / Some stale / All stale / Never fetched / Offline. These are
+  labelled illustrative states; no real fetch runs. Check for new data demonstrates a no-newer-feed
+  result and is disabled offline. The headline data timestamp covers the demo feed as a whole;
+  warnings and named source rows cover selected games. No build timestamp is used.
+- **Appearance:** Dark / Light / System plus three curated scheme previews, Slate / Warm / Plum.
+  This answers the palette request for review, not the unresolved possibility of a fully editable
+  interface palette. Semantic deadline colours remain separate from game identity.
+- **Game colour:** Setup adds a colour picker, hex input, preview and Reset to default. An override
+  applies to all the game's servers and all its views. The stored base colour remains unchanged
+  while its rendered colour is adjusted for contrast in the chosen appearance.
+- **Timezone:** Automatic is the default; named zones can be selected and searched in Region &
+  time. Dates use the selected zone, including daylight saving, without changing server reset
+  boundaries. The prototype's per-game reset clocks remain simplified.
+- **Additional servers:** “Track another server” explains simultaneous separate account tracking.
+  Added servers still start with fresh routine choices and progress.
+- **Onboarding:** initial preferences now ask default server, mode/scheme, timezone and whether
+  upcoming events should appear. Game selection, tracking types and Checklist/Timeline default
+  follow. All tracking types remain selectable even if no matching built-in exists. Availability
+  is explained, and selected intent is saved separately from actual follows. The no-matching-types
+  message does not incorrectly call that selection events only. New supported built-ins are
+  described as offers for review rather than automatic extra work for existing readers.
+- **Archive story:** restores monthly/overall completion percentages, current/best completion
+  run, logged event check-ins and unfinished/near-miss counts, plus per-game outcome bars, above
+  the default per-game archive. Ignored events are excluded from completion-rate denominators.
+  Progress and statistics derive from illustrative saved archive records, and scope is labelled.
+  History timeline remains an alternate view.
+- **Automatic backup history:** Backup shows seven daily, four weekly and six monthly snapshots,
+  with latest-per-period compression. The retained historical examples are labelled sample; today's
+  snapshot updates from the demo's own state. Restore previews game/routine/archive/progress counts
+  and preserves current data as a recovery copy first. Undo last restore is available. Manual
+  Back up now and demo JSON export/import live alongside the automatic history.
+
+## Backup semantics used for this review
+
+The most recent seven days retain one latest snapshot per day. Older snapshots fold into four
+consecutive seven-day windows. Older records then fold into six calendar-month buckets, keeping
+the latest snapshot in each. This is up to seventeen retained snapshots, plus a recovery copy from
+the last restore. No snapshot is invented for a day the reader never opened the app.
+
+The demo clock is fixed and its bucket calculations use UTC. Production needs to settle and
+document the stable calendar basis independently of display-timezone changes, handle storage
+capacity/failures, validate restore files, and use the real export contract. Backups are browser
+local and are created while the app is used; they cannot be promised for days when it stays closed.
+Export remains the way to keep a copy outside that browser or move to another device.
+
+## How to inspect
+
+1. Compare focus options in the review bar. Focus Genshin; tick EU and Asia dailies separately.
+2. Compare Standard/Compact, especially rows without descriptions, and switch the daily layout.
+3. Use the Data selector to inspect every freshness state, then expand Why the data is older.
+4. Open About, Data & sources, Region & time and Appearance. Change timezone, scheme and game colour.
+5. Open Archive to inspect richer stats and History timeline.
+6. Open Backups, review a monthly sample, restore it, then Undo last restore. Demo export files are
+   separate from the production app's format and storage.
+7. Open New user. Choose preferences and Genshin, then select Cycles despite no matching built-in.
+8. Set Timeline as the default and use Returning user to check the introduction appears there.
+
+## Verification and boundaries
+
+Chrome journeys at 1440px and 390px exercised direct daily ticks, layout choices, focus alternatives,
+freshness variants, credits, timezone persistence, light/dark/system and schemes, game-colour reset,
+fresh server setup, Archive stats, backup restore/recovery, onboarding with an empty type,
+returning-reader introduction and completion/Undo. Both passes had no JavaScript errors and no
+page-level horizontal overflow in the checked screens. A follow-up checked latest-per-period
+retention across 400 simulated days, all-games empty-type toggles, and desktop sticky toolbar/rail
+separation.
+
+The mechanical design detector reports 30 findings, chiefly differences from the shipped palette,
+Barlow typography and size/radius ramp, plus inherited archive stripe treatments. These are review
+artifacts in the owner-selected replacement visual direction; no production design reference or
+detector suppression was changed to make the prototype appear to match the shipped app.
+
+An inherited Round 4 Reset handler initially discarded the new state fields. Round 5 now owns
+reset initialization and its browser check passes. The active prototype data namespace is
+`event-clock:mockup:round5:v1`; production localStorage keys and progress are untouched.
+
+The existing demo library/create form, independent pins, completion confirmation/fade/Undo,
+Archive restore and code-newness/redemption distinctions remain. Some inherited own-event editors
+are still placeholders. Codes, old Archive history, backup history and source health are sample
+content. Real parsers, source refreshes, app storage migrations and production backup machinery are
+not implemented by this artifact. The shipped specification and design documents remain about the
+shipped app until the redesign's spec and implementation are reviewed.

docs/design-reviews/2026-10-16-redesign-round6.md

@@ -0,0 +1,105 @@
+# Routine redesign: three quieter layouts
+
+Review artifacts, not a production release. This round responds to the owner's concern that
+Round 5's focus toolbar and stale-data notice occupied too much space, and incorporates the
+additional feedback received while building the alternatives.
+
+Open [the comparison index](../../design/mockups/round6/index.html). The shared copy lives at
+`~/gacha-mockups/round6/index.html`; earlier rounds stay available. Each design is a complete
+standalone HTML prototype with the same sample event data and the shared features below.
+
+## The alternatives
+
+- **A — Inline desk:** retains the left routine/daily rail. Game focus is a small selector beside
+  the event heading, and freshness is a single understated line. Source reasons are one click away.
+- **B — Game desk:** puts game focus, daily ticks and a short source-status report in the rail.
+  There is no full-width freshness or focus band above the event list. It reserves more attention
+  for the list; its tradeoff is a more populated rail that stacks before events on mobile.
+- **C — Open ledger:** replaces the rail with a full-width event list, a brief next-deadline row,
+  direct daily ticks in a horizontal strip, and a disclosure for other pinned routines. Game focus
+  and a short freshness report sit with the event heading. It gives titles the most width; the
+  routine controls scroll with the list.
+
+The chosen timetable appearance is preserved. These compare structure and interaction rather than
+asking the owner to pick a new visual identity again.
+
+## Shared decisions implemented for review
+
+- **Changelog is its own Settings page.** The owner explicitly chose this over a main app tab,
+  and explicitly declined a footer link. Remove the awkward Changelog button from About, remove
+  it from the footer, and render release notes in the page rather than the old overlay. Existing
+  returning-reader news links lead to that Settings page.
+- **Freshness remains honest and available.** Keep the full data timestamp and age in the footer,
+  scope warnings to selected games, and expose successful-check/content-change times and reasons
+  in Data & sources. Older source data is also explained in the event's detail. Unknown causes
+  remain unreported, not invented. The review bar's Data selector tests the illustrative scenarios.
+- **Dailies on Checklist belongs in Routines as well.** Routines → Checklist display controls the
+  same preference as the daily panel shortcut and Appearance. Choose Separate panel or Grouped
+  with routines. Independent pins still govern whether a routine appears.
+- **Checklist routine groups have three behaviours:** Collapsed by default, Expanded by default
+  (still collapsible), and Always expanded (no collapse buttons). Focusing a game expands its
+  routines. The wide layout also honours this for its enclosing routine section.
+- **Numeric fields show the native stepper.** Browser increase/decrease controls remain visible
+  and use step one, as requested. They are not replaced by a separate custom spinner.
+- **Appearance includes Custom.** Edit background, surface, text and interface accent separately
+  for light and dark. Stored choices are retained while preview text/surfaces are adjusted for
+  contrast. Game identities and deadline urgency remain separate from the custom interface accent.
+  Individual game colours retain their own control and reset.
+- **Reset timing can be overridden per game/server.** Game Setup and Region & time expose Automatic
+  versus a custom server-local hour/minute, with Revert to Automatic. The prototype applies the
+  override consistently to daily/routine periods and reset summaries. Reader-authored routines
+  with their own explicit reset retain it. The automatic source clocks remain simplified here;
+  this is not a production reset migration.
+- **A game's About names its sources.** Links come from that game's entries in the existing local
+  feed, including separate event/banner/pass sources. Use readable schedule labels and thank the
+  editors. This differs from the global About's full, unfiltered colophon.
+- **Remove Done and ignored events from Lists.** That row only linked to Archive and was not a
+  setting. Archive keeps its own main navigation tab.
+- **Backup rows say View backup.** They open a preview headed Backup from [date], showing the
+  snapshot's contents. Restore this backup is the explicit action there; the current state is
+  preserved as a recovery copy. The seven-day/four-week/six-month history is retained.
+- **Returning readers get a guided introduction.** The review bar's Returning user control opens
+  a short welcome in whichever view is preferred, with Take the quick tour and Keep browsing.
+  Four steps visit Routines, Checklist, Archive and Settings. Back and Skip are available; finishing
+  returns to the preferred view. Games, follows and progress remain intact. Production will bind
+  this to a saved release marker, so it is offered once rather than every load.
+- **Upcoming events moves to What do you want to track?** It is no longer in the initial preference
+  step. The initial preferences retain default server, appearance and timezone; all type choices
+  remain selectable and explained even when no matching built-in exists.
+
+Standard/Compact density, richer Archive statistics and the history timeline, separate server
+progress, code-newness versus redemption, completion confirmation/fade/Undo, timezone and the
+existing routine library/create form remain available in every alternative.
+
+## Boundaries
+
+Each alternative uses its own `event-clock:mockup:round6:<letter>:v1` browser namespace. No production
+keys, parsers or feed data are changed. Source-health states, codes, archived history and historical
+backups are illustrative. Clock overrides affect the demo's period calculations, not any real stored
+game-day keys. Production must review migration and the preservation of historical ticks before
+introducing reader overrides. These are disposable prototypes, not code to transplant into the app.
+
+## Verification record
+
+The browser pass checks all three designs at 1440px and 390px: focus and daily controls, native
+numeric stepping, all disclosure modes, source reasons in event detail, the Changelog page and its
+absence from About/footer, custom-palette contrast, reset override/revert, per-game source credits,
+Lists cleanup, backup labels, the moved upcoming option, and the returning-user tour preserving
+progress. Screenshots cover each main layout plus the new shared pages.
+
+The first mobile pass found a backup-preview smooth scroll continuing after navigation, allowing a
+subsequent automated tap to hit the fixed review bar. The preview now scrolls instantly, avoiding a
+pending animation against a different screen.
+
+The confirming pass completed all six combinations of design and viewport with no JavaScript
+errors or page-level horizontal overflow in the checked screens. Custom-palette checks included
+equal chosen background/text colours and confirmed the rendered text was adjusted to at least
+4.5:1. Per-server override checks exercised 05:30, verified the 90-minute change from 04:00, then
+returned to Automatic. The tour returned a Timeline-default reader to Timeline with saved games,
+follows and progress unchanged.
+
+Design-hook triage: retain the owner-selected Barlow typography. Narrow value exceptions for that
+font are scoped to `design/mockups/round6/index.html` only, with evidence in `.impeccable/config.json`.
+No whole-file or whole-rule exclusions are added. The shipped DESIGN.md remains the production
+reference; prototype differences in palette/size and inherited archive treatments remain review
+findings rather than being suppressed broadly.

docs/design-reviews/2026-10-16-redesign-round7.md

@@ -0,0 +1,80 @@
+# Routine redesign: one airier design
+
+**Later owner decision:** retain two interfaces after all: Round 7 and Round 6 **B**, selected
+in Settings. The earlier single-interface direction below records the mockup review, not the
+final implementation decision. Replace “Older schedules” with “Event data may be out of date”.
+See the [production redesign specification](../superpowers/specs/2026-10-16-ui-redesign-design.md).
+
+Review prototype, not shipped behaviour. Open
+[the unified mockup](../../design/mockups/round7/converged.html), also copied to
+`~/gacha-mockups/round7/converged.html` through the shared index.
+
+## The owner's correction
+
+Round 6's three alternatives were rejected. The owner asked for:
+
+- Older-data notices in the same structure as New since you last looked, appearing only when
+  games have older data.
+- The current production game's focus-pill structure, placed at the top of the left rail as in B.
+- A more airy, easy-to-read design informed by the original
+  `~/gacha-mockups/c-one-due-list.html`.
+
+The initial idea of a Simple mode or a spacing toggle was then explicitly reconsidered: the owner
+does not want two distinct UIs. Carry the spirit of C into one unified interface instead.
+
+## What this mockup does
+
+**A shared updates area.** New code notices and Older schedules use two compact rows in one
+component above the Checklist's event list and above Timeline. The older row lists affected games
+and links to Details & reasons; no full-width health banner or rail status panel remains. It is
+absent when the selected games have current sources. If there are no new codes either, the whole
+updates area disappears. Source reasons remain available in Data & sources and event detail; the
+full feed timestamp stays in the footer on every load. Scope is the games the reader has switched
+on, rather than only the temporary focus. Repetitive older-data labels on individual list rows are
+removed because the updates row already names those games.
+
+**The existing focus behaviour.** `src/client/components/GameFocus.tsx` is the reference: All and
+game pills, game hues, outstanding counts, and Next progressing through games and then back to All.
+Tapping the focused pill returns to All. Pills wrap in their own panel at the top of the Checklist
+rail; they are absent for a single-game setup. Timeline uses the same pills above its lanes. Focus
+never changes which games are followed.
+
+**One visual world.** The original C informs separated panels, quieter rules, softened surfaces,
+more room around controls and a warmer reading rhythm. Bricolage Grotesque and Figtree replace the
+compressed timetable typography consistently across the prototype, including settings and forms.
+The rail and event list have a real gutter; focus, deadline, dailies and routines have separated
+surfaces. Light mode uses warm paper and dark mode a softer charcoal. No Simple/Detailed mode or
+global spacing toggle is added. Standard/Compact remain two row densities of this same appearance.
+Rows with no description remain shorter; comfortable layout is not a fixed tall event height.
+
+Direct daily ticks, routine disclosure choices, independent pins, custom palettes, per-game colours
+and reset overrides, source links and thanks, Changelog in Settings, Archive statistics and history,
+backup history/recovery, timezone and both onboarding flows remain available. The daily-panel layout
+shortcut is removed from the Checklist rail to reduce controls there; its Routines and Appearance
+settings continue to edit the same preference.
+
+## Validation
+
+Chrome journeys at 1440px and 390px passed with no JavaScript errors and no page-level horizontal
+overflow in the checked views. They cover conditional/scope-aware notices, empty updates, focus
+toggle/advance, spacing, routine expansion, reset override/revert, source credit links, custom
+scheme controls, light-theme game-colour contrast on ground and panel, Changelog location, backup
+history, Archive stats, Timeline, completion/fade/Undo and onboarding. Contrast adjustment now
+considers both panel and page grounds, while retaining saved base game colours.
+
+Screenshots were inspected for Checklist in both appearances, Routines, Data & sources, Archive
+and Timeline. The first verification script used a nonexistent review-bar Settings shortcut; it
+was corrected to use the actual Settings tab. No product change was needed for that script error.
+
+The mechanical design check flags differences from the **shipped** DESIGN.md in palette, type
+size, radius and inherited archive treatments. Those remain review findings, not broad suppressions.
+The intentional Bricolage font exception is scoped to this one prototype file, with rationale in
+`.impeccable/config.json`. The production visual reference is not rewritten before implementation.
+
+## Boundaries
+
+The namespace is `event-clock:mockup:round7:v1`. Earlier mockups and production progress remain
+unchanged. Historical records, codes and source health are illustrative; clocks are fixed and
+automatic reset defaults simplified. No source requests or production parser/storage changes run
+here. This is a disposable visual review artifact; the redesign still needs a reviewed production
+specification and migration plan.

docs/design-reviews/2026-10-17-redesign-fidelity.md

@@ -0,0 +1,101 @@
+# Redesign fidelity correction — 2026-10-17
+
+> **Owner rejected this implementation after browsing it:** “This is still not even close to the
+> mockup.” The completion claim is withdrawn. Screenshots and review verdicts below are historical
+> evidence of the rejected attempt, not acceptance. Continue from
+> [the second-rejection handoff](../handoffs/2026-10-17-redesign-second-rejection-handoff.md):
+> launch the current server, then ask the owner for the biggest differences before further UI edits.
+
+The owner asked to repair the rejected implementation against Round 7 Relaxed and Round 6 B
+Structured, then explicitly made **Structured the default**. Existing saved Relaxed choices remain
+valid. This correction is uncommitted in the existing checkout; no branch, publication or data-source
+refresh was performed.
+
+## What changed
+
+- Checklist uses dedicated reference-shaped event rows and next-deadline panel, with separate copy,
+  countdown, supporting date, segmented meter and detail chevron. Header counts and Settings placement
+  follow the reference. Both interfaces retain the owner-approved focus pills.
+- Routines has By reset/By game bands, aligned game/routine/progress/view-pin/menu columns, live totals,
+  direct daily status, amount bars/inputs, library and a native custom-routine drawer. Bulk pins combine
+  writes per account. Multi-server row identity includes both account and routine.
+- Timeline plots event spans and routine periods on one axis with frozen labels, progress fill and
+  reset markers. In-progress bar labels remain visible after scrolling. Deadline ordering includes
+  routine resets, and separate reset strips remain available.
+- Settings restores separate Default view and Your own events and games pages, game profiles, tracking
+  summaries and Other games. Profiles follow tracking → servers → colour → reset timing. A server
+  selector above tracking keeps choices independent without duplicating tall account panels.
+- Archive restores the story, interactive outcome bars, game sidebar, saved rows and history timeline.
+  Its detail dialog reads saved metadata, original clock region, notes, days and amounts. It does not
+  open the live progress editor or replace historical state with the current clock.
+- Structured defaults agree across prepaint, normalization, setup and applied appearance. No IDs,
+  localStorage key spaces, migrations or ingestion rules were changed by this correction.
+
+## Reference comparisons
+
+Images are in [the evidence directory](assets/2026-10-17-fidelity/). Representative matched views:
+
+| View | App | Approved reference |
+| --- | --- | --- |
+| Structured Checklist | [Desktop](assets/2026-10-17-fidelity/app-structured-dark-1440.png) | [Desktop](assets/2026-10-17-fidelity/reference-structured-dark-1440.png) |
+| Relaxed Checklist | [Desktop](assets/2026-10-17-fidelity/app-relaxed-dark-1440.png) | [Desktop](assets/2026-10-17-fidelity/reference-relaxed-dark-1440.png) |
+| Relaxed mobile | [390px](assets/2026-10-17-fidelity/app-relaxed-dark-390.png) | [390px](assets/2026-10-17-fidelity/reference-relaxed-dark-390.png) |
+| Routines | [Structured](assets/2026-10-17-fidelity/app-structured-routines.png) | [Structured](assets/2026-10-17-fidelity/reference-structured-routines.png) |
+| Timeline | [Structured](assets/2026-10-17-fidelity/app-structured-timeline.png) | [Structured](assets/2026-10-17-fidelity/reference-structured-timeline.png) |
+| Game Setup | [Relaxed](assets/2026-10-17-fidelity/app-relaxed-settings.png) | [Relaxed](assets/2026-10-17-fidelity/reference-relaxed-settings.png) |
+| Archive | [Structured](assets/2026-10-17-fidelity/app-structured-archive.png) | [Structured](assets/2026-10-17-fidelity/reference-structured-archive.png) |
+
+Additional captures cover both themes at 1440px/390px, populated mobile utility pages, compact rows,
+event/archive details, custom-routine drawers, archive history and the Settings pages.
+
+The comparison harness freezes time at 2026-10-16 12:00 UTC and intercepts the event-feed request
+with the prototype's **synthetic demonstration events**. It seeds disposable browser storage with
+matching routine choices and 38 archive snapshots. These fixtures are review evidence only: they
+are not imported by production, copied into public, or written into source snapshots. Actual setup,
+HTTP migration and offline checks use the built app and its real feed separately.
+
+Expected semantic differences: real account rows include Asia events, so totals differ from the
+prototype's game-only event list. One prototype custom task was not seeded. Production has no
+version metadata for archive events, so it groups saved records without inventing version names.
+Real reset clocks and available routines govern progress. Code/release notices reflect actual data;
+Checklist comparisons hide these notices to align the first viewport. The Structured prototype's
+filter dropdown is intentionally superseded by the owner's focus-pill decision.
+
+Reproduce with [fidelity-capture.mjs](fidelity-capture.mjs), from the repository root, setting
+`PUPPETEER_MODULE` to the scratch installation's ESM entry and `APP_URL` / `MOCKUP_URL` to fresh
+running origins. Chrome is `/usr/bin/google-chrome-stable`; the harness maps event-clock.test to
+loopback. Rebuild CSS/JS/static without fetching the feed, and use a new app port after each rebuild.
+
+## Independent review
+
+The first reviewer invocation hit a session usage limit; a retry succeeded. Its initial material
+findings were invisible scrolled timeline labels, substituted Settings navigation, routine column/
+status hierarchy, multi-account row-key collisions, and insufficient populated Archive evidence.
+One follow-up also required correcting the game-profile hierarchy. Each finding was fixed and the
+same screenshot paths recaptured. Final independent verdict: **“ship the reviewed corrections.”**
+All reported material findings were resolved. This verdict is scoped to the compared screens and
+reported fixes; it is not owner acceptance or blanket proof of every interaction.
+
+The Impeccable detector ran once and returned `[]` (no findings).
+
+## Verification
+
+Final browser build: `a28021bbe1a8`, production React/JSX transform, 117 bundled modules.
+
+- TypeScript passes. Full offline suite: **1,594 passed, 0 failed**, 5,410 assertions.
+- Docker-equivalent copied file layout, without docs/design/public: 1,593 passed, one intentional
+  docs-dependent skip, no failures. This validates the COPY-layout assumption; no Docker image was built.
+- Eight interface/theme/width combinations: no document overflow or page exceptions. Both densities,
+  reduced motion/effective 200% viewport, custom palette and timezone selection checked.
+- Ordinary insecure HTTP hostname: new setup, existing v1 migration, daily writes, second server,
+  reset override/revert, backup and reload pass; original legacy bytes retained. Structured is the
+  missing-choice default and saved Relaxed survives reload.
+- Real two-tab simultaneous writes with Web Locks disabled pass using the existing IndexedDB lock.
+  Offline reload passes on localhost's service-worker-capable origin.
+- Final-build interaction checks: multi-server bulk pins preserve the other view's placement; numeric
+  edits and custom-routine creation persist; completion, Undo, archive detail, Restore and Escape pass.
+  Final profile's server/reset controls were rechecked on insecure HTTP after layout changes.
+- `git diff --check` passes. No new runtime dependency, source fetch, commit or publication.
+
+The earlier rejection is preserved in the 2026-10-16 report. Passing tests did not establish its
+visual fidelity; the side-by-side evidence and scoped review above are the correction's design record.

docs/design-reviews/assets/2026-10-17-fidelity/reference-events.json

@@ -0,0 +1 @@
+[{"id":"e0","game":"genshin","title":"Anniversary Memories Album","desc":"Look back through the year's moments in an album and claim Primogems for each page you fill.","start":1790564400000,"end":1792292400000,"src":"https://genshin-impact.fandom.com/wiki/Anniversary_Memories_Album"},{"id":"e1","game":"zzz","title":"Clink, Clank, Pinball Knight!","desc":"A pinball minigame with daily stages; clear them for Polychromes and upgrade materials.","start":1789009200000,"end":1792378800000,"src":"https://game8.co/games/Zenless-Zone-Zero/archives/457176"},{"id":"e2","game":"zzz","title":"Diary of an Orbie Parent","desc":"Raise an Orbie through daily check-ins and small tasks.","start":1790737200000,"end":1792378800000,"src":"https://game8.co/games/Zenless-Zone-Zero/archives/457176"},{"id":"e3","game":"nte","title":"Stamina Recharge","desc":"Spend City Stamina twice as fast in select Hethereau Hobby activities.","start":1791169200000,"end":1792378800000,"src":"https://game8.co/games/Neverness-to-Everness/archives/592073"},{"id":"e4","game":"zzz","title":"Data Bounty - Combat Simulation","desc":"Short combat simulations with bonus rewards for the first clear of each.","start":1791946800000,"end":1792378800000,"src":"https://game8.co/games/Zenless-Zone-Zero/archives/457176"},{"id":"e5","game":"zzz","title":"All-New Program","desc":"","start":1788922800000,"end":1792465200000,"src":"https://game8.co/games/Zenless-Zone-Zero/archives/457176"},{"id":"e6","game":"genshin","title":"Predictive Victory Dynamics","desc":"A combat event in stages; each unlocks a day after the last.","start":1791774000000,"end":1792465200000,"src":"https://game8.co/games/Genshin-Impact/archives/301601"},{"id":"e7","game":"wuwa","title":"Bountiful Crescendo","desc":"","start":1792033200000,"end":1792638000000,"src":"https://game8.co/games/Wuthering-Waves/archives/453473"},{"id":"e8","game":"hsr","title":"4.6 Planar Fissure","desc":"Double rewards from Planar Ornament Extraction, a few times a day.","start":1791774000000,"end":1792897200000,"src":"https://game8.co/games/Honkai-Star-Rail/archives/408749"},{"id":"e9","game":"wuwa","title":"Artisan's Search","desc":"","start":1791428400000,"end":1792983600000,"src":"https://game8.co/games/Wuthering-Waves/archives/453473"},{"id":"e10","game":"wuwa","title":"Waking Moon Fishing","desc":"","start":1792033200000,"end":1793502000000,"src":"https://game8.co/games/Wuthering-Waves/archives/453473"},{"id":"e11","game":"genshin","title":"Battle Pass - Moontrace","desc":"","start":1790132400000,"end":1793588400000,"src":"https://game8.co/games/Genshin-Impact/archives/301601"},{"id":"e12","game":"genshin","title":"To Temper Thyself and Journey Far","desc":"","start":1786330800000,"end":1793588400000,"src":"https://game8.co/games/Genshin-Impact/archives/301601"},{"id":"e13","game":"hsr","title":"Love, Ghosts & Robots","desc":"","start":1790564400000,"end":1794366000000,"src":"https://game8.co/games/Honkai-Star-Rail/archives/408749"},{"id":"e14","game":"hsr","title":"Astral Imagea","desc":"","start":1790564400000,"end":1794366000000,"src":"https://game8.co/games/Honkai-Star-Rail/archives/408749"},{"id":"e15","game":"nte","title":"Pukaland Travelogue","desc":"","start":1790737200000,"end":1794366000000,"src":"https://game8.co/games/Neverness-to-Everness/archives/592073"},{"id":"e16","game":"wuwa","title":"3.7 Moonlit Path","desc":"","start":1790737200000,"end":1794366000000,"src":"https://game8.co/games/Wuthering-Waves/archives/453473"},{"id":"e17","game":"nte","title":"Coal Lumps Treasure","desc":"","start":1791428400000,"end":1794366000000,"src":"https://game8.co/games/Neverness-to-Everness/archives/592073"},{"id":"e18","game":"endfield","title":"Originium Supply Run","desc":"Mockup event so Endfield has a row.","start":1791514800000,"end":1792724400000,"src":null},{"id":"e19","game":"hsr","title":"Free Gilgamesh or Archer","desc":"","start":1784862000000,"end":null,"src":"https://game8.co/games/Honkai-Star-Rail/archives/408749"}]

docs/design-reviews/assets/2026-10-17-fidelity/reference-state.json

@@ -0,0 +1 @@
+{"archive":[{"id":"g1","game":"genshin","ver":"6.0","title":"Thunder Gauntlet Trials","status":"done","start":"2026-08-27","end":"2026-09-08","at":"2026-09-07","desc":"A combat challenge in six stages, one unlocking each day. Each first clear pays Primogems.","moved":false,"prog":{"t":"stages","got":6,"need":6,"unit":"stages","days":[]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g4","game":"genshin","ver":"6.0","title":"Fontinalia Film Festival","status":"done","start":"2026-09-03","end":"2026-09-17","at":"2026-09-16","desc":"Shoot short scenes around Fontaine and trade Film Points in the event shop.","moved":false,"prog":{"t":"amount","got":1200,"need":1200,"unit":"Film Points","days":[]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g5","game":"genshin","ver":"6.0","title":"Mystic Melody Concert","status":"ignored","start":"2026-09-10","end":"2026-09-24","at":"2026-09-11","desc":"A rhythm minigame with daily songs.","moved":false,"prog":{"t":"days","got":0,"need":5,"unit":"days","days":[]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g7","game":"genshin","ver":"6.0","title":"Gilded Winds Exploration","status":"expired","start":"2026-09-12","end":"2026-10-06","at":"2026-10-06","desc":"Explore five wind-swept ruins; each area opens a few days after the last.","moved":false,"prog":{"t":"stages","got":4,"need":5,"unit":"stages","days":[]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g3","game":"genshin","ver":"6.0","title":"Ley Line Overflow","status":"expired","start":"2026-09-15","end":"2026-09-22","at":"2026-09-22","desc":"Double Ley Line rewards, three times a day.","moved":false,"prog":{"t":"days","got":1,"need":7,"unit":"days","days":[6]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g6","game":"genshin","ver":"6.0","title":"Primordial Echoes Web Event","status":"done","start":"2026-09-20","end":"2026-09-27","at":"2026-09-21","desc":"A browser event: check in on three days for Primogems.","moved":true,"prog":{"t":"days","got":3,"need":3,"unit":"days","days":[0,4,6]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g2","game":"genshin","ver":"6.0","title":"Overflowing Mastery","status":"done","start":"2026-10-02","end":"2026-10-09","at":"2026-10-08","desc":"Double Talent Domain drops, three times a day.","moved":false,"prog":{"t":"days","got":6,"need":7,"unit":"days","days":[0,1,2,3,4,5]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"g8","game":"genshin","ver":"6.1","title":"Moonlit Feast Login","status":"done","start":"2026-10-08","end":"2026-10-15","at":"2026-10-14","desc":"Log in on seven days for Intertwined Fates.","moved":false,"prog":{"t":"days","got":7,"need":7,"unit":"days","days":[0,1,2,3,4,5,6]},"src":"https://game8.co/games/Genshin-Impact/archives/297500"},{"id":"h2","game":"hsr","ver":"4.5","title":"Starlight Rhapsody","status":"done","start":"2026-08-13","end":"2026-09-02","at":"2026-09-01","desc":"A story event in eight chapters.","moved":false,"prog":{"t":"stages","got":8,"need":8,"unit":"stages","days":[]},"src":null},{"id":"h3","game":"hsr","ver":"4.5","title":"Gift of Odyssey","status":"done","start":"2026-08-13","end":"2026-09-24","at":"2026-08-20","desc":"Log in on seven days for Star Rail Special Passes.","moved":false,"prog":{"t":"days","got":7,"need":7,"unit":"days","days":[11,12,15,21,25,32,35]},"src":null},{"id":"h4","game":"hsr","ver":"4.5","title":"Aetherium Wars: Final Bout","status":"ignored","start":"2026-08-20","end":"2026-09-23","at":"2026-08-21","desc":"A creature-battling event with a separate shop.","moved":true,"prog":{"t":"days","got":0,"need":10,"unit":"days","days":[]},"src":null},{"id":"h5","game":"hsr","ver":"4.5","title":"Realm of the Strange","status":"done","start":"2026-09-01","end":"2026-09-08","at":"2026-09-07","desc":"Triple relic drops from Caverns of Corrosion, a few times a day.","moved":false,"prog":{"t":"days","got":3,"need":3,"unit":"days","days":[0,2,5]},"src":null},{"id":"h6","game":"hsr","ver":"4.5","title":"Fate's Forge Trial","status":"done","start":"2026-09-05","end":"2026-09-19","at":"2026-09-18","desc":"Trial characters in staged fights; points unlock rewards.","moved":false,"prog":{"t":"amount","got":3000,"need":3000,"unit":"points","days":[]},"src":null},{"id":"h7","game":"hsr","ver":"4.5","title":"Boulder Town Market","status":"expired","start":"2026-09-09","end":"2026-09-23","at":"2026-09-23","desc":"Run a market stall; coins buy materials in the event shop.","moved":false,"prog":{"t":"amount","got":1800,"need":2400,"unit":"coins","days":[]},"src":null},{"id":"h8","game":"hsr","ver":"4.6","title":"Planar Fissure","status":"done","start":"2026-09-26","end":"2026-10-03","at":"2026-10-02","desc":"Double rewards from Planar Ornament Extraction.","moved":false,"prog":{"t":"days","got":5,"need":5,"unit":"days","days":[0,1,2,3,4]},"src":null},{"id":"h1","game":"hsr","ver":"4.6"Line truncated