chore(deps): bump pulseengine/rivet from 0.34.0 to 0.35.0

[dependabot]

Bumps pulseengine/rivet from 0.34.0 to 0.35.0.

Release notes

Sourced from pulseengine/rivet's releases.

Rivet v0.35.0

What's Changed

• plan(v0.35): REQ-308 — verify advances on evidence existence, not sufficiency (#838) by @​avrabe in pulseengine/rivet#840
• fix(render): raise the serve/export palette to WCAG AA (REQ-276) by @​avrabe in pulseengine/rivet#842
• feat(serve,export): render the test-result trace as a fold/expand tree (REQ-274) by @​avrabe in pulseengine/rivet#843
• fix(coverage): a declared-exempt source leaves the denominator (REQ-309, #848) by @​avrabe in pulseengine/rivet#850
• feat(serve): server-rendered tag facet over the tags param (REQ-275) by @​avrabe in pulseengine/rivet#851
• ci: move CI Gate and the zola smoke off GitHub-hosted runners by @​avrabe in pulseengine/rivet#855
• fix(validate): report cross-refs as NOT CHECKED when externals fail to load (REQ-312, #854) by @​avrabe in pulseengine/rivet#857
• feat(validate,export): declared-blocked acceptance criteria (REQ-313, #856) by @​avrabe in pulseengine/rivet#858
• fix(explain): derive the allowed-source set instead of printing [] (REQ-310, #852) by @​avrabe in pulseengine/rivet#859
• feat(sync): --locked checks out the commits recorded in rivet.lock (REQ-311, #853) by @​avrabe in pulseengine/rivet#861
• ci: make the Test and Proptest jobs do what their names say (REQ-304, REQ-305) by @​avrabe in pulseengine/rivet#863
• fix(proofs): Kani proof CoverageEntry init missing exempt/exempt_ids (REQ-309, #848) by @​avrabe in pulseengine/rivet#865
• fix(serve): truncation signal on /api/v1/artifacts and /api/v1/diagnostics (REQ-303, #832) by @​avrabe in pulseengine/rivet#864
• plan(v0.35): cut what shipped, split the remainder by @​avrabe in pulseengine/rivet#866
• plan(v0.36): triage the untracked issue board; give v0.36.0 a theme by @​avrabe in pulseengine/rivet#869
• chore(release): v0.35.0 — the friction round by @​avrabe in pulseengine/rivet#868

Full Changelog: pulseengine/rivet@v0.34.0...v0.35.0

Changelog

Sourced from pulseengine/rivet's changelog.

[0.35.0] - 2026-08-27

The friction round. Every issue a human reported this cycle is fixed here — #832, #833, #835, #848, #852, #853, #854, #856 — alongside the three customer-requested dashboard changes.

Added

• rivet sync --locked (REQ-311, #853) — check out the exact commits recorded in rivet.lock instead of each external's ref: head. rivet lock wrote pins that sync never read, so a consumer's committed lock pinned for provenance while its federated CI validated against whatever the sibling repos' heads happened to be: a force-push, artifact rename or bad commit silently changed what CI saw, and a run could not be reproduced later. Mirroring cargo, --locked never updates the lock and fails rather than floating when it cannot honour it — a missing lockfile or an unpinned external are both hard errors. Each resolved commit is printed so a CI log records what was actually validated.
• rivet context --stdout / --brief (REQ-297, #811) — read project state without mutating the working tree.
• Declared-blocked acceptance criteria (REQ-313, #856) — an acceptance-criteria entry may be a mapping (text / status / blocked-by) as well as a bare string, so a criterion an author knows is not yet dischargeable has somewhere to live other than shouty caps inside the string. A criterion blocked-by the release its own artifact is scoped to is a deadlock and is now an error: the release cannot be cut until the artifact verifies, and the artifact cannot verify until that release ships.

Fixed

• Declared incompleteness scored as an oversight (REQ-309, #848) — a safety goal carrying GSN's undeveloped: true counted identically to a goal someone forgot. The schema's own rule description already promised the exemption ("unless marked undeveloped") while undeveloped appeared in no Rust file. A traceability rule may now name an exempting boolean field via exempt-when-field; an exempt source leaves the denominator and is reported as its own named count. A forgotten goal moves the figure 100% → 50%, where it is loud, instead of hiding among declared gaps.
• validate --explain reported from one of [] (REQ-310, #852) for a rule that is satisfiable — which reads as "no type may source this link" and sent the reporter toward filing a schema gap that did not exist. The source set is now derived from the types that declare the ability to source the link, and a rule nothing can satisfy says so explicitly.
• A dead externals path reported 0 broken cross-refs (REQ-312, #854). When external loading fails, cross-ref resolution never runs — and a zero read as "the cross-repo graph is clean" when it meant "the graph was never checked". On the reporting project that hid 12 genuine dangling refs behind 38 phantom errors. The summary now says cross-refs NOT CHECKED.
• Overlapping sources collided every id with itself (REQ-302, #746) — 184 phantom errors masked 6 real ones. Sources are deduped at load; diagnostic order is now total, so report diffing between baselines works.
• check verification-evidence was blind to nested workspaces (REQ-236,

... (truncated)

Commits

• 4ff980e chore(release): v0.35.0 — the friction round (#868)
• 9d9a697 plan(v0.36): triage the untracked issue board; give v0.36.0 a theme (#869)
• fe18f29 plan(v0.35): cut what shipped, split the remainder (#866)
• 679d612 fix(serve): truncation signal on /api/v1/artifacts (REQ-303, #832) (#864)
• fa387cc fix(proofs): Kani CoverageEntry init missing exempt/exempt_ids (REQ-309, #848...
• 2ddb0b3 ci: make the Test and Proptest jobs do what their names say (REQ-304, REQ-305...
• 83c7d91 feat(sync): --locked checks out the commits recorded in rivet.lock (REQ-311, ...
• 99f3b8b fix(explain): derive the allowed-source set instead of printing [] (REQ-310, ...
• e08b3d0 feat(validate,export): declared-blocked acceptance criteria (REQ-313, #856) (...
• e569bf2 fix(validate): report cross-refs as NOT CHECKED when externals fail to load (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🔒 HELD — not auto-mergeable (class: zerox-minor). 0.34.0 -> 0.35.0: for a 0.x crate the MINOR is the de-facto major (ordeal 0.9->0.12; object 0.39->0.40 / #938)

Auto-merge has been actively disabled and asserted off by the hold gate (#965). For a 0.x crate the MINOR component is the de-facto major (and for 0.0.x, the patch): ordeal 0.9→0.12 auto-merged as "minor" and hung Test+Z3 for days; object 0.39→0.40 (#938) broke 16 call sites across three unrelated newtype surfaces. Merge this BY HAND only once the FULL suite is green, including the separate --features z3-solver path (required context "Z3 Verification") — the discriminator is CI, not a read of the diff.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[avrabe]

[maintainer loop] Held-state audit — recording measured status so this hold is not silent.

pulseengine/rivet action 0.34.0 -> 0.35.0 · classifier: ``

All 9 required contexts are GREEN on this PR. The only red is
Rivet Federated Graph (advisory), which was failing repo-wide from
2026-09-03 04:00–21:25 because GitHub rate-limits anonymous clones from
datacenter IPs — nothing to do with this bump. Diagnosed and fixed in #1143/#1144.

So this is held by policy, not by evidence of breakage. The policy
(SYNTH-DEPENDABOT-MINORHOLD-ENFORCED-965) treats a 0.x minor as a de-facto
major, because for a 0.x crate it is one — earned from ordeal 0.9 -> 0.12,
which auto-merged as "minor" and hung Test/Z3 for 4–6 hours per run for
days.

Why you are being told this rather than left to rot. A held PR currently has
no defined exit: it cannot auto-merge, and nothing prompts a human. Four of
these accumulated since 2026-08-31 — one (#1111, wasmparser) was genuinely
source-breaking and is closed with that evidence; the rest were reporting a CI
outage, not an incompatibility. A hold that is correct and silent is how they
became invisible, and I described their state wrongly in the org review as a
result. Raised for temper in #1132.

Staying held pending a deliberate decision, not forgotten. If you want it taken,
say so on this PR.