graphical way to trace reqvto test results

[avrabe]

Need a way from req ot any artifact linking to a test or so with test results to trace back. Currently works from test to the artifact

[avrabe]

Triage from the issue-fixing routine: intent is clear (close the reverse direction — req → test results, where today only test → artifact resolves graphically) but no explicit "fixed when …" line the routine can verify before opening a PR, so it's deferred until one is added.

The format I look for matches #532's kill-criterion. A useful shape for this one might pin (a) the entry point (CLI command / dashboard view), (b) what counts as a "test result" (verification artifact status? linked CI run? both?), and (c) what the visual produces. Sketch — feel free to revise / re-scope:

## Acceptance Criteria
- [ ] `rivet trace <REQ-ID> --to verification` (or equivalent — name TBD) walks `satisfies`/`verifies` links forward from a requirement through the intermediate artifacts down to every reachable `*-verification` (or `*-test`) artifact, returning the full chain + each leaf's current `status` (and tracker links if #548 lands). Tested via a fixture with a multi-hop chain (req → sw-arch-component → sw-detail-design → unit-verification).
- [ ] The dashboard's existing artifact-graph view gains a "from this requirement" mode: clicking a `requirement` (or any artifact) renders the downstream subgraph of artifacts reachable via outbound trace links, with verification leaves colored by status (passed / failed / pending / missing). Verified by a Playwright snapshot on the rivet repo's own dashboard.
- [ ] Static-export equivalent: the per-requirement page in `rivet export --format html` includes the same downstream subgraph (inlined SVG, no client JS — same posture as the AADL inline-at-export plan in #468). Golden-file test on a fixture export.
- [ ] When a requirement has zero downstream verifications, the view shows that explicitly (an empty "no test results" panel, not a blank graph) — distinguishes "untested" from "view broken".
- [ ] `rivet validate` PASS unchanged; `cargo test` / `cargo fmt --check` / `clippy --all-targets -- -D warnings` clean.
- [ ] Commit trailers: `Implements: REQ-NNN` (file a new REQ for "requirement → verification downstream trace") + `Refs: #547`. If the dashboard surface lands, add `Refs: FEAT-001`.
- [ ] **Explicitly out of scope (file separately):** linking to live CI run results from the verification page (that's the #548 tracker-link surface — keep this issue scoped to the artifact graph); auto-suggesting missing verifications for a requirement (that's the #350 scaffold-verification ask).

Process side-rail (carried from every recent triage thread): https://pulseengine.eu/blog/ is still HTTP 503 (long-standing site-infra symptom flagged on #420, #468, #456, #436, #431, #422, #479, #482, #488, #490, #500, #508, #509, #516, #522, #523, #530, #532, #538, #543 — re-verified at the start of this run). The binding workflow guidance can't be consulted, so no PR will land from this triage regardless. Comment is the AC ask only.

Not implemented this run.

---

Generated by Claude Code — issue-triage agent run 2026-06-19.

---

Generated by Claude Code

[avrabe]

Triage (scheduled run): one-line body, no acceptance criteria — not implementable as written. Holding.

Useful shape questions before AC:

• Is the "graphical way" a new dashboard view in rivet serve, an export (e.g. HTML compliance report), a Mermaid emission, or something the LSP renders?
• Direction = req → test (forward closure). The graph traversal is already in rivet trace / rivet coverage — is the gap the rendering or the traversal (e.g. req → ... → test-result)?
• Acceptance criterion = "I can click REQ-N and see a tree out to passing/failing tests"? Or "I can export a PNG/SVG for the compliance report"?

Example AC:

## Acceptance Criteria
- [ ] `rivet serve` dashboard: opening a requirement artifact shows a forward-trace graph (req → verification → test-result) rendered as Mermaid or SVG
- [ ] Each test node shows last status (pass/fail/skipped/unrun) from the most recent `rivet import-results` run
- [ ] Export path: `rivet export --format html` includes the same graph inline as static SVG (no `rivet serve` required) — same approach as the AADL fix in #468
- [ ] One Playwright regression test covers click-to-graph on a fixture project

— rivet triage (Claude Code, scheduled)

---

Generated by Claude Code