Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

Rust 1.99.1: the pin, every workflow that names a toolchain, the clippy delta, and a flaky proof gate #576

Closed
dcharlot wants to merge 5 commits from chore/rust-1.99.1-on-main into main
pull from: chore/rust-1.99.1-on-main
merge into: Transaction-Science:main
Conversation 0 Commits 5 Files changed 99 +531 -460
dcharlot commented 2026-11-02 08:08:13 -05:00
Owner
Copy link

Rust 1.98.0 → 1.99.1, the current stable (channel manifest dated 2026-10-15,
rustc 58cf8f9c3 2026-10-13), across both toolchain pins and every workflow that
installs a toolchain by name.

Why, beyond "newer"

1.98.0 carries a P-critical miscompile, rust-lang/rust#161441 (I-miscompile,
regression-from-stable-to-stable): rustc emits a vacant (null) method slot in a
trait-object vtable, so a safe dynamic call jumps to address zero. RELEASES.md
records the fix in 1.98.1. 1.99.1 also fixes 1.99.0's own regressions (wcslen on
UEFI and embedded targets, x86_64 FFI bool returns, the rust-lld rpath on macOS).

What moves

  • rust-toolchain.toml and eoc/eoc-rs/rust-toolchain.toml: channel 1.98.0 →
    1.99.1. These are the only two pins in the tree, and the root one governs every
    other cargo root — verified on the build host, where the active toolchain
    resolves to 1.99.1-aarch64-apple-darwin (overridden by …/rust-toolchain.toml).
  • 64 workflows, 409 lines: every Install Rust 1.98.0, rustup toolchain install / default / component add / target add --toolchain 1.98.0 and
    --default-toolchain 1.98.0. Two of those lines sit in build steps rather than
    install steps (wai-conformance.yml's two wasm32 (unix) steps each
    rustup target add --toolchain); they move with the rest, because a target
    added to a toolchain that is not installed is an error.
  • smart-byte-rs/Cargo.lock: async-trait 0.1.89 → 0.1.92 (+ syn 3.0.9). 0.1.89
    put #[must_use] on every trait method it generates, and clippy 1.99 counts the
    returned Pin<Box<dyn Future>> as must_use already, so double_must_use fired
    at nine #[async_trait] methods. The attribute is the macro's, not ours, so the
    fix belongs in the macro. Every other lockfile in the tree was already on 0.1.92.
  • The clippy fixes 1.99 newly requires (see the second commit) and two findings
    from re-running that comparison against current main (the third).
  • A fix to this repo's own proof gate (the fourth commit), which this branch's
    first CI run caught: standards-build.yml's joulespec-proofs step read
    echo "$out" | grep -q under set -euo pipefail, so grep -q exiting at its
    first match killed echo with SIGPIPE and a found match read as not found. It
    printed "did not verify" directly beneath Kani's own VERIFICATION:- SUCCESSFUL. Measured on that harness's real 191,128-byte output (its one
    matching line is 1839 of 1843): the piped form fails 1 in 20, a here-string 0
    in 20. A standing ~5% flake, not something the pin introduced — cargo kani
    compiles with its own pinned compiler and never reads rust-toolchain.toml.

What deliberately does not move

  • Measurement records. wai/research/determinism-cost/record.json, the
    sink-energy tables, determinism-tiers.md's "measured … with rustc 1.98.0", and
    the "rustc 1.98.0 (example)" strings in receipts, vectors and docs. These state
    what was measured on 1.98.0. Two of those cases cannot be edited even in
    principle without breaking themselves: the strings sit inside Ed25519-signed
    receipt bodies, and one conformance object is named by its own digest.
  • Two comments that record an observation at 1.98.0: standards-build.yml's
    "Verified on a native arm64 Linux container (rustc 1.98.0): without the flag, 12
    errors; with it, 4457 tests pass", and wai-conformance.yml's note on Rust 1.98's
    LLD 22. 1.99.1 ships LLD 23.1.1, which that note says links those inputs, but
    removing the one-codegen-unit workaround it explains should wait for a run at the
    CI path on x86_64 — it is a separate change with its own evidence.
  • The 1.97 MSRV. rust-version is the floor a consumer of these reference
    implementations must meet, not the compiler this tree builds with. Raising it
    narrows who can build an open standard and buys nothing: no code here needs 1.98
    or 1.99, and the two constants this PR starts using compile on 1.96.0.
    wai-quantum-webgpu.yml installs 1.97.0 beside 1.99.1 to hold that floor; that
    leg is untouched.

Provenance of this branch

The two toolchain commits were written on 2026-10-25 against a main 903 commits
older than this one, pushed to the forge as chore/rust-1.99.1, and never opened
as a pull request. They are reapplied here on current main rather than force-pushed
over, so that branch stays as the record of the original work. One conflict, in
wai-pack.yml, where main had added a pack_verify.py --jobs 2 step immediately
above the step being renamed; both are kept.

This replaces #575, which was the same four commits based before #574. The
repository audit is red on every branch that does not carry #574's zip fix, and
CI checks out a PR's head rather than a merge with its base, so #575's
repo-checks leg failed on six RUSTSEC-2026-0429 findings that had nothing to do
with the toolchain. Rebuilt on main with #574 in it rather than rebased, to avoid
both a force-push and a merge commit in the branch. With that base,
scripts/check-advisories.py passes here: 60 lockfiles, 20 allowed advisories, 63
warnings, not gated.

Evidence

Everything that compiles ran on the build host (aarch64-apple-darwin) through
~/kani-logs/remote/rb. Nothing was built on the dev Mac.

  • The complete new-lint surface, taken from the lint tables rather than from
    whichever lints happened to fire: clippy-driver -Whelp lists 1067 lints on
    1.98.0 and 1079 on 1.99.1. The 14 new names are clippy::assert_is_empty,
    block_scrutinee, definition_in_module_root, manual_bit_width,
    mismatched_bit_width_type, nonnull_unchecked_on_box_ptr,
    rest_pattern_accessible_field, unnecessary_rest_pattern, and rustc's
    duplicate_tools, malformed_diagnostic_filters,
    method_call_on_diverging_infer_var, raw_borrows_via_references,
    recursion_depth_exceeding_limit,
    semicolon_in_expressions_from_non_local_macros. No lint's default level
    changed. Eight of the fourteen are warn-or-deny by default.
  • approx_constant keeps its name but gained constants: of the 24 values
    std::f64::consts has carried, 1.98.0 flags 18 and 1.99.1 flags 20 — the two
    added are exactly EULER_GAMMA and GOLDEN_RATIO.
  • joulespec-rs, the one entry in standards-build.yml with clippy: true:
    cargo clippy --workspace --all-targets -- -D warnings clean on 1.99.1.
  • The two roots whose crates carry #![warn(clippy::pedantic)], run with the
    identical command on both toolchains (cargo clippy --workspace --all-targets -- -D warnings, each leg with its own target dir): aac-rs is unchanged — 3
    errors in 3 kinds on 1.98.0 and the same 3 on 1.99.1, with no kind that only
    1.99.1 reports. openpay goes from 165 errors in 29 kinds to 220 in 30. That
    is below every gate and is not caused by a new lint: no openpay crate declares
    #![deny(warnings)] (0 of 43), its standards-build entry has no clippy: true,
    and each of the ten differing message texts belongs to a lint that already
    exists on 1.98.0 (manual_slice_fill, cast_precision_loss,
    cast_possible_truncation, cast_possible_wrap, needless_pass_by_value) —
    so 1.99.1 finds more sites for pedantic lints both toolchains have. The -D warnings here is stricter than anything CI applies to either root; only
    joulespec-rs carries a clippy gate, and it is clean.
  • scripts/check-lockfiles.sh: 60 lockfiles, all current.
  • scripts/check-workflow-concurrency.sh: 77 workflows, each grouped per ref.
  • scripts/check-no-vanity-metrics.sh: clean over 517 Markdown files.

A note on method, because the first attempt at the comparison was wrong:
rustup run <toolchain> cargo clippy does not select that toolchain's clippy.
cargo resolves the clippy subcommand by searching PATH for cargo-clippy, and
Homebrew's (1.99.1) comes first, so both legs reported clippy 0.1.99 and the
comparison was of one clippy against itself — while rustc --version showed the
expected 1.98.0, which hides it. The runs above call each toolchain's own binary by
path with RUSTC set to match and RUSTUP_TOOLCHAIN unset, and print
cargo-clippy --version per leg so the two can be seen to differ.

What this PR's CI is for

The eight new warn-or-deny-by-default lints above are not exercised by anything
this branch could run by hand in reasonable time — only a handful of roots carry a
CI clippy gate, and the lints could fire in any of the 62 cargo roots. Every
workflow installs 1.99.1 here, so this PR's own run is the test. The pin files
touch every path filter, so expect the full matrix.

🤖 Generated with Claude Code

Closed: superseded by #594: this branch's head sat 29 commits behind main, and CI checks out the head, so its matrix did not test the tree the pin would land on

Rust 1.98.0 → 1.99.1, the current stable (channel manifest dated 2026-10-15, rustc 58cf8f9c3 2026-10-13), across both toolchain pins and every workflow that installs a toolchain by name. ### Why, beyond "newer" 1.98.0 carries a P-critical miscompile, rust-lang/rust#161441 (I-miscompile, regression-from-stable-to-stable): rustc emits a vacant (null) method slot in a trait-object vtable, so a safe dynamic call jumps to address zero. RELEASES.md records the fix in 1.98.1. 1.99.1 also fixes 1.99.0's own regressions (wcslen on UEFI and embedded targets, x86_64 FFI `bool` returns, the rust-lld rpath on macOS). ### What moves - `rust-toolchain.toml` and `eoc/eoc-rs/rust-toolchain.toml`: `channel` 1.98.0 → 1.99.1. These are the only two pins in the tree, and the root one governs every other cargo root — verified on the build host, where the active toolchain resolves to `1.99.1-aarch64-apple-darwin (overridden by …/rust-toolchain.toml)`. - 64 workflows, 409 lines: every `Install Rust 1.98.0`, `rustup toolchain install / default / component add / target add --toolchain 1.98.0` and `--default-toolchain 1.98.0`. Two of those lines sit in build steps rather than install steps (wai-conformance.yml's two `wasm32 (unix)` steps each `rustup target add --toolchain`); they move with the rest, because a target added to a toolchain that is not installed is an error. - `smart-byte-rs/Cargo.lock`: async-trait 0.1.89 → 0.1.92 (+ syn 3.0.9). 0.1.89 put `#[must_use]` on every trait method it generates, and clippy 1.99 counts the returned `Pin<Box<dyn Future>>` as must_use already, so `double_must_use` fired at nine `#[async_trait]` methods. The attribute is the macro's, not ours, so the fix belongs in the macro. Every other lockfile in the tree was already on 0.1.92. - The clippy fixes 1.99 newly requires (see the second commit) and two findings from re-running that comparison against current main (the third). - A fix to this repo's own proof gate (the fourth commit), which this branch's first CI run caught: `standards-build.yml`'s `joulespec-proofs` step read `echo "$out" | grep -q` under `set -euo pipefail`, so `grep -q` exiting at its first match killed `echo` with SIGPIPE and a found match read as not found. It printed "did not verify" directly beneath Kani's own `VERIFICATION:- SUCCESSFUL`. Measured on that harness's real 191,128-byte output (its one matching line is 1839 of 1843): the piped form fails 1 in 20, a here-string 0 in 20. A standing ~5% flake, not something the pin introduced — `cargo kani` compiles with its own pinned compiler and never reads `rust-toolchain.toml`. ### What deliberately does not move - **Measurement records.** `wai/research/determinism-cost/record.json`, the sink-energy tables, `determinism-tiers.md`'s "measured … with rustc 1.98.0", and the `"rustc 1.98.0 (example)"` strings in receipts, vectors and docs. These state what was measured on 1.98.0. Two of those cases cannot be edited even in principle without breaking themselves: the strings sit inside Ed25519-signed receipt bodies, and one conformance object is named by its own digest. - **Two comments** that record an observation at 1.98.0: standards-build.yml's "Verified on a native arm64 Linux container (rustc 1.98.0): without the flag, 12 errors; with it, 4457 tests pass", and wai-conformance.yml's note on Rust 1.98's LLD 22. 1.99.1 ships LLD 23.1.1, which that note says links those inputs, but removing the one-codegen-unit workaround it explains should wait for a run at the CI path on x86_64 — it is a separate change with its own evidence. - **The 1.97 MSRV.** `rust-version` is the floor a consumer of these reference implementations must meet, not the compiler this tree builds with. Raising it narrows who can build an open standard and buys nothing: no code here needs 1.98 or 1.99, and the two constants this PR starts using compile on 1.96.0. `wai-quantum-webgpu.yml` installs 1.97.0 beside 1.99.1 to hold that floor; that leg is untouched. ### Provenance of this branch The two toolchain commits were written on 2026-10-25 against a main 903 commits older than this one, pushed to the forge as `chore/rust-1.99.1`, and never opened as a pull request. They are reapplied here on current main rather than force-pushed over, so that branch stays as the record of the original work. One conflict, in wai-pack.yml, where main had added a `pack_verify.py --jobs 2` step immediately above the step being renamed; both are kept. This replaces #575, which was the same four commits based before #574. The repository audit is red on every branch that does not carry #574's `zip` fix, and CI checks out a PR's head rather than a merge with its base, so #575's `repo-checks` leg failed on six `RUSTSEC-2026-0429` findings that had nothing to do with the toolchain. Rebuilt on main with #574 in it rather than rebased, to avoid both a force-push and a merge commit in the branch. With that base, `scripts/check-advisories.py` passes here: 60 lockfiles, 20 allowed advisories, 63 warnings, not gated. ### Evidence Everything that compiles ran on the build host (aarch64-apple-darwin) through `~/kani-logs/remote/rb`. Nothing was built on the dev Mac. - The complete new-lint surface, taken from the lint tables rather than from whichever lints happened to fire: `clippy-driver -Whelp` lists 1067 lints on 1.98.0 and 1079 on 1.99.1. The 14 new names are `clippy::assert_is_empty`, `block_scrutinee`, `definition_in_module_root`, `manual_bit_width`, `mismatched_bit_width_type`, `nonnull_unchecked_on_box_ptr`, `rest_pattern_accessible_field`, `unnecessary_rest_pattern`, and rustc's `duplicate_tools`, `malformed_diagnostic_filters`, `method_call_on_diverging_infer_var`, `raw_borrows_via_references`, `recursion_depth_exceeding_limit`, `semicolon_in_expressions_from_non_local_macros`. No lint's default level changed. Eight of the fourteen are warn-or-deny by default. - `approx_constant` keeps its name but gained constants: of the 24 values `std::f64::consts` has carried, 1.98.0 flags 18 and 1.99.1 flags 20 — the two added are exactly EULER_GAMMA and GOLDEN_RATIO. - `joulespec-rs`, the one entry in standards-build.yml with `clippy: true`: `cargo clippy --workspace --all-targets -- -D warnings` clean on 1.99.1. - The two roots whose crates carry `#![warn(clippy::pedantic)]`, run with the identical command on both toolchains (`cargo clippy --workspace --all-targets -- -D warnings`, each leg with its own target dir): **aac-rs is unchanged** — 3 errors in 3 kinds on 1.98.0 and the same 3 on 1.99.1, with no kind that only 1.99.1 reports. **openpay** goes from 165 errors in 29 kinds to 220 in 30. That is below every gate and is not caused by a new lint: no openpay crate declares `#![deny(warnings)]` (0 of 43), its standards-build entry has no `clippy: true`, and each of the ten differing message texts belongs to a lint that already exists on 1.98.0 (`manual_slice_fill`, `cast_precision_loss`, `cast_possible_truncation`, `cast_possible_wrap`, `needless_pass_by_value`) — so 1.99.1 finds more sites for pedantic lints both toolchains have. The `-D warnings` here is stricter than anything CI applies to either root; only `joulespec-rs` carries a clippy gate, and it is clean. - `scripts/check-lockfiles.sh`: 60 lockfiles, all current. - `scripts/check-workflow-concurrency.sh`: 77 workflows, each grouped per ref. - `scripts/check-no-vanity-metrics.sh`: clean over 517 Markdown files. A note on method, because the first attempt at the comparison was wrong: `rustup run <toolchain> cargo clippy` does not select that toolchain's clippy. `cargo` resolves the `clippy` subcommand by searching PATH for `cargo-clippy`, and Homebrew's (1.99.1) comes first, so both legs reported `clippy 0.1.99` and the comparison was of one clippy against itself — while `rustc --version` showed the expected 1.98.0, which hides it. The runs above call each toolchain's own binary by path with `RUSTC` set to match and `RUSTUP_TOOLCHAIN` unset, and print `cargo-clippy --version` per leg so the two can be seen to differ. ### What this PR's CI is for The eight new warn-or-deny-by-default lints above are not exercised by anything this branch could run by hand in reasonable time — only a handful of roots carry a CI clippy gate, and the lints could fire in any of the 62 cargo roots. Every workflow installs 1.99.1 here, so this PR's own run is the test. The pin files touch every path filter, so expect the full matrix. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- **Closed:** superseded by #594: this branch's head sat 29 commits behind main, and CI checks out the head, so its matrix did not test the tree the pin would land on 
These are the only lints clippy 1.99.1 reports that clippy 1.98.0 does not.
Every cargo root in the tree was compared on both toolchains (the evidence is
in the next commit). 1.98.0's clippy also builds every target of the fixed
code, and reports nothing it did not report before, so this commit stands
under either pin.

What changed, and why

- clippy::assert_is_empty is new in 1.99. 36 sites, all in test code
  (#[cfg(test)] modules; no lib or bin build reports any):
  aac-core and access-core, 23 sites; openpay's op-crypto-extra, op-emv,
  op-iso20022, op-reconciliation, op-routing, op-screening, op-settlement
  and op-tax, 13 sites. `assert!(x.is_empty())` becomes
  `assert_eq!(x, [] as [T; 0])`, `assert_ne!` for the negation, or `""` for
  strings, so a failure prints the value instead of only "false". aac-core and
  access-core are `#![deny(warnings)]` and `#![deny(clippy::all)]`, so without
  this their clippy run fails on 1.99.1.
  Judgment call: at 18 of the 36 sites, clippy's own "MachineApplicable"
  suggestion does not compile. It names local types by crate-relative path
  (`finder::Found`, which is not in scope in a test module), or offers a bare
  `[]` whose element type cannot be inferred. So each site names its element
  type as its own module sees it (`[] as [Found; 0]`, `[] as [f64; 0]`). The
  four lines rustfmt would wrap are wrapped the way rustfmt wraps them.

- clippy::approx_constant (deny-by-default) now knows EULER_GAMMA and
  GOLDEN_RATIO. Both are in std::f{32,64}::consts and stable since 1.94; the
  jouleclaw workspace MSRV is 1.97.
  - jouleclaw-omni, inference/architecture/mochi.rs: `1.618_034` becomes
    `std::f32::consts::GOLDEN_RATIO`. They are the same f32
    (1.61803400516510009765625), so the latents do not change. This file is
    in standards-build.yml's macOS gate (`cargo clippy -p jouleclaw-omni
    --features metal -- -D warnings`), which fails on 1.99.1 without the fix.
  - jouleclaw-outlier, c_factor: `0.5772156649` becomes
    `std::f64::consts::EULER_GAMMA`. Judgment call: the literal was
    truncated, so c(n) moves by 3.1e-12. The normalisation in the
    isolation-forest paper uses the Euler-Mascheroni constant itself, so this
    is the intended value. No other crate and no committed vector reads these
    scores, and the crate's tests pass unchanged.

- smart-byte-rs/Cargo.lock: async-trait 0.1.89 becomes 0.1.92, which adds
  syn 3.0.9 as its dependency. 0.1.89 put `#[must_use]` on every trait method
  it generates. clippy 1.99 now counts the returned `Pin<Box<dyn Future>>` as
  must_use already, so clippy::double_must_use fired at 9 #[async_trait] trait
  methods. The attribute there is the macro's, not ours, so the right fix is
  the macro: 0.1.92 no longer emits it, and every other lockfile in this tree
  already uses 0.1.92. A narrow `cargo update -p async-trait --precise 0.1.92`
  also moved data-encoding-macro-internal (which accepts syn >=1, <3) from syn
  2 to syn 1. That was put back to syn 2.0.117, as on main, so the lock
  changes only what the bump needs. `cargo update --workspace --locked` and
  scripts/check-lockfiles.sh accept it.

Left as they are

- openpay op-dispute-evidence evidence.rs:92 (clippy::double_must_use) is
  reported on 1.98.0 too. Only the message's wording changed in 1.99.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Approved by the owner on 2026-10-22. Procedure: change `channel`, run
`rustup show`, then run the pipeline.

What changed
- rust-toolchain.toml and eoc/eoc-rs/rust-toolchain.toml: channel "1.98.0"
  becomes "1.99.1". These are the only two pins in the tree, and the root one
  governs every other cargo root.
- 64 workflows under .github/workflows (the forge's CI): every `Install Rust
  1.98.0`, `rustup toolchain install / default / component add / target add
  --toolchain 1.98.0` and `--default-toolchain 1.98.0` now names 1.99.1
  (409 lines). Two of those lines are in build steps rather than install
  steps (wai-conformance.yml's two `wasm32 (unix)` steps each
  `rustup target add --toolchain`), and they move with the rest: a target
  added to a toolchain that is not installed is an error.
- Left as they are, because they record what was measured on 1.98.0:
  standards-build.yml's "Verified on a native arm64 Linux container (rustc
  1.98.0)", wai-conformance.yml's note on Rust 1.98's LLD 22, and the
  "rustc 1.98.0 (example)" strings in receipts, vectors and docs. The
  one-codegen-unit workaround that note explains also stays. 1.99.1 ships
  LLD 23.1.1, which the note says links those inputs, but removing the
  workaround should wait for a run at the CI path on x86_64.

Why
- 1.98.0 has a P-critical miscompile, rust-lang/rust#161441 (I-miscompile,
  regression-from-stable-to-stable). rustc emits a vacant (null) method slot
  in a trait-object vtable, so a safe dynamic call jumps to address zero
  (undefined behaviour). RELEASES.md records the fix in 1.98.1 ("rustc: fix
  miscompilation in generating vtables").
- 1.99.1 is the current stable (channel manifest dated 2026-10-15; rustc
  58cf8f9c3 2026-10-13). It also fixes 1.99.0's own regressions: wcslen on
  UEFI and embedded targets, x86_64 FFI `bool` returns, and the rust-lld rpath
  on macOS.

Evidence
All of it ran on the build host ([email protected], aarch64-apple-darwin)
through ~/kani-logs/remote/rb. Nothing was built on the dev Mac.

- `rustup show`: the active toolchain is 1.99.1-aarch64-apple-darwin,
  "overridden by .../rust-toolchain.toml" (and by eoc/eoc-rs's own file
  there). rustc 1.99.1 (58cf8f9c3 2026-10-13), LLVM 23.1.1, clippy 0.1.99,
  rustfmt 1.10.0. The baseline is rustc 1.98.0 (88d9e12ae 2026-08-18).
- Scope: every cargo root the pin governs, which is 46 of the 49 tracked
  lockfiles. The other three: two are vendored crates that resolve inside
  their parents, and wai/wai-rs/fuzz builds on its own pinned nightly.
- Trees. The final tree is main at 96117c570 plus these two commits. Main
  moved four times while this ran, and each root's evidence comes from the
  newest tree it was run on:
  - 13 roots on the final tree: every root main changed after 1a465f23d,
    and every root that consumes such a crate by path.
  - 12 roots on 1a465f23d plus these two commits.
  - 7 roots on b16816671 plus these two commits.
  - 14 roots on aa61ab3b9 plus the pin change.
  For each root in the last three groups, checked with git diff and the
  lockfiles' path packages: none of its files, and no crate it reaches by
  path, differs on the final tree.
- Each root got:
  (a) `cargo fmt --all -- --check` on the pin and on 1.98.0. The output is
      byte-identical in all 46. CI gates no root on rustfmt, and none is
      rustfmt-clean on main.
  (b) `cargo clippy --locked --keep-going --workspace --all-targets` on both
      toolchains, with the diagnostics compared line by line. After the
      previous commit, no root has a diagnostic that only 1.99.1 reports.
      openpay's one differing line is the same lint at the same site,
      reworded.
  (c) `cargo test --workspace --locked`.
  (d) the root's other CI steps that can run on this host: feature-gated
      tests, conformance suites, release-profile tests, the aac page-set
      checks, and every clippy -D warnings gate. The gates are
      standards-build's macOS meter and omni lints (jouleclaw-energy x2,
      jouleclaw-omni metal, jouleclaw-loader-gguf, jcp, proof, eoc, sandbox),
      wai-pack, wai-quantum-cli (default, no-default and metal),
      wai-quantum-service, wai-quantum-qpu and wai-quantum-desktop.
- Totals: `cargo test --workspace` ran in 43 roots: 12,532 passed, 1 failed,
  101 ignored. The other 3 roots are wasm32-only, and their
  `cargo build --release --target wasm32-unknown-unknown` passed. Every
  other CI step passed (62 of 62).
- On the final tree: scripts/check-lockfiles.sh (cargo 1.99.1) found all 47
  lockfiles current, and scripts/check-advisories.py passes.
- tokio is 1.54.1 in every lockfile cargo reads. That is patched for both
  RUSTSEC-2026-0386 (>= 1.53.3) and RUSTSEC-2026-0384 (>= 1.54.1). The 1.53.1
  in vendor/wtransport/Cargo.lock is the upstream file kept with the vendored
  source; cargo resolves wtransport inside its parents, and both gates skip
  that file.
- What is not green, each one reproduced on 1.98.0:
  - wai-ops-gpu: under the debug profile, `corpus` trips the debug_assert at
    exec.rs:187 on both toolchains. CI runs it in release only, and that
    passes (6/6).
  - wai-ops: clippy::derived_hash_with_manual_eq (deny-by-default) on both
    toolchains. No CI job runs clippy there.
  - wai-vector/wasm: `--all-targets` cannot build the lib-test target (its
    own `panic_impl`) on either toolchain. `clippy --lib` for wasm32 reports
    0 diagnostics on both.
  - eoc-cascade's hit_calibration_process_energy test reads real energy
    counters, and it fails some of the time on the loaded shared host. In
    interleaved runs each toolchain passed 18 of 20. The full eoc-rs suite
    passed on the final tree (741 passed).
- Environment, not code:
  - wai-quantum-desktop embeds the Studio's build, so wai/quantum-studio was
    built first (`npm ci`, `node build.mjs`), as CI does.
- Not covered here: the x86_64 and arm64 Linux and Windows legs; the GPU,
  NPU, FPGA, emulator and hardware-meter legs; wasm32 tests under Node,
  wasmtime and wasip2; and the fuzz job.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
The two commits before this were written against a main 903 commits older than
this one, so their comparison of clippy 1.98.0 against 1.99.1 was re-run over
every cargo root that has gained Rust code since. It found these.

Method, because the first attempt was wrong

`rustup run <toolchain> cargo clippy` does NOT select that toolchain's clippy.
`cargo` resolves the `clippy` subcommand by searching PATH for `cargo-clippy`,
and on this machine Homebrew's (1.99.1) comes first, so both toolchains reported
`clippy 0.1.99` and the comparison was of one clippy against itself. The runs
behind this commit call each toolchain's own binary by path
(`~/.rustup/toolchains/<tc>/bin/cargo-clippy`, with `RUSTC` set to match and
`RUSTUP_TOOLCHAIN` unset), which gives `clippy 0.1.98` and `clippy 0.1.99`.
Confirming the delta that way: of the 24 constants `std::f64::consts` has
carried, 1.98.0 flags 18 and 1.99.1 flags 20 — the two added are exactly
EULER_GAMMA and GOLDEN_RATIO, as the previous commit says.

What changed

- wai-quantum, engine/synth/kak.rs: `1.618_033_988_749_895` becomes
  `std::f64::consts::GOLDEN_RATIO`. This is a `clippy::approx_constant`, which
  is deny-by-default, so it is an error and not a warning. The line arrived on
  2026-10-27, two days after the comparison was made, as one of six "mixing
  weights with nothing in common" that `kak` tries in turn. The literal and the
  constant are the same f64 — both `0x3ff9e3779b97f4a8` — so no value the
  decomposition computes changes. The constant is stable well below this tree's
  1.97 MSRV (it compiles on 1.96.0). The other five weights are not flagged:
  1/sqrt(3) and Feigenbaum's delta are not constants clippy knows.
  No workflow runs clippy inside wai/wai-quantum, so this was latent in CI and
  would have met anyone who ran clippy there by hand.

- Six `assert!(x.is_empty())` the previous commit missed, five of which were
  already in the tree when it was written: aac-core (translations, prediction
  twice, symbols), access-core (scan_order) and openpay's op-connect (account).
  `clippy::assert_is_empty` is new in 1.99, is allow-by-default, and reaches
  these crates through their own `#![warn(clippy::pedantic)]`, which
  `#![deny(warnings)]` then makes an error in the two aac crates.
  Each gains a message naming the value instead of the array comparison the
  previous commit used, because none of these six is a Vec or a slice: four are
  a HashMap, a BTreeSet or `OrderDiff`, which cannot be compared to `[] as [T; 0]`
  at all, and `Vec<PredictionCandidate>` derives Debug but not PartialEq, which
  `assert_eq!` against an empty array needs. A message is what the lint asks for
  anyway — it exists so a failure prints the value rather than only "false" — and
  it is the reason the lint does not fire at the other 147 `assert!(…is_empty())`
  sites that have arrived since: with a message supplied, it stays quiet.

Not changed, with the reason

- The 1.97 MSRV. `rust-version` is the floor a consumer of these reference
  implementations must meet, not the compiler this tree builds with; raising it
  narrows who can build an open standard and buys nothing, since no code here
  needs 1.98 or 1.99. `wai-quantum-webgpu.yml` installs 1.97.0 beside 1.99.1 to
  hold that floor, and that leg is untouched.

Co-Authored-By: Claude Opus 5 <[email protected]>
standards-build: the proof gate read echo | grep -q under pipefail, a 1-in-20 flake
Some checks failed
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 35s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 1m34s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 16m11s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 3m8s
Details
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 11m3s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 19m36s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Successful in 44m20s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h24m38s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Successful in 41m49s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Successful in 19m52s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Successful in 20m7s
Details
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 15s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m44s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 2m5s
Details
wai-ops-npu integer operators on neural processors / builds · no device is not a pass (linux-arm64) (pull_request) Successful in 23s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Has been cancelled
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Has been cancelled
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Has been cancelled
Details
wai-pack / wai-pack · dependency licences (pull_request) Has been cancelled
Details
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Has been cancelled
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Has been cancelled
Details
wai-ops integer operators / linux-aarch64 (pull_request) Has been cancelled
Details
wai-quantum HIP member / member · HIP absent (linux-arm64) (pull_request) Has been cancelled
Details
wai-quantum npu-cores member / member · npu-cores absent (linux-arm64) (pull_request) Has been cancelled
Details
wai-quantum pulse and dynamics / the same bits · linux-arm64 (pull_request) Has been cancelled
Details
wai-quantum extension points / the registry and the example · linux-arm64 (pull_request) Has been cancelled
Details
wai-quantum tensor-engine member / member · tensor engine absent (linux-arm64) (pull_request) Has been cancelled
Details
wai-quantum variational and algorithm library / parameters, gradients, optimisers, VQE, QAOA and builders · linux-arm64, release (pull_request) Has been cancelled
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Has been cancelled
Details
wai-vector vector graphics / linux-aarch64 (pull_request) Has been cancelled
Details
5fbd718b10 
The `joulespec-proofs` leg failed on this branch with Kani's own output saying
the opposite of the gate's verdict:

     ** 0 of 336 failed (1 unreachable)
     ** 4 of 4 cover properties satisfied
    VERIFICATION:- SUCCESSFUL
    widening_a_set_can_only_lower_its_cap did not verify

The step runs under `set -euo pipefail` and asked
`echo "$out" | grep -q '^VERIFICATION:- SUCCESSFUL'`. `grep -q` exits at its
first match; `echo` is then still writing, takes SIGPIPE and exits 141; and
`pipefail` makes the pipeline return 141, so a match that was found reads as not
found. The failure message is printed by the `||` branch of a grep that in fact
matched.

Measured on the build host against this harness's real output rather than
assumed: the output is 191,128 bytes, its one `VERIFICATION:- SUCCESSFUL` line
is line 1839 and four lines follow it, so `grep -q` always exits with the writer
mid-stream. Twenty trials of each form on that exact string: the piped form
failed 1, the here-string 0. So this is a standing ~5% flake in the gate, not
something the toolchain change introduced — `cargo kani` compiles with its own
pinned compiler and does not read `rust-toolchain.toml`, so the pin cannot alter
the property count. #570 passed this leg for the same reason a coin comes up
heads.

Both `grep -q` reads in the two proof steps now take a here-string, which has no
writer to kill. The two that capture into a variable already end in `|| true`
and are unaffected.

This is the fourth place this pattern has been found in the repo (see the
here-string fixes in `check-lockfiles.sh`, `check-tests-in-ci-selftest.sh` and
`standards-touched-selftest.sh`), and the first in a workflow rather than a
script.

Co-Authored-By: Claude Opus 5 <[email protected]>
CI: two macOS legs depended on runner state the pin change cleared or never had
All checks were successful
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 14s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 55s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 2m16s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 10m38s
Details
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 5m30s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 11m41s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h1m16s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Successful in 34m43s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Successful in 35m7s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Successful in 17m37s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Successful in 17m26s
Details
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 5s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m25s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 1m23s
Details
wai-ops-npu integer operators on neural processors / builds · no device is not a pass (linux-arm64) (pull_request) Successful in 18s
Details
wai-ops integer operators / linux-aarch64 (pull_request) Successful in 1m5s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m53s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Successful in 34m26s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 23s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m21s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 7m10s
Details
wai-quantum HIP member / member · HIP absent (linux-arm64) (pull_request) Successful in 57s
Details
wai-quantum npu-cores member / member · npu-cores absent (linux-arm64) (pull_request) Successful in 27s
Details
wai-quantum pulse and dynamics / the same bits · linux-arm64 (pull_request) Successful in 1m26s
Details
wai-quantum tensor-engine member / member · tensor engine absent (linux-arm64) (pull_request) Successful in 20s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Successful in 16m46s
Details
wai-quantum extension points / the registry and the example · linux-arm64 (pull_request) Successful in 2m31s
Details
wai-quantum variational and algorithm library / parameters, gradients, optimisers, VQE, QAOA and builders · linux-arm64, release (pull_request) Successful in 1m43s
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Successful in 2m37s
Details
wai-vector vector graphics / linux-aarch64 (pull_request) Successful in 2m41s
Details
3cc2a772a9 
Both failed on this branch for reasons that are about how the `macos` label is
provisioned, not about the code. That label is served by four hosts, which are
not identically set up:

  tx-dev-mac         Mac Studio M3 Ultra      full Xcode
  tx-mbp-m5max-48    MacBook Pro M5 Max 48    full Xcode
  tx-mbp-m4max-128   MacBook Pro M4 Max 128   full Xcode
  tx-imac-pro-macos  iMac Pro (x86_64)        Command Line Tools only

Which host takes a job is not predictable, so a leg that needs more than the
base install passes or fails by where it lands.

wai-examples, the apple-app step
  `rustup target add` had never named the apple slices' targets; the job ran on
  targets some earlier toolchain happened to have left on the runner. A target's
  std belongs to one toolchain, so moving the pin to 1.99.1 left the job with
  none of them and the macos slice failed at x86_64-apple-darwin with E0463,
  "can't find crate for `core`". The five targets are now added by name, the
  same set and the same line as wai-sink-swift.yml, which has always done this.
  The tvos slices' nightly is a separate toolchain and keeps its own targets, so
  it is not re-added.

jouleclaw-fabrics, the Metal shader step
  Xcode ships the Metal compiler as a downloadable component, and an Xcode or
  macOS upgrade uninstalls it. Three of the four hosts reported
  `Status: uninstalled` (Xcode 27B47), and on those every `xcrun metal` fails
  with "missing Metal Toolchain" -- which check-metal-shaders.py reports as all
  44 shaders failing to compile, so a provisioning gap reads as a code failure.
  The job now installs the component if it is absent. It is idempotent and
  persists on the host, so the download happens once per host per Xcode version,
  and it makes the job correct wherever it lands instead of only on the host
  that was provisioned by hand. Where there is no full Xcode -- the iMac Pro --
  it now fails with that as the stated reason rather than as 44 broken shaders.

  Verified on two real hosts rather than reasoned about: the absent branch takes
  the download path on a host reporting `uninstalled`, and the present branch
  short-circuits on the Studio, printing `Apple metal version 32023.922`. The
  component was installed on the Studio by hand first and
  `scripts/check-metal-shaders.py` then reported 44 compiled, 0 failed,
  0 skipped, which is what confirmed the shaders themselves are fine.

Neither leg's workflow had said what it needed; both read it off a host. That is
the class of fault a toolchain change exposes, because it clears per-toolchain
state while leaving the host otherwise untouched.

Co-Authored-By: Claude Opus 5 <[email protected]>
dcharlot closed this pull request 2026-11-03 01:17:53 -05:00
Some checks failed
joule-moq-room room service / joule-moq-room · does this change touch it (pull_request) Successful in 24s
Details
wai-app and Create / wai-app · does this change touch it (pull_request) Successful in 9s
Details
jouleclaw fabrics / cuda (linux, RTX 4050 + Vulkan loader) (pull_request) Successful in 41s
Details
joule-moq-remote host agent / joule-moq-remote · does this change touch it (pull_request) Successful in 34s
Details
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 31s
Details
jouleclaw fabrics / vulkan (linux, RTX 4050 + Vulkan loader) (pull_request) Successful in 15s
Details
joule-code conformance gate / joule-moq-relay, its own energy on a counter (macos) (pull_request) Successful in 1m8s
Details
jouleclaw fabrics / metal (macOS, Apple GPU) (pull_request) Successful in 1m23s
Details
joule-moq-remote host agent / joule-moq-remote, every target (macos) (pull_request) Successful in 50s
Details
wai-quantum on every processor / emulated · aarch64-unknown-linux-gnu (pull_request) Successful in 2m39s
Details
joule-code conformance gate / Build + round-trip C1-C4 vectors (pull_request) Successful in 3m39s
Details
wai-quantum on every processor / emulated · armv7-unknown-linux-gnueabihf (pull_request) Successful in 2m54s
Details
wai-ops differential (nightly) / differential · debug (pull_request) Successful in 4m45s
Details
wai-ops differential (nightly) / differential · release (pull_request) Successful in 5m37s
Details
wai-quantum on every processor / emulated · loongarch64-unknown-linux-gnu (pull_request) Successful in 5m40s
Details
wai-quantum on every processor / emulated · powerpc64le-unknown-linux-gnu (pull_request) Successful in 3m34s
Details
wai-web reach builds / wai-web reach · does this change touch it (pull_request) Successful in 6s
Details
wai-app and Create / wai-app · tests, clippy, the line language's verifier (linux) (pull_request) Successful in 31s
Details
wai-app and Create / wai-app · Create, browser end-to-end (macos) (pull_request) Successful in 7m55s
Details
wai-quantum on every processor / emulated · riscv64gc-unknown-linux-gnu (pull_request) Successful in 5m42s
Details
wai-quantum on every processor / emulated · powerpc64-unknown-linux-gnu (pull_request) Successful in 6m50s
Details
wai-web reach builds / wai-web reach builds · the package of record, every output as recorded (pull_request) Successful in 2m49s
Details
wai-quantum WebGPU member / member · DX12 and Vulkan (cbio-windows) (pull_request) Successful in 13m3s
Details
wai-quantum on every processor / emulated · s390x-unknown-linux-gnu (pull_request) Successful in 8m47s
Details
wai-web reach builds / wai-web reach builds · this tree's wai-web, every rung on its engine line (pull_request) Successful in 4m40s
Details
wai-quantum on every processor / emulated · sparc64-unknown-linux-gnu (pull_request) Successful in 11m47s
Details
wai-quantum on every processor / emulated · i686-unknown-linux-gnu (pull_request) Successful in 13m12s
Details
joule-code conformance gate / joule-moq-relay, every target (pull_request) Successful in 5m15s
Details
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 43s
Details
wai-audit collector and player integration / does this change touch it (pull_request) Successful in 52s
Details
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (pull_request) Successful in 20s
Details
wai cross-architecture byte-equality / does this change touch it (pull_request) Successful in 32s
Details
WAI operation catalogue / does this change touch it (pull_request) Successful in 21s
Details
joule-code conformance gate / joule-moq-ingest, every target (pull_request) Successful in 6m33s
Details
WAI conformance / does this change touch it (pull_request) Successful in 35s
Details
WAI energy receipts / does this change touch it (pull_request) Successful in 28s
Details
WAI examples / WAI examples · does this change touch them (pull_request) Successful in 29s
Details
wai formal verification (integer core) / does this change touch it (pull_request) Successful in 18s
Details
wai-fleet service / does this change touch it (pull_request) Successful in 24s
Details
WAI JPEG-AI whole decode (pinned inputs, required) / does this change touch it (pull_request) Successful in 23s
Details
WAI HTTP delivery / WAI HTTP · does this change touch it (pull_request) Successful in 25s
Details
wai-key-proxy / does this change touch it (pull_request) Successful in 21s
Details
wai-ledger service / does this change touch it (pull_request) Successful in 24s
Details
WAI neural decoders end-to-end / does this change touch it (pull_request) Successful in 18s
Details
WAI neural sink gates / does this change touch it (pull_request) Successful in 24s
Details
wai-ops-gpu integer operators on GPUs / does this change touch it (pull_request) Successful in 23s
Details
wai-ops-npu integer operators on neural processors / does this change touch it (pull_request) Successful in 23s
Details
wai-ops integer operators / does this change touch it (pull_request) Successful in 15s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 6m50s
Details
wai-pack / wai-pack · does this change touch it (pull_request) Successful in 20s
Details
wai-quantum command line / does this change touch it (pull_request) Successful in 24s
Details
wai-quantum contract / does this change touch it (pull_request) Successful in 21s
Details
wai-quantum CUDA member / does this change touch it (pull_request) Successful in 18s
Details
wai-quantum dataflow member / does this change touch it (pull_request) Successful in 30s
Details
wai-quantum docs, course and locales / does this change touch it (pull_request) Successful in 33s
Details
WAI conformance / fast integer kernels, every x86_64 kernel set (AVX-512 silicon) (pull_request) Successful in 3m41s
Details
wai-quantum signal processor / does this change touch it (pull_request) Successful in 43s
Details
wai-ops-npu integer operators on neural processors / neural processor (framework-128gb silicon) (pull_request) Successful in 10s
Details
wai-quantum editors / does this change touch it (pull_request) Successful in 32s
Details
wai-quantum resource estimation / does this change touch it (pull_request) Successful in 37s
Details
wai-quantum other formats / does this change touch it (pull_request) Successful in 30s
Details
wai-quantum FPGA member / does this change touch it (pull_request) Successful in 21s
Details
wai-quantum HIP member / does this change touch it (pull_request) Successful in 23s
Details
wai-quantum CUDA member / member · CUDA (jetson-hub) (pull_request) Successful in 1m40s
Details
wai-quantum for JavaScript / does this change touch it (pull_request) Successful in 30s
Details
wai-quantum OpenQASM reader / does this change touch it (pull_request) Successful in 26s
Details
wai-quantum CUDA member / member · CUDA (thor) (pull_request) Successful in 1m53s
Details
wai-quantum Metal member / does this change touch it (pull_request) Successful in 26s
Details
wai-quantum npu-cores member / does this change touch it (pull_request) Successful in 32s
Details
wai-quantum neural-processor member / does this change touch it (pull_request) Successful in 32s
Details
wai-quantum OpenCL member / does this change touch it (pull_request) Successful in 30s
Details
wai-quantum HIP member / member · HIP (framework-128gb) (pull_request) Successful in 1m4s
Details
wai-quantum pulse and dynamics / does this change touch it (pull_request) Successful in 31s
Details
wai-quantum OpenCL member / member · OpenCL GPU and CPU (jetson-hub) (pull_request) Successful in 37s
Details
wai-quantum error correction and mitigation / does this change touch it (pull_request) Successful in 40s
Details
wai-quantum for Python / does this change touch it (pull_request) Successful in 52s
Details
wai-quantum OpenCL member / member · OpenCL GPU and CPU (thor) (pull_request) Successful in 50s
Details
wai-quantum extension points / does this change touch it (pull_request) Successful in 39s
Details
wai-quantum-qpu / does this change touch it (pull_request) Successful in 1m1s
Details
wai-quantum service / does this change touch it (pull_request) Successful in 43s
Details
wai-quantum npu-cores member / member · npu-cores, neural processor (framework-128gb silicon) (pull_request) Successful in 1m24s
Details
wai-quantum matrix-extension member / does this change touch it (pull_request) Successful in 26s
Details
wai-quantum tensor-engine member / does this change touch it (pull_request) Successful in 29s
Details
wai-quantum OpenCL member / member · OpenCL GPU (framework-128gb) (pull_request) Successful in 27s
Details
wai-quantum studio and desktop / does this change touch it (pull_request) Successful in 39s
Details
wai-quantum portable tensor program / does this change touch it (pull_request) Successful in 29s
Details
wai-quantum variational and algorithm library / does this change touch it (pull_request) Successful in 28s
Details
wai-quantum CPU vector units / does this change touch it (pull_request) Successful in 25s
Details
wai-quantum portable tensor program / tensor program · integrated GPU (framework-128gb) (pull_request) Successful in 16s
Details
wai-quantum verdicts and repairs / does this change touch it (pull_request) Successful in 18s
Details
wai-quantum WebGPU member / does this change touch it (pull_request) Successful in 24s
Details
wai-quantum CPU vector units / member · vector units, avx2 and avx512 (framework-128gb silicon) (pull_request) Successful in 23s
Details
wai-quantum views in agent hosts / does this change touch it (pull_request) Successful in 36s
Details
wai-quantum service / service energy · linux packages (pull_request) Successful in 1m35s
Details
wai-sink-android native sink library / does this change touch it (pull_request) Successful in 28s
Details
wai-quantum portable tensor program / tensor program · GPUs (jetson-hub) (pull_request) Successful in 26s
Details
wai-sink-swift native sink package / does this change touch it (pull_request) Successful in 38s
Details
WAI Studio / does this change touch it (pull_request) Successful in 27s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / does this change touch it (pull_request) Successful in 30s
Details
wai-web wasm32 / does this change touch it (pull_request) Successful in 27s
Details
wai-vector vector graphics / does this change touch it (pull_request) Successful in 31s
Details
joule-moq-remote host agent / joule-moq-remote, every target (linux-arm64) (pull_request) Failing after 3m50s
Details
joule-moq-room room service / joule-moq-room, every target (pull_request) Successful in 6m45s
Details
wai-quantum WebGPU member / member · integrated GPU, Vulkan (framework-128gb) (pull_request) Successful in 8m44s
Details
wai-quantum studio and desktop / desktop app · windows (pull_request) Successful in 9m13s
Details
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 54s
Details
wai-quantum WebGPU member / member · GPU, Vulkan (jetson-hub) (pull_request) Successful in 23m18s
Details
standards workspaces build + test / joulespec-proofs (joulespec/joulespec-rs, joulespec-proofs, true, macos) (pull_request) Successful in 1m37s
Details
standards workspaces build + test / arl-rs (arl/arl-rs, arl-rs, linux) (pull_request) Successful in 31s
Details
wai cross-architecture byte-equality / macos-arm64 (reference) (pull_request) Successful in 28s
Details
wai-quantum WebGPU member / member · GPU, Vulkan (thor) (pull_request) Successful in 25m15s
Details
standards workspaces build + test / eoc-rs (eoc/eoc-rs, -p eoc-meter --features cuda, eoc-rs, linux) (pull_request) Successful in 56s
Details
wai-audit collector and player integration / collector, player integration and the browser end to end · macos (pull_request) Successful in 3m17s
Details
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 26s
Details
standards workspaces build + test / macOS energy backends (pull_request) Successful in 6m16s
Details
standards workspaces build + test / joulehook-rs (joulehook/joulehook-rs, joulehook-rs, linux) (pull_request) Successful in 32s
Details
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 1m58s
Details
standards workspaces build + test / pool-rs (pool/pool-rs, pool-rs, linux) (pull_request) Successful in 26s
Details
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 47s
Details
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 2m24s
Details
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, -p sandbox-tee --features amd-kds,intel-pcs, sandbox-rs, linux) (pull_request) Successful in 1m27s
Details
standards workspaces build + test / proof-rs (proof/conformance/v1/joulespec.toml, proof-conformance, proof/proof-rs, proof-rs, linux, true) (pull_request) Successful in 1m59s
Details
standards workspaces build + test / sense-rs (sense/sense-rs, sense-rs, linux) (pull_request) Successful in 30s
Details
wai-audit collector and player integration / collector · linux (pull_request) Successful in 1m16s
Details
standards workspaces build + test / joulespec-rs (true, joulespec/joulespec-rs, true, joulespec-rs, linux) (pull_request) Successful in 1m38s
Details
wai cross-architecture byte-equality / linux-x86_64 (pull_request) Successful in 37s
Details
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (pull_request) Successful in 2m2s
Details
standards workspaces build + test / smart-byte-rs (smart-byte/smart-byte-rs, smart-byte-rs, linux) (pull_request) Successful in 3m49s
Details
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (pull_request) Successful in 2m42s
Details
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 31s
Details
WAI conformance / faces from keypoints under wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m39s
Details
WAI energy receipts / energy receipts · macos (pull_request) Successful in 7m2s
Details
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 3m25s
Details
WAI operation catalogue / the catalogue and every door · linux (pull_request) Successful in 4m26s
Details
wai formal verification (integer core) / every harness in one shard (pull_request) Successful in 13s
Details
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 12m14s
Details
wai-fleet service / service · macos (pull_request) Successful in 34s
Details
wai-ledger service / service · macos (pull_request) Successful in 43s
Details
WAI examples / WAI examples · portable · linux (pull_request) Successful in 8m46s
Details
wai formal verification (integer core) / kani (rans64-t2) (pull_request) Successful in 11m11s
Details
wai-ops-gpu integer operators on GPUs / Metal GPU and browser WebGPU (macos) (pull_request) Successful in 7m18s
Details
wai formal verification (integer core) / kani (arith) (pull_request) Successful in 9m35s
Details
wai-quantum command line / command line · macos (pull_request) Successful in 59s
Details
wai-ops integer operators / macos-arm64 (pull_request) Successful in 2m22s
Details
wai-quantum dataflow member / member · dataflow device absent (macos) (pull_request) Successful in 14s
Details
wai formal verification (integer core) / kani (plan) (pull_request) Successful in 5m11s
Details
wai-pack / wai-pack · macos (pull_request) Successful in 2m21s
Details
wai-quantum FPGA member / member · FPGA datapath, simulated (macos) (pull_request) Successful in 1m1s
Details
WAI energy receipts / energy receipts · linux (pull_request) Successful in 14m12s
Details
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 16m2s
Details
wai-quantum OpenCL member / member · OpenCL GPU (macos) (pull_request) Successful in 23s
Details
wai formal verification (integer core) / kani (stage) (pull_request) Successful in 2m55s
Details
wai-quantum pulse and dynamics / the same bits · macos (pull_request) Successful in 49s
Details
wai-quantum editors / editors · macos (pull_request) Successful in 2m45s
Details
wai-fleet service / service · linux (pull_request) Successful in 1m47s
Details
wai-key-proxy / proxy · linux (pull_request) Successful in 1m2s
Details
wai-quantum for Python / python · macos (pull_request) Successful in 1m52s
Details
wai-quantum-qpu / credentials in the keychain (macos) (pull_request) Successful in 21s
Details
wai-quantum Metal member / member · Metal (macos) (pull_request) Successful in 2m10s
Details
wai-ledger service / service · linux (pull_request) Successful in 1m18s
Details
wai-quantum neural-processor member / member · neural processor (macos) (pull_request) Successful in 4m24s
Details
wai-quantum matrix-extension member / member · matrix extension absent (macos) (pull_request) Successful in 50s
Details
wai-quantum portable tensor program / tensor program · Metal and the arm64 CPU (macos) (pull_request) Successful in 16s
Details
WAI examples / WAI examples · the archive, the readiness check, the browser and Apple · macos (pull_request) Successful in 24m10s
Details
wai-quantum CPU vector units / member · vector unit absent (macos) (pull_request) Successful in 55s
Details
WAI neural decoders end-to-end / synthetic fixtures → Rust decode → reference (±4) (pull_request) Successful in 1m19s
Details
wai formal verification (integer core) / kani (sound) (pull_request) Successful in 11m19s
Details
wai formal verification (integer core) / kani (integer-core) (pull_request) Successful in 6m30s
Details
wai-quantum WebGPU member / member · browser WebGPU (macos) (pull_request) Successful in 1m27s
Details
WAI JPEG-AI whole decode (pinned inputs, required) / fetch pinned JPEG-AI inputs → whole decode + pixel hash, required (pull_request) Successful in 5m58s
Details
WAI neural sink gates / model-free refusals of the neural sink (pull_request) Successful in 1m27s
Details
wai-ops integer operators / wasm32-wasip2 (wasmtime) (pull_request) Successful in 31s
Details
wai-ops integer operators / wasm32 under Node (pull_request) Successful in 24s
Details
wai-ops integer operators / independent checker (Python) (pull_request) Successful in 18s
Details
wai-ops integer operators / linux-x86_64 (pull_request) Successful in 58s
Details
wai-quantum service / service · macos (pull_request) Successful in 4m16s
Details
wai-pack / wai-pack · linux (pull_request) Successful in 2m0s
Details
wai-ops-gpu integer operators on GPUs / builds · no adapter is not a pass (linux) (pull_request) Successful in 3m12s
Details
wai-quantum contract / the policy is linked, and the deprecations page reads (pull_request) Successful in 5s
Details
wai-quantum command line / command line · linux (pull_request) Successful in 2m46s
Details
wai-quantum CUDA member / member · CUDA absent (linux) (pull_request) Successful in 1m35s
Details
wai-quantum studio and desktop / desktop app · macos (pull_request) Successful in 7m11s
Details
wai-quantum contract / API compatibility · linux (pull_request) Successful in 4m39s
Details
wai-quantum WebGPU member / member · Metal (macos) (pull_request) Successful in 8m7s
Details
wai-quantum dataflow member / member · dataflow device, simulated (pci 1e52:401e) (pull_request) Successful in 1m51s
Details
wai-quantum dataflow member / member · dataflow device, simulated (pci 1e52:b140) (pull_request) Successful in 4m1s
Details
wai-quantum docs, course and locales / the Studio's words in every locale · linux (pull_request) Successful in 9s
Details
wai-quantum docs, course and locales / the course and the command line's languages · linux (pull_request) Successful in 1m40s
Details
wai-quantum contract / schemas and the committed tool lists · linux (pull_request) Successful in 5m49s
Details
WAI Studio / Studio in Chromium and Firefox · macos (pull_request) Successful in 7m58s
Details
wai-vector vector graphics / macos-arm64 (pull_request) Successful in 5m14s
Details
wai-quantum editors / editors · linux (pull_request) Successful in 2m13s
Details
wai-quantum resource estimation / estimation and calibration · linux, release (pull_request) Successful in 1m54s
Details
wai-sink-swift native sink package / libwai slices, desktop tests, simulator tests · macos (pull_request) Successful in 12m8s
Details
wai-quantum other formats / the set under wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m35s
Details
wai-quantum FPGA member / member · FPGA simulation absent (linux) (pull_request) Successful in 22s
Details
wai-quantum other formats / readers, writers and the set · linux (pull_request) Successful in 3m50s
Details
wai-quantum for JavaScript / javascript · linux (pull_request) Successful in 2m49s
Details
wai formal verification (integer core) / kani (stage-long) (pull_request) Successful in 22m54s
Details
wai-quantum OpenQASM reader / reader and corpus · linux (pull_request) Successful in 1m35s
Details
wai-quantum Metal member / member · Metal absent (linux) (pull_request) Successful in 29s
Details
wai-quantum neural-processor member / member · neural processor absent (linux) (pull_request) Successful in 23s
Details
wai-quantum OpenQASM reader / corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 49s
Details
wai-quantum OpenCL member / member · OpenCL absent (linux) (pull_request) Successful in 26s
Details
wai-quantum pulse and dynamics / reader, simulator and pulse jobs under wasm32-wasip2 (wasmtime) (pull_request) Successful in 57s
Details
wai-quantum pulse and dynamics / reader, simulator and pulse jobs · linux, release (pull_request) Successful in 1m24s
Details
wai-sink-android native sink library / every ABI, the AAR, and the instrumented tests in a headless emulator · macos (pull_request) Successful in 18m59s
Details
wai-quantum error correction and mitigation / codes, decoders, texts and mitigation · linux, release (pull_request) Successful in 2m24s
Details
wai-quantum extension points / the registry under wasm32-wasip2 (wasmtime) (pull_request) Successful in 52s
Details
wai-quantum for Python / python · linux (pull_request) Successful in 2m42s
Details
wai-quantum extension points / the registry and the example · linux (pull_request) Successful in 2m27s
Details
wai-quantum-qpu / clients against their contracts (linux) (pull_request) Successful in 42s
Details
wai-quantum matrix-extension member / member · matrix extension, emulated (aarch64 Linux) (pull_request) Successful in 24s
Details
wai-quantum signal processor / processor and member · signal processor, emulated (pull_request) Successful in 14m5s
Details
wai-quantum docs, course and locales / every command and snippet in the docs · linux (pull_request) Successful in 17m36s
Details
wai-quantum studio and desktop / studio · browser (pull_request) Successful in 3m24s
Details
wai-quantum portable tensor program / tensor program · CPU, mutants, GPU builds (pull_request) Successful in 55s
Details
wai-quantum CPU vector units / member · vector unit, rvv 1024-bit (riscv64, emulated) (pull_request) Successful in 22s
Details
wai-quantum service / service · linux (pull_request) Successful in 4m33s
Details
wai-quantum CPU vector units / member · vector unit, sve 128-bit (aarch64, emulated) (pull_request) Successful in 28s
Details
wai-quantum CPU vector units / member · vector unit, rvv 128-bit (riscv64, emulated) (pull_request) Successful in 38s
Details
wai-quantum CPU vector units / member · vector unit, sve 2048-bit (aarch64, emulated) (pull_request) Successful in 10s
Details
wai-quantum CPU vector units / member · vector unit, sve 512-bit (aarch64, emulated) (pull_request) Successful in 10s
Details
wai-quantum tensor-engine member / member · tensor engine, the kernel toolchain's simulator (linux) (pull_request) Successful in 4m57s
Details
wai-quantum CPU vector units / member · vector unit, avx2 (x86_64 silicon) (pull_request) Successful in 20s
Details
wai-quantum variational and algorithm library / parameters, gradients, optimisers, VQE, QAOA and builders · linux, release (pull_request) Successful in 1m32s
Details
wai-quantum verdicts and repairs / the intent set and the verdict under wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m14s
Details
wai-quantum studio and desktop / desktop app · linux (pull_request) Successful in 5m21s
Details
wai-quantum verdicts and repairs / verdicts, repairs and the intent set · linux (pull_request) Successful in 1m53s
Details
wai-quantum WebGPU member / member · software Vulkan (linux) (pull_request) Successful in 2m4s
Details
WAI Studio / the catalogue's actions, the unit tests and the core · linux (pull_request) Successful in 52s
Details
wai-quantum WebGPU member / shader checks · browser build · wasip2 inertness · MSRV (pull_request) Successful in 3m34s
Details
wai-quantum views in agent hosts / views · a scripted host (pull_request) Successful in 3m21s
Details
wai-quantum views in agent hosts / views · the page and its engine (pull_request) Successful in 3m29s
Details
wai-vector vector graphics / wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m13s
Details
wai-vector vector graphics / wasm32 under Node (pull_request) Successful in 30s
Details
wai-vector vector graphics / linux-x86_64 (pull_request) Successful in 2m49s
Details
wai-vector vector graphics / fuzz, peak allocation, comparison count (pull_request) Successful in 25s
Details
wai-web wasm32 / wai-web wasm32 build · corpus, menu and writers (pull_request) Successful in 5m28s
Details
WAI mbt2018_mean integer decode (regenerated vectors) / regenerate mbt2018_mean integer vectors → Rust decode, required (pull_request) Successful in 5m33s
Details
wai-vector vector graphics / wasm32 in three browser engines (pull_request) Successful in 3m43s
Details
wai-vector vector graphics / independent checker (Python) (pull_request) Successful in 4m45s
Details
WAI Studio / Studio in WebKit · linux (pull_request) Successful in 13m9s
Details
wai formal verification (integer core) / kani (isqrt512) (pull_request) Successful in 1h6m5s
Details
standards workspaces build + test / jouleclaw-rs (-nodebug, jouleclaw/jouleclaw-rs, -p jouleclaw-energy --features rapl,nvml, jouleclaw-rs, linux-arm64, -C target-feature=+fp16) (pull_request) Successful in 4m30s
Details
standards workspaces build + test / aac-rs (aac-conformance, aac/aac-rs, aac-rs, linux-arm64) (pull_request) Successful in 4m34s
Details
standards workspaces build + test / joulecontract-rs (joulecontract/joulecontract-rs, joulecontract-rs, linux-arm64, true) (pull_request) Successful in 1m29s
Details
standards workspaces build + test / map-rs (map-conformance, map/map-rs, map-rs, linux-arm64) (pull_request) Successful in 1m30s
Details
standards workspaces build + test / mesh-rs (mesh/mesh-rs, -p mesh-engine-gguf -p mesh-openai --features mesh-engine-gguf/gguf,mesh-openai/server, mesh-rs, linux-arm64) (pull_request) Successful in 1m14s
Details
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 7m4s
Details
wai cross-architecture byte-equality / linux-aarch64 (pull_request) Successful in 40s
Details
standards workspaces build + test / openpay (openpay, openpay, linux-arm64) (pull_request) Successful in 4m35s
Details
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 32s
Details
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 17m22s
Details
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 14s
Details
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 55s
Details
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 2m16s
Details
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 10m38s
Details
WAI examples / WAI examples · android-app · linux-arm64 (pull_request) Successful in 5m30s
Details
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 11m41s
Details
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h1m16s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Successful in 34m43s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Successful in 35m7s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Successful in 17m37s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Successful in 17m26s
Details
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 5s
Details
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m25s
Details
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 1m23s
Details
wai-ops-npu integer operators on neural processors / builds · no device is not a pass (linux-arm64) (pull_request) Successful in 18s
Details
wai-ops integer operators / linux-aarch64 (pull_request) Successful in 1m5s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m53s
Details
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Successful in 34m26s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 23s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m21s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 7m10s
Details
wai-quantum HIP member / member · HIP absent (linux-arm64) (pull_request) Successful in 57s
Details
wai-quantum npu-cores member / member · npu-cores absent (linux-arm64) (pull_request) Successful in 27s
Details
wai-quantum pulse and dynamics / the same bits · linux-arm64 (pull_request) Successful in 1m26s
Details
wai-quantum tensor-engine member / member · tensor engine absent (linux-arm64) (pull_request) Successful in 20s
Details
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Successful in 16m46s
Details
wai-quantum extension points / the registry and the example · linux-arm64 (pull_request) Successful in 2m31s
Details
wai-quantum variational and algorithm library / parameters, gradients, optimisers, VQE, QAOA and builders · linux-arm64, release (pull_request) Successful in 1m43s
Details
wai-sink-android native sink library / the JNI layer and the platform-free half on the host JVM · linux-arm64 (pull_request) Successful in 2m37s
Details
wai-vector vector graphics / linux-aarch64 (pull_request) Successful in 2m41s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!576
No description provided.