v0.3.1
A patch release for two things a stranger would have hit.
A shallow clone stopped accusing the paper
git clone --depth 1 followed by make ci produced five failures naming worked-example, Lean-file-count and receipt-flow "drift". None of them mentioned the clone.
The public-system paper pins its evidence to a specific commit, and the checks read the repository as it stood there. A truncated clone does not contain that commit, so those comparisons ran against absent data — not against anything that had actually changed. The honest reading of the output was "the paper's numbers are wrong", which was false.
The history dependency is kept deliberately. The paper makes claims about a particular past commit; re-deriving them from a receipt that same commit produced would only check that file against itself. What changed is that absence is now reported as absence — the checker names the shallow clone and the fetch that resolves it, and the checks needing the pinned commit skip with that reason instead of failing as drift.
| clone | before | after |
|---|---|---|
--depth 1 |
5 failed | 5 skipped, 0 failed |
| full | passing | unchanged, 0 skipped |
One publication owner for the site
.github/workflows/pages.yml is deleted. GitHub Pages serves this site from the gh-pages branch builder; that workflow checked out the same branch and deployed the same tree again as an artifact to the same environment, so which one won depended on which ran last.
It had already taken the published site down once — an earlier version copied a hardcoded list of files, and all three papers plus .well-known/security.txt returned 404 until it was switched off. It was disabled rather than deleted, which left the second owner one toggle away. A test now asserts no workflow deploys Pages while the branch builder owns publication.
Verification
make cigreen on a fresh full clone ofmain; CI green on Python 3.11 / 3.12 / 3.13, plus CodeQL and the smoke job--depth 1clone: 5 skips, 0 failures- live site checked after the change:
/,/.well-known/security.txtand all three papers return 200, Pages stillbuild_type: legacyfromgh-pages
On v0.3.0
v0.3.0 is unchanged and stays exactly as published. Immutable releases were enabled on this repository after it was cut, and enabling them is not retroactive — the API still reports immutable: false for it. So an immutable release could only be a new one, and this is it. No previously published artifact was moved, rewritten, or deleted.