Fix SV-WOHL verification artifact ID collision

[avrabe]

Problem

artifacts/verification/SV-WOHL-001.yaml was a bundle declaring five sw-verification artifacts as SV-WOHL-001..005. But SV-WOHL-002.yaml…008.yaml are separate sys-verification artifacts. IDs SV-WOHL-002..005 were each declared twice — by two unrelated artifact families colliding on the same ID range.

rivet validate (v0.12.0) reports these as 4 errors. Earlier wohl CI runs used rivet v0.10.0, which did not flag duplicate IDs — CI rebuilds rivet-cli from the unpinned rivet sibling each run, and the tool got stricter. The bug itself is pre-existing; it was just invisible until the tool caught up.

Fix

Re-prefix by verification kind (architect's decision):

• sys-verification artifacts keep SV-WOHL-* (SV = System Verification).
• The five sw-verification artifacts move to SWV-WOHL-001..005, one file each — matching the one-artifact-per-file convention of the rest of artifacts/verification/. The SV-WOHL-001.yaml bundle is removed.

No cross-references needed updating — nothing links to these IDs; their verifies links point outward to SWREQ-* (unchanged).

Verification

• rivet validate (v0.12.0, same as CI): PASS, 0 errors (down from 4 errors). Remaining warnings are the pre-existing lifecycle-coverage notes shared by every approved requirement.

Related

• This is a concrete instance of the unpinned-sibling fragility tracked in CI follow-ups: matrix split, pinned siblings, cargo-deny, bazel build, nightly long-fuzz #8 — CI behavior changed with zero wohl code change because rivet advanced. Pinning rivet/relay to commit SHAs (per CI follow-ups: matrix split, pinned siblings, cargo-deny, bazel build, nightly long-fuzz #8) would make the gate deterministic.
• Unblocks Design decision: Matter integration via hub bridge (SWARCH-WOHL-006) #15 (the Matter design-decision artifacts) — that PR's rivet-validate failure was caused entirely by this pre-existing collision, not by its own changes.

🤖 Generated with Claude Code