poc-reference-1: parity reference

Not a software release. This is the proof of concept's output, pinned so that diegoami/ck3-chronicle can prove its port changes no page (its docs/PLAN.md §5, milestone M3).

The build: 40fd399, uv run python -m ck3wiki.build saves --out site, with no flags, over the five release saves from ck_wiki. Those were fetched with scripts/fetch_saves.sh, so saves/releases.json is present.

The result: 3 chronicles, 25 124 pages, 25 133 files. The build was run twice, from a cold cache and a warm one, and the two outputs were identical, file for file.

Assets

• site-sha256.txt: one sha256 path line per generated file, in the format sha256sum -c reads.

• inputs-sha256.txt: the five saves and releases.json.

• reference.json: the commit, command and conditions, and the three owner-specific URLs and where they occur:

  • https://github.com/diegoami/Ck-parser in 25 129 files (every page footer and the manifests' docs block);
  • https://github.com/diegoami/ck_portrait_generator in the landing page;
  • https://github.com/diegoami/ck_wiki in the 4 portraits.json.

  Configure a port with these same values and its site should match byte for byte, with no normalisation needed.

To check a build:

cd site && sha256sum -c ../site-sha256.txt