| Filename | Latest commit message | Latest commit date |
|---|---|---|
faf2d76f52
All checks were successful
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 4s
no-vanity-metrics / WAI public text names no comparison (pull_request) Successful in 4s
no-vanity-metrics / WAI public text names no company or product (pull_request) Successful in 4s
standards workspaces build + test / arl-rs (pull_request) Successful in 1m7s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m55s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m27s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m7s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m13s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m16s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m12s
standards workspaces build + test / sense-rs (pull_request) Successful in 1m10s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m39s
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 34m16s
standards workspaces build + test / aac-rs (pull_request) Successful in 9m18s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 6m37s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 3m44s
standards workspaces build + test / map-rs (pull_request) Successful in 4m5s
standards workspaces build + test / mesh-rs (pull_request) Successful in 3m31s
standards workspaces build + test / openpay (pull_request) Successful in 16m2s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 8m41s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 8m6s
`standards workspaces build + test / mesh-rs` failed on this branch: adding `delivered_fidelity` to `ServeOutcome` reached seven places in mesh, and I updated five. The two I missed are both in `mesh-engine-gguf`, inside `#[cfg(feature = "gguf")]`, so no default build on this machine compiles them — only the matrix entry's `feature_tests: -p mesh-engine-gguf --features gguf` does, which is why CI found it and local verification did not. Both engines decode greedily from whatever model was loaded and form no after-the-fact view of what they delivered, so they report `None`: the field's documented historical shape, skipped on the wire, with `fidelity_met` falling back to the advertised rating. That is exactly where these engines already stood, so this is the absence-as-tag doing its job rather than a new claim. Checked every other feature in the workspace for the same blind spot — `mesh-core`/`mesh-meter --features hw-meter`, `mesh-openai --features server`, `mesh-engine-gguf --features metal` and `--features rayon` — and `gguf` was the only one broken. The workspace's tests pass, and so do the gguf feature tests as CI runs them. Co-Authored-By: Claude Opus 5 <[email protected]> |
||
| .. | ||
| crates | ||
| Cargo.lock | ||
| Cargo.toml | ||