Lucas WintherandClaude Opus 5
cada4d7771
Retiring nikki-game8-events left its snapshot behind. snapshots/ is defined as the current page per source, and there is no such source — so these two files are 200 KB of a wiki that stopped being updated in August 2025, tracked in git, described by metadata naming a sourceId nothing resolves. Harmless today: build-feed.ts iterates ADAPTERS, so an orphan is never read. That is also what makes it worth removing rather than leaving. The one path that would read it again is someone re-registering the id, and what they would silently get back is the stale page the lane was moved off — the failure the move was made to fix, arriving through a file nobody looked at. The fixture stays. fixtures/nikki/game8-events-2026-08-17 is pinned and permanent, it is the only page here carrying Game8's labelled "Start: ... End: Permanent" shape, and test/adapters still drives it through the parser. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Snapshots
Raw pages, exactly as fetched. scripts/refresh-sources.ts writes them; nothing else fetches.
<source-id>.html the body verbatim — tracked
<source-id>.meta.json hash, size, charset, ETag, Last-Modified, when the bytes last changed — tracked
<source-id>.state.json when we last checked, and failure streak — gitignored
"Verbatim" means the bytes as served, not text we re-encoded. charset in the metadata records
what those bytes are in — the Content-Type header, else a <meta charset> in the page, else
UTF-8 — and bytes is the served length. A page in Shift_JIS or Latin-1 decoded as UTF-8 would be
stored as a field of U+FFFD with the original bytes gone; re-parsing could never recover it, and the
mojibake would reach slugify, moving every event ID for that source (AGENTS.md § Event IDs are
localStorage keys).
Every file is written to a sibling .tmp-* and renamed into place, body before metadata, so an
interrupted run leaves a stray temp file rather than a truncated snapshot or metadata describing
bytes that were never stored. Those temp files are gitignored: refresh.yml commits the whole
directory, so otherwise a run killed mid-write would pin a half-page in git forever.
Three reasons this is committed rather than cached:
- Re-parsing never re-fetches. Iterating on a parser reads these files, not the wikis (AGENTS.md § Scraping conduct).
- A refresh is reviewable. The commit diff is the page diff, so "an event vanished" is a question you can answer from git rather than from a wiki that has since changed again.
- The build stays offline.
bun run build:feedparses whichever of these exists and falls back tofixtures/otherwise, so a clean checkout and the container build work with no network.
The .state.json files are the exception: they change every cycle whether or not a page did, and
committing them would mean a commit per run saying nothing happened. CI keeps them in the actions
cache instead: refresh.yml saves that cache, and ci.yml restores it read-only before building
the feed. Both halves matter — lastConfirmedAt lives only there, and without the restore the feed
falls back to contentChangedAt and the UI calls every source stale two days after its bytes last
moved.
The metadata is rewritten on an unchanged page in one case: the server rotating an ETag or
Last-Modified while serving the same bytes. Keeping the old validator would mean sending a stale
If-None-Match forever and being served the whole page every cycle, so that diff is worth the
commit — contentChangedAt and the body stay put, so it is still visibly not a content change.
Fixtures are not the same thing. A fixture is pinned to a date and kept forever as the regression test for a page shape; a snapshot is the current page and is overwritten each time it changes.