Expose Hermes Switchyard routing status and document the support lifecycle

Parent Epic: #7937

## Outcome

Users can intentionally configure, inspect, operate, and troubleshoot supported Hermes routing without reading sandbox internals or exposing secrets.

## Scope

- Add explicit enable/disable configuration and one supported random/classifier preset or expert configuration path.
- Show whether routing is requested, active, disabled, degraded, or failed.
- Show non-secret versions, router, semantic targets, selected target/model, and route reason/tier.
- Surface latency, TTFT, tokens, and cost only where upstream provides a stable contract.
- Document supported versions/routers, configuration ownership, provider setup, enable/disable, upgrade, rollback, limitations, and troubleshooting.
- Keep benchmark-backed model/router recipe ownership in #8501.

## Acceptance

- [ ] Status distinguishes configured from actually active routing.
- [ ] Per-turn evidence identifies the selected target/model without revealing credentials or private prompts.
- [ ] Unsupported versions and incomplete configurations produce actionable guidance.
- [ ] Documentation can reproduce setup in a fresh environment using released artifacts.
- [ ] Documentation clearly separates supported platform behavior from benchmarked recipes and experimental routers.