verify(v1.139): promote the four merged fixes — battery, Format gate, fleet monitor, readiness report - #439
Merged
Merged
Conversation
…e ran in the merge gate (#413) Code-free promotion under the two-commit rule. The implementation landed in #430 (a1b0e17) at `implemented`. Evidence, observed rather than asserted: - #430's REQUIRED Verification gate (run 35137919049, the run that gated the merge) matched FV-FALCON-BATT-003 and executed all four of its steps: PASS — `cargo test -p falcon-core --release absent_battery_blocks_arming` (4.27 s) and the three source greps (Option<f32> defaults to None for read_battery_v and BatteryDriver::voltage; arming requires batt_present). - Re-run on main a1b0e17: all four steps exit 0, and the test really runs (`1 passed`, not a vacuous zero-match filter). - #430 merged with all 8 required contexts SUCCESS. Scope: this promotes the VERIFICATION artifact. The requirement it verifies, SWREQ-FALCON-ORPHAN-P01, is broader (wiring the orphaned crates) and stays `proposed`. #413 stays open until a tagged release carries the fix. Refs #413 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
…can fail, and on main it passes for real (#409) Code-free promotion. Implementation merged in #424 (4c5feda). Evidence, observed: - The flag is gone: ci.yml has no continue-on-error on `cargo fmt --all -- --check` (the artifact's first step). - main bcbe93e's Format job (CI run 35185137151): step `success`, 0 `Diff in`, no `Process completed with exit code` line — a real pass, not a masked failure (the 3ec4a2f log before #424 had 893 diffs and exit code 1 under a `success` job). - #424's own gate did NOT execute this artifact (default `falcon` filter, and it carries no `falcon` tag), so this PR's Verify-Filter includes it: its two steps run in this PR's gate. Scope: this verifies the Format-gate instance only. SWREQ-RELAY-VGATE-P04 stays `proposed` (its v1.139 scope is recording dark tracks). Refs #409 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
… runners it failed on for months (#429, #436) Code-free promotion. Implementation merged in #432 (7daf818) and #437 (bcbe93e). Evidence, observed: - FV-RELAY-FLEET-001's steps executed in #437's merge gate (run 35182187826): all PASS, including `rust-script --test scripts/ci-wedge-watch.rs` and the setup-gh pins. - A run that EVALUATES on main (the artifact's own promotion condition): fleet-status dispatched on bcbe93e, run 35185164979, both jobs on ci-01-8 — `gh-2.100.0.tar.gz: OK`; starvation query succeeded (its "could not be evaluated" step skipped); wedge detector `10 job(s) running, 0 wedged`. ci-01-8 is the box whose scheduled runs printed a vacuous `queued-too-long: 0` before #437. - The detector's first live catch (2026-09-17 00:53Z): Kani (relay-mix-quad) 125.4 min vs 4.0 min median, flagged; recorded on #429. Not claimed (unchanged in the artifact): detection within 15 minutes — scheduled runs are throttled to every few hours (#436, CIFLOW-P01). Refs #429, #436 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
…y job is green and publishes the report Code-free promotion. Implementation merged in #433 (572ae38). Evidence, observed: - FV-RELAY-READY-001's steps executed in #433's merge gate (run 35176152604): all PASS, including the fixture-repo tests of the four verdict bugs. - The artifact's promotion condition — a run on main, GREEN, with a non-empty summary: Release readiness dispatched on 572ae38 (run 35182551834), `Report` step success, printing "## Release readiness — falcon-v1.139.0 / 0 of 15 artifacts done" and the notice "next release still has blocking artifacts". That is exactly the falsification case: the 2026-09-16 scheduled run under the old code failed with exit code 1 and an empty summary on a not-ready tree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
avrabe
enabled auto-merge (squash)
September 17, 2026 05:40
✅ Rivet verification gate — falcon4/4 passed
Source of truth: |
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.
Verify-Filter: (and (has-tag "v1.139") (or (has-tag "battery") (has-tag "fleet") (has-tag "readiness") (has-tag "verification-gate")))
What
This is a code-free promotion under the two-commit rule. It moves the four v1.139 fixes that have already merged from
implementedtoverified: six artifacts, one commit per fix, each commit carrying its evidence. No implementation file changes.check-verification-independence.shreportscode-changed=no, terminal-status-added=yes.They are bundled into one PR on purpose. The artifacts touch disjoint files, and on a contended fleet one CI cycle is cheaper than four. The
Verify-Filtermatches exactly these 4 verification artifacts, so this PR's gate executes every one of them.1 passed, not a vacuous filterbcbe93eFormat: stepsuccess, 0Diff in, no failure exit, and nocontinue-on-errorinci.yml. #424's own gate did not run this artifact (defaultfalconfilter), so its steps run in this PR's gategh … OK, starvation query ok,10 job(s) running, 0 wedged); first live catch recorded on #429After merge,
scripts/release-readiness.rsreports falcon-v1.139.0: 6 of 11, measured on this branch.Still not claimed
proposed. Its v1.139 scope is recording dark tracks in the release notes, which isn't done yet.What remains for v1.139: CLAIMS-P01, EVIDENCE-P01, the VGATE-P04 recording, and then the independent review checkpoint.
Refs #413, #409, #429, #436.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG