Repository navigation
Close T-18 and record v0.2.9 - #61
Open
Samueru-sama wants to merge 4 commits into
Open
Samueru-sama wants to merge 4 commits into
Samueru-sama wants to merge 4 commits into
Conversation
v0.2.8 is published with 40 assets across five architectures. T-18 is closed in place, under its own title, with the acceptance command and its output: `gh release list`, a full `gh release download`, and `sha256sum -c` over all five checksum files, which verifies every asset against the number published beside it. The entry's premise said aarch64 had never been built anywhere. That has been false since v0.1.0: release.yml builds five architectures and runs the evidence table on ubuntu-24.04-arm. The correction is written beneath the premise rather than edited into it, because the title is how the entry is cited elsewhere. INDEX.md moves infrastructure to 6 open and 3 done, totals to 18/1/3, and high priority to 5. The counts were read out of the entries themselves. PROGRESS.md named v0.2.6 as the published release and carried a work order whose first item merged as PR #41 in v0.2.7. It now names v0.2.8, records that v0.2.8 is the first release carrying the ppc64le resolver frame repair, and orders the three things actually left: the unchecked class in glfwd_try_vendor, wiring gl-fwd-qemu-check into a runner, and the remaining stale totals in docs/ground-truth.md. Two things a next session should not re-derive are recorded as distrust notes: the scheduled appimage-suite is red because upstream's demo AppDir no longer carries a dispatcher slot, and the release gate does not run the wide suite at all.
Both are in PROGRESS.md, and both were caught by asking what had been asserted without being run. 900a393 is a squashed commit with one parent, not the PR #60 merge commit. The property that matters is unchanged and is now stated as the property: the tree CI tested (62985da) is the tree the tag carries, so the commits differ and the trees do not. The gtk3-demo ppc64le reproduction came from issue #59 and the PR body, not from this session. What was measured here is that `make gl-fwd-qemu-check` fails on the pre-fix gl-fwd.c and passes on the shipped one, and that the published ppc64le-gl-fwd.so carries the 288-byte frame. Nothing here ran a GTK3 application, so the entry now says so instead of repeating the report as though it were a result.
v0.2.9 is published with 40 assets across five architectures. PROGRESS named v0.2.8 and carried a work order that the NixOS change did not touch. The new release adds /run/opengl-driver/lib and /run/current-system/sw/lib to three lists, and the container suite reports 69/69 on x86-64, which is the 66 this file recorded plus E104, E105 and E106. The entry says so rather than leaving the previous total standing. Two review passes, asking different questions. Pass 1, does every claim hold when the command is run: swept the suite output and the tag/binary claims. Found that this file first said the three cases "were not measured here" while also reporting the 69/69 that includes them. They do run, in the container, as root; what is missing is a NixOS host. Rewritten to say that. Pass 2, what did I assert that I did not measure: swept every factual sentence added. Found a pointer claiming report section 10 carries the NixOS measured-versus-assumed distinction. It does not mention NixOS at all, so the text now says that writing it is open work instead of citing it. The one sentence that survives is the A/B actually run here: the fake-libva contract prints NO-DRIVER on the v0.2.8 source and DRIVER=NIX on the shipped one.
Samueru-sama
force-pushed
the
docs/close-v0.2.8
branch
from
October 23, 2026 21:14
261da56 to
9098a7a
Compare
Samueru-sama
changed the title
The hygiene gate refused this branch: 69/69 and 65/65 each appeared in two files, docs/report/ and docs/todo/PROGRESS.md. Every headline number has one home and it is the report; a second copy is the defect the gate exists to catch, and it caught this one on a runner. The two sentences now say what changed without repeating the number: the container runs the three cases so the total rises, and section 8 carries the current pair.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two release close-outs in one branch, rebased onto the NixOS change so it applies to
mainas it stands.T-18, closed in place
The entry keeps its title and its premise; the correction is written beneath them, because the title is how the entry is cited elsewhere. The premise said aarch64 had never been built anywhere. That has been false since v0.1.0:
release.ymlbuilds five architectures and runs the evidence table onubuntu-24.04-arm.Closed with its acceptance command and output:
INDEX moves infrastructure to 6 open and 3 done, totals to 18/1/3, high priority to 5. The counts were read out of the entries.
v0.2.9
PROGRESS now names v0.2.9 and the NixOS directories it adds. The evidence table reads 69/69 on x86-64, which is the previous 66 plus E104, E105 and E106.
⚠ What the NixOS work does not prove, recorded rather than implied: the three cases create
/run/opengl-driver/lib, so the container suite runs them as root and they SKIP by name where/runis not writable. Nothing in the tree has run the shims on a NixOS host, and report section 10 does not yet carry that distinction.What was measured for the release itself:
sh scripts/run-evidence.sh: 69/69 predictions held, exit 0, including E104/E105/E106.sh scripts/build.sh --arch x86_64on the floor: every artefact verified, maxGLIBC_2.16against 2.31.NO-DRIVERon thev0.2.8source andDRIVER=NIXon the shipped source./run/opengl-driver/libingl-fwd.soandcross-libc-dlopen.so, and both NixOS paths inruntime-select..sha256files.Review passes
Two, asking different questions, both recorded because each found something.
sh scripts/check-drift.shandsh scripts/check-charset.shboth exit 0.