fix(sources): Mira Journey ends at Asia's reset after the version's last day

The Version table prints the version's last day as its End Date. Read as
an ordinary day-precision end, the event left the calendar 9 to 24 hours
before the pass did. The owner's timer on Europe put the end at about
20:00 UTC on 29 Oct: Asia's 04:00 reset opening the 30th, for every
server. The source's entry now says so, with that evidence, and the
event ends at exactly 2026-10-29T20:00Z. Found in the whole-branch
review.

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

docs/SOURCES.md

@@ -883,7 +883,7 @@ passed. A `fetched` with more than zero events means the wiki is back.
 
 **Source:** `https://infinity-nikki.fandom.com/api.php?action=parse&page=Version&prop=text&formatversion=2&format=json` (page `https://infinity-nikki.fandom.com/wiki/Version`), source id `nikki-fandom-mira-journey`, parser `fandomversion` (`src/ingest/parsers/versionTable.ts`).
 
-**What it is:** Mira Journey has no dated page. The `Version` page dates *versions*: three tables headed `Version Name | Version Number | Release Date | End Date | Duration` (2.x, 1.x, prerelease), 25 rows in all (counted independently of the parser), e.g. `The Feather of Justice | 2.10 | September 23, 2026 | October 29, 2026 | 36 Days`. A version stands in for the pass only because the owner confirmed in game, 2026-10-16, that the pass ends with it (it read 13d 19h at 00:47 UTC, ending 2026-10-29 with version 2.10). That claim and its evidence are one entry in `VERSION_PASSES`, keyed by source id; the event's summary repeats it (`Follows version 2.10 (The Feather of Justice). That the pass ends with the version was confirmed in game, 2026-10-16.`). Rows already ended are skipped, a row without a readable end is skipped; at capture exactly one row survives: 2026-09-23 to 2026-10-29, day precision, titled `Mira Journey`. The page states no zone, so nothing is region-scoped.
+**What it is:** Mira Journey has no dated page. The `Version` page dates *versions*: three tables headed `Version Name | Version Number | Release Date | End Date | Duration` (2.x, 1.x, prerelease), 25 rows in all (counted independently of the parser), e.g. `The Feather of Justice | 2.10 | September 23, 2026 | October 29, 2026 | 36 Days`. A version stands in for the pass only because the owner confirmed in game, 2026-10-16, that the pass ends with it (it read 13d 19h at 00:47 UTC, ending 2026-10-29 with version 2.10). That claim and its evidence are one entry in `VERSION_PASSES`, keyed by source id; the event's summary repeats it (`Follows version 2.10 (The Feather of Justice). That the pass ends with the version was confirmed in game, 2026-10-16.`). Rows already ended are skipped, a row without a readable end is skipped; at capture exactly one row survives, titled `Mira Journey`, from 2026-09-23 (day precision). **Its End Date is the version's last day**, not the day it ends: the owner's timer on Europe put the end between 19:47 and 20:47 UTC on 2026-10-29, which is Asia's 04:00 reset opening the 30th. So the entry carries `endsAfterLastDay: { clock: "asia" }` and the event ends at exactly 2026-10-29T20:00Z for every server. Read as an ordinary day-precision end it would have left the calendar 9 to 24 hours early, before the pass did. Nothing is region-scoped.
 
 **Not the history-table reader:** `fandomtable` refuses any table with a `Duration` heading and this reader requires one, so neither claims the other's page (tested across every fixture).