From dbcd14eb70423ce7d2eb1e910dbea9ea0280afd1 Mon Sep 17 00:00:00 2001 From: Lucas Winther Date: Sun, 23 Aug 2026 01:07:30 +0200 Subject: [PATCH] docs: record the TBA drop and what a one-row source means MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two things the last two commits taught, written down where the next person looking at a parser will hit them. The date table now carries the slash-dated open range, and the prose beside it says the year is required and why — that reader is tried last, so a guess there reaches the feed unchallenged. It also names the second copy of the open-end vocabulary, because the two lists being out of step is not a hypothetical failure any more. The second is the one worth having on record. `eventCount` in a snapshot's meta is not a count of the page. Endfield's Game8 lane read 1 for a week — one row of an *upcoming* table, while four live events sat in a card grid the parser cannot read — so the first time the page moved, the lane read 0 and the gate reported a shape change. Neither number described the page. A count far below what the page shows is a shape being skipped, and it is worth finding before it reaches zero and the gate has to guess on your behalf. Co-Authored-By: Claude Opus 5 (1M context) --- AGENTS.md | 14 +++++++++++--- docs/INGESTION.md | 15 +++++++++++++-- 2 files changed, 24 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 54d51c9..e38cfd4 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -240,9 +240,17 @@ These come from how gacha games actually schedule things, and they cause most bu - **Prefer a source that states machine-readable times.** wiki.gg emits ISO timestamps with a timer per server region, which is the only reason `regionEnds` carries real data anywhere. - **Silent drops are the dangerous failure.** A date format the parser does not recognise makes - events vanish with no error. Abbreviated months (`Apr. 29 - May 13, 2026`) are supported for - exactly this reason. When adding a source, compare the parser's event count against an - independent count of the page. + events vanish with no error. Abbreviated months (`Apr. 29 - May 13, 2026`) and slash-dated open + ends (`09/02/2026 - TBA`) are supported for exactly this reason. When adding a source, compare the + parser's event count against an independent count of the page. +- **A source resting on one row is a source about to read zero.** `eventCount` in a snapshot's + `.meta.json` is the count the whole lane depends on, and a small one is a warning rather than a + fact about the game. Endfield's Game8 page read `1` for a week — one row of an *upcoming* table, + while four live events sat in a card grid the parser cannot see — and when Game8 re-cut that table + for the next version in a notation `parseOpenRange` did not know, the source read `0` and the + refresh reported a shape change. Neither number was ever a count of the page. When a source's + count is far below what the page shows, find out which shape is being skipped before the count + reaches zero and the gate has to guess for you. ## Event IDs are localStorage keys diff --git a/docs/INGESTION.md b/docs/INGESTION.md index 5d4a569..c0e5a46 100644 --- a/docs/INGESTION.md +++ b/docs/INGESTION.md @@ -146,7 +146,7 @@ All live in `src/ingest/dates.ts`, each returning null rather than inferring any | `parseIsoOffsetInstant` | `2026-08-03T21:00-07:00` (a machine-readable `