| Filename | Latest commit message | Latest commit date |
|---|---|---|
a63d788046
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 15s
repository checks / lockfiles, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 1m44s
standards workspaces build + test / jcp-rs (jcp-conformance, jcp/jcp-rs, -p jcp-energy --features nvml, jcp-rs, linux) (pull_request) Successful in 1m37s
standards workspaces build + test / joule-ui-rs (joule-ui/joule-ui-rs, joule-ui-rs, linux) (pull_request) Successful in 1m12s
standards workspaces build + test / joulehook-rs (joulehook/joulehook-rs, joulehook-rs, linux) (pull_request) Successful in 1m12s
standards workspaces build + test / sandbox-rs (sandbox-conformance, sandbox/sandbox-rs, sandbox-rs, linux) (pull_request) Successful in 2m49s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 9m48s
standards workspaces build + test / jouledesk-rs (jouledesk/jouledesk-rs, jouledesk-rs, macos) (pull_request) Successful in 3m44s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 3m1s
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 2m20s
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 4m55s
`check-spec-refs` caught a dangling citation in the previous commit: `LocalToolGate::resume` cited "SPEC §3.3's 'over budget is deny'", but §3.3 is JouleHook's section. A citation in a jcp crate resolves against `jcp/SPEC.md`, which defines no §3.3 — that binding rule is exactly what the check exists to enforce, and it fired on its author. The rule this method implements is jcp's own: §8.1, "The receipt stream is the write-ahead log (REQUIRED)" — an enforcement point that crashes rebuilds its budget state by replaying its own verified receipt stream. That is what `resume` does, and it is the same section `Bridge::restore`, `Runtime::restore` and `Gateway::resume` already cite. The JouleHook consequence is still described, without a bare §-citation that would bind to the wrong standard; the rule is cited where it lives, in `joulehook-hook`. Co-Authored-By: Claude Opus 5 <[email protected]> |
||
| .. | ||
| jcp-a2a | ||
| jcp-action-receipt | ||
| jcp-bridge | ||
| jcp-channel | ||
| jcp-cite | ||
| jcp-cli | ||
| jcp-conformance | ||
| jcp-efficiency | ||
| jcp-energy | ||
| jcp-flow | ||
| jcp-gateway | ||
| jcp-grant | ||
| jcp-intercept | ||
| jcp-orchestrate | ||
| jcp-policy | ||
| jcp-prompt | ||
| jcp-receipt | ||
| jcp-runtime | ||
| jcp-schema | ||
| jcp-threshold | ||
| jcp-trace | ||
| jcp-wire | ||
| jcp-x402 | ||