site: close the loop between capability pages and inspectable proof

[masarray]

R6.1 — Proof Surface Flow

Builds on the R6 homepage evidence routing already merged in #364.

Stable rollback point

checkpoint/site-r6-evidence-routing-2026-09-22
→ 32d4809b9705c56d50f957271fc0ea5521475558

What this changes

Compatibility Evidence

• Makes the service matrix the primary action instead of sending technical evaluators back to Quick Start.
• Keeps claim governance one click away.
• Connects field profile A directly to the file-service/fault-record workflow.
• Connects field profile B directly to the RCB/SCL workflow.
• Preserves the existing public GitHub engineering records and machine-readable registry.

Technical Review

• Replaces generic hero actions (troubleshooting/About) with evaluator-first routes:
  • field interoperability evidence,
  • exact stable-release verification.
• Troubleshooting remains available as a quiet tertiary path.

Capability pages

• Extends the shared Evidence Contract so core EN/ID capability pages link to both:
  • bounded field interoperability evidence,
  • engineering/claim boundaries.

Resulting review graph

Homepage evidence → service matrix → public field record → capability workflow → field evidence / technical boundary.

The flow is intentionally bidirectional so evaluators do not hit a dead end after reading either a marketing surface or a protocol-detail page.

Regression protection

Source, rendered-site and adoption/field-proof validators now require these evaluator routes.

Scope

Website templates/partials and validators only. No IEC 61850 runtime, Smart Discovery, Reporting, GOOSE, file service, SCL engine, control, C#/XAML or ARIEC61850 behavior is changed.