bootstrap from 2026.9.20.1 - #679
Merged
Merged
Conversation
…entifier 2026.9.20.1 is released, mirrored on both ends and resolvable from the index, so the workspace bootstraps from it. VERIFIED BEFORE THE PIN MOVED, not after. The published CN artifact reports its own version and builds openkal-musl's real 24-row [c-abi-absent] manifest; `.agents/docs/2026-09-20-cenv-interfaces-verify.sh` reports `fails=0` against it both on this host and inside `xlings subos use v920 --sandbox`, with CN mirrors, addressing the store path rather than the shim --- `xlings use` rewrites only the root configuration, so a shim is not evidence of which binary a sandbox runs. The same script against the published 2026.9.18.3 reports `fails=2`, which is what makes each CHANGE section a measurement rather than a formality. The other change is a test. `AFreestandingTargetWithoutASelectionIsRefused` asserted that the refusal contains the target triple --- an identifier, which sits in the right place in a sentence that is wrong. Two refusals this wave added were found malformed exactly that way, by rendering them and reading them: one had lost a closing parenthesis, and one read as the claim it denies. This message has a single substitution and no paired delimiters, so it has no such failure mode; the assertion is widened anyway, because "no failure mode" is a property of today's wording rather than of the check.
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
2 participants
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.
The pin
2026.9.20.1 is released, mirrored on both ends and resolvable from the index, so the workspace bootstraps from it.
Verified before the pin moved, not after:
mcpp 2026.9.20.1; builds openkal-musl's real 24-row[c-abi-absent]manifestcmp-identical across GitCode and GitHubcenv-interfaces-verify.sh, this hostfails=0,not run: (none)xlings subos use v920 --sandbox, CN mirrorfails=0,not run: (none)fails=2— so each CHANGE section discriminatesThe sandbox run addresses the store path rather than the shim:
xlings userewrites only the root configuration, socommand -v mcppis not evidence of which binary a sandbox actually runs (it still resolved to 2026.9.17.1 there).The test
AFreestandingTargetWithoutASelectionIsRefusedasserted that the refusal contains the target triple — an identifier, which sits in the right place in a sentence that is wrong.Two refusals this wave added were found malformed in exactly that way, by rendering them and reading them: one had lost a closing parenthesis (
the C library in this graph (musl declares …), and one read as the claim it denies (openkal.space/provided by fakekernel). Both had tests matching an identifier inside the sentence.This message has one substitution and no paired delimiters, so it has no such failure mode. The assertion is widened anyway — "no failure mode" is a property of today's wording, not of the check.