Repository navigation
chore: pin the toolchain to topaz-1's own ref and regenerate vendored/ - #71
Merged
Merged
Conversation
GNOVERSION was 2c7f1abe, six weeks older than the chain this is about to be published to immutably. Now fc4052651, which is what topaz-1 runs. The skew was not theoretical. Roughly 15 vendored packages differed from what the chain hosts, including p/nt/avl/v0: its Get is single-value on-chain and was two-value in the vendored copy. A green build did not prove publishability, and the gap was held open by a hand argument about which symbols gnodaokit happened to touch. Regenerating at the chain's ref closes it — the vendored stdlib avl is now single-value, matching what AddPackage will resolve. The old toolchain also had no sub-realm support at all: cur.Sub() failed preprocessing, and realmSubpathOf / topmostCrossingFrameCurHIV are absent from the binary. Nothing could exercise the sub-realm semantics the identity work reasons about, on the compiler the freeze was being validated with. 15 files changed content, one was added, and p/moul/md/filetests is gone upstream — its filetest became example_test.gno in the package. The fork at p/samcrew/avl is untouched and still exposes the two-value Get. Verified at the new pin with the network unavailable: 8 packages ok, lint clean, gno fmt zero diff, zero "gno: downloading" lines, and the provenance comparison run locally in both directions — 118 files checked, 0 drift, 0 deleted, 0 symlinks. The stdlib-avl boundary gate stays, but it is belt-and-braces now rather than load-bearing: a misuse fails the local build instead of surviving to AddPackage. Its comment and vendored/README.md said the opposite and are corrected.
zxxma
changed the base branch from
freeze/exported-surface
to
feat/topaz-v2-rename
July 20, 2026 18:50
This was referenced Jul 20, 2026
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.
Stacked on #70. Merge order: #69 → #70 → this.
The skew was real
GNOVERSIONwas2c7f1abe(2026-06-01), six weeks older than the chain this is about to be published to immutably. topaz-1 runsfc4052651(2026-07-17).Roughly 15 vendored packages differed from what the chain hosts — including
p/nt/avl/v0, whoseGetis single-value on-chain and was two-value in the vendored copy. A green build genuinely did not prove publishability. The gap was held open only by a hand argument about which symbols gnodaokit happens to touch, re-argued on every change.After regeneration the vendored
p/nt/avl/v0is single-value, matching the chain. Thep/samcrew/avlfork is untouched and still exposes the two-valueGetthe data-structure role needs.The other cost, which the identity review surfaced
The old toolchain has no sub-realm support at all.
cur.Sub()fails preprocessing withmissing field Sub in .uverse.realm, and the symbols are absent from the binary:So nothing could exercise the sub-realm semantics #69's design reasons about, on the very compiler the freeze was being validated with.
What changed
15 vendored files changed content, one was added (
p/moul/md/example_test.gno), andp/moul/md/filetestsis gone upstream — its filetest became thatexample_test.gno. Every other vendored package exists at the new ref with an unchanged layout.Verification
Run with the network unavailable, at the new pin: 10 packages ok · lint clean ·
gno fmtzero diff · zerogno: downloading.The provenance comparison was run locally in both directions before pushing — 118 files checked, 0 drift, 0 deleted, 0 symlinks.
Deployer
assert_gnodaokit_source_form topaz-1passes against this tree.Docs that asserted the old skew
vendored/README.mdhad a section headed "A green build here does not by itself prove publishable on topaz-1" and the provenance workflow's stdlib-avl gate carried the same rationale. Both corrected: the gate stays, but it is belt-and-braces now rather than load-bearing — with the vendored copy matching the chain, anntavl.Get()two-value call fails the local build instead of surviving toAddPackage.Supersedes
#63 proposes
5111dbc2, and #64's Makefile bump proposesba9da8eb— both older than the chain. This takes the chain's own ref instead.