Release 0.8.0, the quiet minor: instruments (G-076, G-078, G-079) and pages; no public entry moves - #59
Merged
Conversation
…try moves. G-076: a sixteenth gate step, baseline, diffs docs/public-api.txt against origin/main through tools/baseline_diff.sh (pure: base file, head file, base CHANGELOG in; a verdict out) -- a public entry's line deleted by hand is a FAIL (the writer never deletes a line), and a marker arriving with a release number the base CHANGELOG already lists is a FAIL (a change dressed as one that shipped), compared per entry so a new line back-dated to an old number is still an arrival; the release step's own not-yet-listed number and the writer's Unreleased pass. tools/probe_baseline_diff.sh plants on copies: P0 unchanged 0; P1 a line deleted 1; P2 the same entry marked removed_in=Unreleased 0; P3 removed_in= and P4 deprecated_since= with the last release's number 1, 1; P5 a marker with a number not yet released 0; P6 a new entry marked Unreleased 0; P7 a new entry back-dated 1 -- PROBE OK. Where origin/main does not resolve the step says so and is not evidence. G-079: the edited summary's read moves into tools/ci_legs_verdict.sh, which polls the head SHA's leg check runs until every one is completed (bounded, 40 polls at 30 s) and only then judges; gate.yml's summary checks out the tree (the same pinned action) and calls it, with timeout-minutes 25 above the bound. tools/probe_ci_legs_verdict.sh runs it offline with a scripted gh: S1 in_progress twice then three successes 0; S2 a leg completing as failure 1; S3 a leg never completing, the bound 1; S4 two legs beside the skipped unexpanded name 1; S5 three successes on the first read 0 -- PROBE OK. G-078: the honesty probe's discriminator reads pass( \(|$); on a green gate.out the old regex counted 10 of 16 step lines as not pass, the new 0 (logs). Pages: the governance table carries the Scorecard's measured figure per row (api.scorecard.dev, 2026-09-19T21:18:40Z, aggregate 7) with the rule behind each low figure, and two rows the result added; provenance's two example commands say 0.7.0; connectome-canonical's schema history drops 'which carries this note'; the gate is sixteen steps in governance and the README. The unused ret in the no-signature census is _ret. Gate on this tree: Gate OK, the new step reading 131 entries, none deleted, 0 markers arriving Signed-off-by: Ayla Croft <aylacroft@proton.me>
… surface. release_markers!("0.8.0") on docs/public-api.txt wrote 0 -- the file is 0.7.0's line for line, and the gate's new baseline step reads 131 entries, none deleted, 0 markers arriving against origin/main; the census holds an empty Unreleased section. The [0.8.0] heading dated, with a paragraph stating the no-move and that this is the full minor unchanged the README names as 1.0.0's condition; the README requirement ~> 0.8.0 with its paragraph (0.7.0 an addition, 0.8.0 a quiet minor, neither a break; ~> 0.8 would admit a 0.9.0); the requirement test refusing 0.7.0 and 0.6.0 with true reasons and 0.5.0 across the bytes break; SECURITY's supported row (0.8.x yes, 0.7.x superseded); api-stability's example command and current-minor sentence; UPGRADING's pin, a paragraph saying 0.8.0 has no row either and what did change, and the road list with 0.8.0 as this release and 1.0.0 next; HANDOFF for the release (State, the road, sixteen steps, git log v0.7.0..main as the authority, 705 tests measured on this tree -- 0.8.0 adds no test, its instruments are probed by shell); the wire recording re-taken at 0.8.0 (its ten version lines and nothing else). Gate on this tree: Gate OK; 11 properties, 705 tests, 0 failures. The owner publishes and tags, in the 0.6.0 order; this commit does neither
Signed-off-by: Ayla Croft <aylacroft@proton.me>
… no longer says 'nothing else to do' -- a host on beam_mcp_signer 0.1.0, whose requirement is ~> 0.7.0 by the same three-number rule, cannot take 0.8.0 until a signer release admits it, and the page says so (HANDOFF beside it); HANDOFF's runbook heading names 0.8.0 and its step list names all sixteen (dialyzer and audit were missing from the enumeration since 0.7.0). Instruments: tools/baseline_diff.sh refuses a marker arriving with any number not above the base CHANGELOG's highest heading -- one it lists, or a phantom between two releases (the lane's removed_in=0.6.5 passed the first draft); probe P8 added, PROBE OK on P0-P8. tools/ci_legs_verdict.sh treats a failed checks-API read as a poll spent, not a verdict (a transient error during the wait no longer fails the required check), and counts an empty read as 0 pending, not 1; probe S6 (fails once, then green: 0), S7 (fails every time: the bound, 1), S8 (no check runs: 1) added, PROBE OK on S1-S8. The CHANGELOG's three entries say what the instruments do now, and give both discriminator figures (7 of the probe's 13 names; 10 of the gate's 16). No version string moved; the baseline did not move; Gate OK Signed-off-by: Ayla Croft <aylacroft@proton.me>
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
1 participant
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.
0.8.0, the quiet minor. Two commits: instruments and pages (
bea6a80), then the release strings (d769d60). Tier: measurement + records — one lane, one round (declared in the slice PLAN before any edit).No public entry moves.
docs/public-api.txtis 0.7.0's line for line;release_markers!("0.8.0")wrote 0; the census holds an empty Unreleased section; no wire or envelope byte moves; no{:beam_mcp_signer, ...}inmix.exs.Instruments (each with an offline probe)
baseline:tools/baseline_diff.shdiffsdocs/public-api.txtagainstorigin/main; a public entry's line deleted by hand, or a marker arriving with a release number the CHANGELOG already lists, is a FAIL.tools/probe_baseline_diff.sh: P0–P7 as expected, PROBE OK.tools/ci_legs_verdict.sh: the edited summary polls the head SHA's leg check runs until each is completed (bounded 20 min; job ceiling 25), then judges.tools/probe_ci_legs_verdict.shwith a scriptedgh: S1–S5 as expected, PROBE OK.gate.yml's summary checks out (same pinned action) and calls it.pass (<detail>)as pass: 10 of 16 step lines miscounted on a green gate before, 0 after.Pages:
docs/governance.md's Scorecard table carries the check's measured figure per row (api.scorecard.dev, 2026-09-19, aggregate 7) with the rule behind each low one, and two rows the result added;docs/provenance.mdexamples name 0.7.0;connectome-canonical.md's schema history;_retin the no-signature census; "sixteen steps" in governance and the README.Release strings:
mix.exs0.8.0; README~> 0.8.0; requirement test refuses 0.7.0/0.6.0/0.5.0; CHANGELOG[0.8.0] — 2026-09-19; UPGRADING ("0.8.0 has no row either"; the road with 1.0.0 next); SECURITY 0.8.x; api-stability; HANDOFF; wire recording's ten lines.Gate on this tree: Gate OK;
11 properties, 705 tests, 0 failures. Not done here: publish, tag (the owner's, in the 0.6.0 order); the signer's CHANGELOG heading (a separate commit on that repo).