The workflows run in lithosananke-runner:4f675c8b75b2, the image runner-image.yml built from master 4f675c8b (run 193) after #127: what init installs, Maven, and the HOL-Library heap, fetched prebuilt (checksum OK, 4.8 s), so the proofs step builds only the StarForth session (~2.2 GiB, under a minute) instead of HOL-Library (~5.3 GiB, which the server cannot hold). Without this, the v4.0.0-alpha.1 release run's proofs step would be killed as nightly 174's was.
Part of #120, #17. The step before tagging v4.0.0-alpha.1.
Acceptance
The Acceptance check on this pull request runs in the new image: it is the test.
Logs from runs made by hand are committed in logs/, if any -- none
Hardware this was tried on, if any: none (CI only)
The record
docs/fabric/FABRIC-3.md has the ruling and what was built, if this is design work -- XLVII.4 already describes it
CHANGELOG.md, if it is a milestone -- part of the v4.0.0-alpha.1 entry
Nothing in this PR is a fix nobody asked for (.claude/CLAUDE.md, Hard Rules)
## What and why
The workflows run in **`lithosananke-runner:4f675c8b75b2`**, the image `runner-image.yml` built from master `4f675c8b` (run 193) after #127: what `init` installs, Maven, and the **HOL-Library heap, fetched prebuilt** (checksum OK, 4.8 s), so the proofs step builds only the StarForth session (~2.2 GiB, under a minute) instead of HOL-Library (~5.3 GiB, which the server cannot hold). Without this, the `v4.0.0-alpha.1` release run's proofs step would be killed as nightly 174's was.
Part of #120, #17. The step before tagging `v4.0.0-alpha.1`.
## Acceptance
The **Acceptance** check on this pull request runs in the new image: it is the test.
- [ ] Logs from runs made by hand are committed in `logs/`, if any -- none
- [ ] Hardware this was tried on, if any: none (CI only)
## The record
- [ ] `docs/fabric/FABRIC-3.md` has the ruling and what was built, if this is design work -- XLVII.4 already describes it
- [ ] `CHANGELOG.md`, if it is a milestone -- part of the v4.0.0-alpha.1 entry
- [x] Nothing in this PR is a fix nobody asked for (`.claude/CLAUDE.md`, Hard Rules)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
The image runner-image.yml built from master 4f675c8b (run 193): what init
installs, Maven, and the HOL-Library heap fetched prebuilt (checksum OK, 4.8
s), so the proofs build only the StarForth session. Its acceptance run is
this PR's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2
rajames
merged commit 233025da88 into master2026-11-07 18:17:53 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What and why
The workflows run in
lithosananke-runner:4f675c8b75b2, the imagerunner-image.ymlbuilt from master4f675c8b(run 193) after #127: whatinitinstalls, Maven, and the HOL-Library heap, fetched prebuilt (checksum OK, 4.8 s), so the proofs step builds only the StarForth session (~2.2 GiB, under a minute) instead of HOL-Library (~5.3 GiB, which the server cannot hold). Without this, thev4.0.0-alpha.1release run's proofs step would be killed as nightly 174's was.Part of #120, #17. The step before tagging
v4.0.0-alpha.1.Acceptance
The Acceptance check on this pull request runs in the new image: it is the test.
logs/, if any -- noneThe record
docs/fabric/FABRIC-3.mdhas the ruling and what was built, if this is design work -- XLVII.4 already describes itCHANGELOG.md, if it is a milestone -- part of the v4.0.0-alpha.1 entry.claude/CLAUDE.md, Hard Rules)🤖 Generated with Claude Code
https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2