docs: correct the source count and the pass readers' entries

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

AGENTS.md

@@ -43,7 +43,7 @@ A web app that aggregates live and upcoming events across popular gacha games, p
 calendar, sorts them by end date or by what the reader is partway through, tracks day-by-day
 progress on events that repeat daily, and lets a user mark events completed.
 
-**Status: working app, refreshing itself on a schedule.** Schema, twelve parsers, twenty-six sources across
+**Status: working app, refreshing itself on a schedule.** Schema, twelve parsers, twenty-five sources across
 twenty games, the full interface, offline support, a static server, a Docker image and CI all exist and
 are tested. The refresh runner (`bun run refresh`) fetches, caches raw snapshots and rebuilds the
 feed; `.gitea/workflows/refresh.yml` runs it twice a day and commits only when a page actually

docs/INGESTION.md

@@ -52,8 +52,8 @@ Consequences worth internalising:
 | `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 — five page templates: `Event \| Time Period \| Version` wikitables, FGO's picture-fenced `ONGOING EVENTS` blocks, Nikke's `Event \| Start(UTC+9) \| End(UTC+9)` tables, Infinity Nikki's `Event \| Duration \| Description \| Type` article-tables, and Genshin Impact's `Event \| Duration \| Type(s)` tables | Reverse: 1999, Fate/Grand Order, Nikke, Infinity Nikki, Genshin Impact |
-| `fandomtable` | Fandom's dated **history table** via the same `action=parse` API — one `article-table` headed `Name \| Start \| End` (plus Image/Version), a row per run of a battle pass, found by heading rather than column position and skipped when its heading row names `Duration` (that is a version table). Titles come from a per-source `PASS_SOURCES` entry; only rows not yet ended by `ctx.now` are emitted, at day precision | Star Rail (Nameless Honor) |
-| `fandomversion` | Fandom's **version table** via the `action=parse` API — tables headed `Version Name \| Version Number \| Release Date \| End Date \| Duration` (the `Duration` heading is what `fandomtable` refuses, so the readers are disjoint). A pass is emitted for each version row not yet ended by `ctx.now`, only where the source's `VERSION_PASSES` entry states the pass follows the version, with who said so and when; day precision | Infinity Nikki (Mira Journey) |
+| `fandomtable` | Fandom's dated **history table** via the same `action=parse` API — one `article-table` headed `Name \| Start \| End` (plus Image/Version), a row per run of a battle pass, found by heading rather than column position and skipped when its heading row names `Duration` (that is a version table). Titles come from a per-source `PASS_SOURCES` entry; only rows not yet ended by `ctx.now` are emitted, at day precision; a table whose dated runs have all ended states no events | Star Rail (Nameless Honor), ZZZ (New Eridu City Fund) |
+| `fandomversion` | Fandom's **version table** via the `action=parse` API — tables headed `Version Name \| Version Number \| Release Date \| End Date \| Duration` (the `Duration` heading is what `fandomtable` refuses, so no one table matches both). A pass is emitted for each version row not yet ended by `ctx.now`, only where the source's `VERSION_PASSES` entry states the pass follows the version, with who said so and when; day precision, unless the entry states the End Date is the last day and on whose reset the pass ends (Nikki: Asia's) | Infinity Nikki (Mira Journey) |
 | `bawiki` | bluearchive.wiki's rendered `/wiki/Events` — redesigned `#eventtable` unified schedule (and legacy JP/Global tabber) | Blue Archive |
 | `holodoriwiki` | holodori.wiki's rendered `/wiki/Events` — `Current Events` and `Past Events` wikitables over `Event \| Type \| Start Date \| End Date` | hololive Dreams |
 | `iopwiki` | iopwiki.com's `gf-table event-period` tables — `Title \| Period (start/end) \| Server \| Type \| Comment`, one table per event and one row per server | Girls' Frontline 2 |

docs/SOURCES.md

@@ -869,7 +869,7 @@ passed. A `fetched` with more than zero events means the wiki is back.
 
 **Precision:** day, start and end. Nothing is inferred: no clock, no region, no end for a row without one (skipped). At capture one row is live, 2026-09-28 to 2026-11-09 (4.6); each row ends on the day the next one starts. The Name cell reads `Nameless Honor <start date>`, so the title is constant and the start is the only thing that tells runs apart in the ID.
 
-**Reuse:** the parser is `fandomtable` (`src/ingest/parsers/fandomTable.ts`). The next pass pages (ZZZ `New_Eridu_City_Fund`, Genshin `Miliastra_Pass`) are one `PASS_SOURCES` entry each (title as a function of the row's Name cell) plus a `SOURCES` entry; columns are found by heading. A table headed with `Duration` is deliberately not this template (it is a version table).
+**Reuse:** the parser is `fandomtable` (`src/ingest/parsers/fandomTable.ts`). Another pass page is one `PASS_SOURCES` entry (a title, constant or built from the row's Name cell) plus a `SOURCES` entry, as ZZZ's `New_Eridu_City_Fund` is (§ 18); Genshin's `Miliastra_Pass` was tried and reverted, being in the feed already; columns are found by heading. A table headed with `Duration` is deliberately not this template (it is a version table).
 
 ## 18. ZZZ — New Eridu City Fund window (Fandom) — BUILT 2026-10-16