Enforce rivet-validate as required pre-commit hook wherever rivet.yaml exists

[avrabe]

Part of the V&V coverage initiative.

Problem

13 pulseengine repos ship a rivet.yaml traceability artifact, but only a subset gate rivet validate at pre-commit (loom, rivet, synth do; relay, sigil, gale, wohl do not). This means traceability drift can land on main before any gate catches it — undermining the whole traceability story.

Acceptance

• Audit every repo for rivet.yaml presence vs. rivet-validate hook presence. Produce a gap list (output: issue comment or docs/adoption-status.md).
• For each gap, open an adoption issue on the target repo pointing back here.
• Add a rivet-validate hook to rivet's canonical pre-commit template (Tier 1).
• Provide a rivet install path that CI and pre-commit can both use (binary release? cargo install rivet?)
• Document failure mode: when rivet validate fails, the commit is blocked with a clear message pointing at the broken link.
• Optional: pre-commit hook version-pins rivet to avoid drift between developer setups.

Notes

• Parent template issue: coordinate with canonical-template issue
• Document that adoption is not automatic — every adopter makes a deliberate choice
• This directly addresses the DO-178C / ISO 26262 traceability objective

[avrabe]

Triage: this issue has acceptance criteria, but several bullets require write access to other org repos:

• "Audit every repo for rivet.yaml presence vs. hook presence" — needs read access to relay/sigil/gale/wohl, fine if public.
• "For each gap, open an adoption issue on the target repo pointing back here" — automated agents in this workflow are scoped to pulseengine/rivet only; cross-repo issue creation has to be done from a session with broader scope (or by hand).
• "Add a rivet-validate hook to rivet's canonical pre-commit template (Tier 1)" — in scope here. This belongs in Canonicalize 21-hook pre-commit template for adoption across production repos #186 anyway.
• "Provide a rivet install path that CI and pre-commit can both use" — in scope, but big enough to deserve its own sub-issue (binary release vs. cargo install vs. pre-commit additional_dependencies).
• Documentation of failure mode — in scope.

Proposed split:

1. Sub-issue: write the audit (CI job + report). Acceptance = audit script lands in scripts/, runs in CI, output committed to docs/adoption-status.md.
2. Sub-issue: pin a rivet install recipe. Acceptance = one canonical method (probably additional_dependencies: [rivet@<ver>] in pre-commit) works on a clean machine.
3. Cross-repo adoption issues: filed by hand or by a session scoped to those repos.

Confirm and I can take the in-scope sub-issues.

---

Generated by Claude Code