Repository navigation
oracle corpus: the ABI-o1 cell stages the published 1.5 plugin (plugins_line, as the pinned generator emits it) - #536
Closed
MattJackson wants to merge 1 commit into
Closed
MattJackson wants to merge 1 commit into
MattJackson wants to merge 1 commit into
Conversation
…ery binary judged (plugins_line, as the pinned generator emits it)
`plugins.abi|json-contract|store-sqlite` is recorded against the PUBLISHED store-sqlite v1.0.6,
the 1.5.5 JSON-contract plugin. The pinned generator (busbar-release 4a7a7bba2c,
builders_capture.rs json_plugin_cells) emits `"plugins_line": "1.5"` on it, so that release is
staged whatever the judged binary's own line is. The committed cells.json lacked the field.
Without it, a 1.6 build asked fetch-plugin for a 1.6-line asset ("no pinned asset for
store-sqlite on x86_64-unknown-linux-gnu for busbar line 1.6"). The cell recorded nothing
(missing.candidate), and ABI-o1's premise, which probes this cell, could not be evaluated.
This is the one line the generator emits there, byte for byte. `cells --generate` now differs from
the committed corpus only by the three neutrality|routes|*-shaped-404 cells and their counts,
which #493 adds with D-1's scope count. No golden, accepted difference or engine pin changes.
MattJackson
enabled auto-merge
October 7, 2026 09:21
promote into
|
Collaborator
Author
|
Superseded by #594, per ARCHITECT ruling 2026-10-07 option (b). The ABI-o1 cell moves to a new id, plugins.abi|json-contract|store-sqlite@1.5-line: the old id is retired whole with a citation, and the new one is golden-added from the published 1.5.5. |
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.
Row 86 (oracle byte-identical to 1.5.5). This adds the one corpus line the pinned generator emits and predev's committed
cells.jsonlacked.Cause.
busbar-oracle cells --checkat predev's own engine (busbar-release 4a7a7bba2c) refused the corpus.builders_capture.rs json_plugin_cellsgivesplugins.abi|json-contract|store-sqlitethe field"plugins_line": "1.5", because the published 1.5.5 store-sqlite plugin is that cell's subject for every binary judged. Without the field, a 1.6 build asked fetch-plugin for a 1.6-line asset ("no pinned asset for store-sqlite on x86_64-unknown-linux-gnu for busbar line 1.6"). The cell recorded nothing (missing.candidate), and ABI-o1's premise, which probes this cell, could not be evaluated.Change. That one line, byte for byte as the generator writes it.
cells --generatenow differs from the committed file only by the threeneutrality|routes|*-shaped-404cells and their counts, which #493 adds together with D-1's scope count. The shepherd confirmed #493's file is the generator output minus this line, so the two merge cleanly. No golden, accepted difference, engine pin or code changes.Proof (Latchkey large, full-corpus record and strict replay against golden/1.5.5, engine 4a7a7bba2c):
plugins.abi|json-contract|store-sqlite, FAIL (missing.candidate) -> PASS;No Rust crate is touched, so there are no crate tests, clippy or fmt legs.