feat(holodori): track hololive Dreams from its own wiki

New holodoriwiki parser plus the holodori-holodoriwiki-events source,
giving the game its two live and upcoming events at exact precision.

holodori.wiki is Miraheze, so this is the same call bawiki makes and for
the same reason: robots.txt disallows /w/ and /*?action=, which closes the
API route and leaves the rendered /wiki/Events page as the surface * is
allowed. It serves our own User-Agent a 200, sets no Content-Signal and no
Crawl-delay for us, and the wiki is CC BY-SA 4.0.

What makes this source unusually good is that it states its timezone on
every cell — 08/17/2026 8:00PM (JST) — so it is the only wiki source here
publishing exact precision on both boundaries without a per-region timer.
parseSlashClockZone requires that zone rather than defaulting to UTC: a row
that ever loses it drops out instead of silently landing nine hours off,
and an abbreviation absent from the table is refused rather than guessed,
which is why the table holds only JST and not the plausible-looking
candidates that are not fixed offsets. The 12-hour clock gets its own
handling and its own tests, because 12PM and 12AM are the two readings a
naive parser gets wrong while still producing a valid-looking instant.

Inclusion is fenced by the Current Events <h2> and bounded by the next one.
That matters more than it looks: Past Events sits directly below with
identical columns, so a reader taking every wikitable would put the back
catalogue on the calendar with nothing to mark it. Rows are still checked
against ctx.now on top of the heading, because Current is maintained by
hand and goes stale before anyone moves a row down.

Two rows are deliberately missing. Beginner Mission runs Game Launch →
Unknown, and no start means no event ID — a permanent tutorial chore is not
what a calendar of deadlines is for. An Unknown end is kept as endsAt null,
and unlike bawiki this parser does not drop a started-but-undated row: the
heading has already said the event is running, which is the fact bawiki
lacks when reading an archive.

Every event title is still a red link — the wiki has no article for any of
them yet — so each points at ?action=edit&redlink=1, a create-page form on
a path this robots.txt disallows. Refusing a href with a query keeps those
out and falls back to the events page; the articles get linked when they
exist, with no change here.

holodori gets resetOffsets of UTC+9 across all three regions, evidenced
rather than assumed the way Arknights' is: the game launched worldwide
simultaneously on one service, every boundary is stated in JST, and
Training Support Missions ends at 3:59AM JST, one minute before a 04:00
local reset. Only the offset is overridden; the hour is the default.
Setting it now is free, because no reader has a day key for a game the app
has never shipped — the same override a year from now would re-label ticks
already logged.

Both boundaries and the exclusions are asserted against an independent
extraction off the fixture, computed through a timezone library rather than
by the parser's own arithmetic.

Several counts in AGENTS.md and PRD.md were already stale before this — the
Fate/Grand Order source did not update them — and are corrected to what the
tree now holds rather than to what it held yesterday.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

docs/ARCHITECTURE.md

@@ -77,6 +77,7 @@ src/
       akwiki.ts         arknights.wiki.gg mrfz-wtable             ✓ built
       fandom.ts         Fandom via the action=parse API           ✓ built
       bawiki.ts         bluearchive.wiki JP/Global tabber         ✓ built
+      holodori.ts       holodori.wiki Current/Past Events tables   ✓ built
       index.ts          parser registry                           ✓ built
     adapters/
       types.ts          Adapter interface, ParseContext           ✓ built

docs/DATA-MODEL.md

@@ -260,12 +260,21 @@ reader cannot see.
 | Endfield, Europe | 04:00 | UTC-5 (on the Americas server) | 09:00 | 11:00 / 10:00 |
 | Endfield, Asia / Americas | 04:00 | regional default | 20:00 / 09:00 | — |
 | Reverse: 1999, all regions | **05:00** | UTC-5 (one global server) | 10:00 | 12:00 / 11:00 |
+| hololive Dreams, all regions | 04:00 | UTC+9 (one worldwide server) | 19:00 | 21:00 / 20:00 |
 
-Arknights is the one game whose override covers **all three** regions, and it is not a blanket
-per-game offset of the kind this section warns about below: the game genuinely runs a single Global
-server for every region we model. The offset is read off the source rather than assumed — every
-ending event on arknights.wiki.gg carries an exact end of `10:59:59Z`, which is `03:59:59` at UTC-7,
-one second before a 04:00 reset.
+Arknights and hololive Dreams are the games whose override covers **all three** regions, and neither
+is a blanket per-game offset of the kind this section warns about below: both genuinely run a single
+worldwide server for every region we model. Arknights' offset is read off the source rather than
+assumed — every ending event on arknights.wiki.gg carries an exact end of `10:59:59Z`, which is
+`03:59:59` at UTC-7, one second before a 04:00 reset.
+
+hololive Dreams is read the same way and is the cleaner case of the two, because the source states
+its zone outright: every boundary on holodori.wiki carries `(JST)`, the game launched worldwide
+simultaneously on one service, and `Training Support Missions` ends at `3:59AM JST` — one minute
+before a 04:00 local reset. Only the offset is overridden; the hour is the default. It also cost
+nothing to add, which is the point worth carrying to the next game: an override that arrives with
+the game moves nobody, while the same override added a year later re-labels every tick already
+logged under the old clock. Get it right at introduction or accept a migration.
 
 Infinity Nikki, P5X and Blue Archive carry **no `resetOffsets` entry**, so they take the regional
 default. That is an assumption, not a verified server map — none of the three sources states one.

docs/INGESTION.md

@@ -51,8 +51,9 @@ Consequences worth internalising:
 | `game8` | game8.co article calendars | Genshin, Star Rail, Wuthering Waves, ZZZ, Endfield, NTE, Infinity Nikki, Persona 5: The Phantom X |
 | `wikigg` | wiki.gg MediaWiki `mp-event` templates | Endfield |
 | `akwiki` | arknights.wiki.gg's `mrfz-wtable` "Ongoing/upcoming" table | Arknights |
-| `fandom` | Fandom wikis via the MediaWiki `action=parse` API — `Event \| Time Period \| Version` wikitables | Reverse: 1999 |
+| `fandom` | Fandom wikis via the MediaWiki `action=parse` API — `Event \| Time Period \| Version` wikitables | Reverse: 1999, Fate/Grand Order |
 | `bawiki` | bluearchive.wiki's rendered `/wiki/Events` — a JP/Global tabber over `Name (EN) \| Start date \| End date \| Notes` wikitables | Blue Archive |
+| `holodoriwiki` | holodori.wiki's rendered `/wiki/Events` — `Current Events` and `Past Events` wikitables over `Event \| Type \| Start Date \| End Date` | hololive Dreams |
 
 `wikigg` is the better shape by a distance: it emits ISO timestamps with one timer per server
 region, so its events carry exact precision and real `regionEnds`. Prefer a source like that over a
@@ -118,6 +119,7 @@ All live in `src/ingest/dates.ts`, each returning null rather than inferring any
 | `parseYearFirstSlashRange` | `2026/07/30 – 2026/08/20` (year first, so field order is not inferred) | Arknights |
 | `parseOrdinalDateTimeRange` | `November 9th, 05:00 - December 4th, 2023, 04:59 (UTC-5)` (ordinal days, stated offset) | Reverse: 1999 |
 | `parseIsoDay` | `2026-08-04` (one boundary per column, so nothing to split) | Blue Archive |
+| `parseSlashClockZone` | `08/17/2026 8:00PM (JST)` (one boundary per column, 12-hour clock, **named** zone) | hololive Dreams |
 | `parseOpenRange` | `Jul. 24, 2026 - End of 4.6`, `July 10, 2026 - Permanent` | Star Rail, Wuthering Waves |
 
 `parseOpenRange` is tried last because it is the most permissive — it accepts any leading full date

docs/PRD.md

@@ -51,13 +51,14 @@ event, because a missing event sends them to a wiki while a wrong one makes them
 | Neverness to Everness | `nte` |
 
 Added since launch, on the strength of the release thread (`docs/FEEDBACK.md` § P1): Infinity Nikki
-(`nikki`), Persona 5: The Phantom X (`p5x`), Reverse: 1999 (`r1999`), Blue Archive (`ba`).
+(`nikki`), Persona 5: The Phantom X (`p5x`), Reverse: 1999 (`r1999`), Blue Archive (`ba`),
+Fate/Grand Order (`fgo`), hololive Dreams (`holodori`).
 **`GameId` in `src/shared/schema.ts` is the live answer** and `SOURCES` says which of them actually
 have a source — this table is the launch scope, not a roster to keep in sync.
 
 Adding a game must require no change to `GachaEvent` — only a `GameId` entry, its `games.ts`
 metadata, and a source registration. That is the test of whether the data model is right, and it has
-held: the eleven games here have cost the event schema nothing. Per-game *metadata* does occasionally
+held: the thirteen games here have cost the event schema nothing. Per-game *metadata* does occasionally
 grow (Reverse: 1999 needed `resetHourLocal` for a 05:00 reset), which is a different file and moves
 no stored key. A game may have several sources; see `docs/INGESTION.md` § Three layers.