feat(schemas): vv-coverage — repo-status type for V&V technique tracking (#188)

[avrabe]

Refs: #188 (sub-issue #1 of the proposed decomposition in the 2026-04-26 triage comment).

Summary

First in-scope cut at the V&V coverage matrix story (#188). Introduces a single new schema, vv-coverage, with one artifact type, repo-status, designed as the source-of-truth shape consumed by:

• the planned rivet coverage --matrix rendering surface (sub-issue Add document system and improve graph visualization #2 of V&V coverage matrix dashboard via rivet coverage (per-commit, per-repo, per-technique) #188),
• the cross-repo pulseengine V&V coverage matrix aggregator (sub-issue feat: AADL integration — schema, adapter, WASM rendering, architecture dogfood #3 of V&V coverage matrix dashboard via rivet coverage (per-commit, per-repo, per-technique) #188).

Filed as a draft because two follow-up sub-issues (#188 #2 + #3) need to land before this schema has a real consumer. The shape itself is the contract those follow-ups depend on; merging it early gives them a stable target.

Acceptance-criteria mapping (#188 sub-issue #1)

AC bullet (proposed in 2026-04-26 triage comment)	Where it landed
Schema fields for techniques_applied, techniques_gated_in_ci on a repo-level artifact	schemas/vv-coverage.yaml — repo-status.techniques-applied (required, list<string>), repo-status.techniques-gated-in-ci (optional, list<string>)
Schema lints	Embedded in rivet-core/src/embedded.rs; cargo test -p rivet-core --test schema_agent_pipelines exercises every entry in SCHEMA_NAMES
rivet validate clean (no new diagnostics)	Identical to origin/main: 6 errors / 62 warnings, all pre-existing in spar-external
Snapshot of typed shape	9 integration tests in rivet-core/tests/vv_coverage_schema.rs covering required/optional, list-typing, schema name registration, extends: [common]

Out of scope

These bullets from #188 cannot be addressed by this PR and are tracked for follow-ups:

• rivet coverage --matrix CLI surface — sub-issue Add document system and improve graph visualization #2 in the prior triage decomposition. Depends on this schema landing.
• Cross-repo aggregator — sub-issue feat: AADL integration — schema, adapter, WASM rendering, architecture dogfood #3. Depends on this schema and probably on a config file (or the rivet-on-rivet pattern) listing pulseengine repos.
• Published dashboard / GitHub Pages — sub-issue docs: add phase 2.5 features and CLI tests #4.
• Per-standard mapping view — sub-issue feat: client-side AADL diagram rendering via spar WASM #5 (stretch goal).

The agent-pipelines block is intentionally not added; sub-issue #1 is shape-only and the pipeline would have nothing to fire on yet.

Why kebab-case fields

Project convention (tool-name, safety-level, cve-id, mutation-score, etc. across the existing schemas). The original issue body uses techniques_applied; this PR matches the in-tree style. If a hard rename is preferred, say the word and I'll switch.

Verification

• cargo test -p rivet-core --lib — 857 pass
• cargo test -p rivet-core --test vv_coverage_schema — 9 pass (new)
• cargo test -p rivet-core --test schema_agent_pipelines — 5 pass (iterates SCHEMA_NAMES; new entry round-trips)
• cargo test -p rivet-core --test supply_chain_schema — pass (regression sanity for the neighbouring schema)
• cargo fmt --all -- --check — clean
• rivet validate — identical to origin/main: Result: FAIL (6 errors, 62 warnings, 0 broken cross-refs) — same six SPAR-* errors in the external fixture, no new diagnostics

Test plan

• New schema parses + registers in SCHEMA_NAMES
• repo-status declares repo, techniques-applied, techniques-gated-in-ci with the documented required/optional shape
• cargo fmt --check clean, rivet validate baseline unchanged
• CI green
• Maintainer confirms field naming convention (techniques-applied vs techniques_applied)
• Follow-up sub-issues filed for rivet coverage --matrix, aggregator, dashboard

Trailers

Per CLAUDE.md, the commit carries:

Implements: REQ-010
Refs: #188, #184

(Schema change → REQ-010. #184 is the V&V coverage initiative hub.)

---

Generated by Claude Code — issue-triage agent run 2026-04-28.

---

Generated by Claude Code

[github-actions]

📐 Rivet artifact delta

No artifact changes in this PR. Code-only changes (renderer, CLI wiring, tests) don't touch the artifact graph.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!