docs: fgo has a snapshot now

A hand-run refresh landed one at 02:36 on 2026-08-19, four events. The sentence
two commits ago said it had never had one, which was true when written and is
the kind of claim that decides whether someone bothers trying — so it is worth
being exact about: r1999 and fgo have snapshots, both taken by hand today;
nikke and nikki are still served from their fixtures.

The conclusion is unchanged. None of the four will ever be refreshed on a
schedule, because CI cannot read Fandom's robots.txt.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
Lucas Winther
2026-08-19 04:50:09 +02:00
co-authored by Claude Opus 5
parent f67118913a
commit aa393828d8
+4 -4
View File
@@ -367,10 +367,10 @@ Two consequences, and neither is a licence to work around it:
- **All four** built Fandom sources report `skipped_robots` on **every** run, from any address we
have, so `r1999`, `fgo`, `nikke` and `nikki` are permanently fixture-backed until someone
refreshes them from an address Fandom serves. Only `r1999` has ever had a snapshot at all — last
refreshed on 2026-08-19, hours before the tightening was found — and `fgo`, `nikke` and `nikki`
have never had one. That is not a source being down: nothing is broken, and nothing will ever
update these four on a schedule.
refreshes them from an address Fandom serves. `r1999` and `fgo` have snapshots, both taken by hand
on 2026-08-19; `nikke` and `nikki` have never had one and are served from their fixtures. That is
not a source being down: nothing is broken, and nothing will ever update any of the four on a
schedule.
- A **new** Fandom source can still be added, but only once someone reads that wiki's `robots.txt`
from an address Fandom serves and records it here. That is exactly how Nikke was cleared on
2026-08-19: the file was read in a browser, is the standard Fandom file — no `Disallow: /` for