[OpenSpec] [mydash] dashboards

[rubenvdlinde]

Hydra validation tracker — dashboards capability

Spec: openspec/specs/dashboards/spec.md (10 REQs)

Tracks Hydra's re-run of this capability against the current code as a validation exercise. Created as part of the per-spec issue sweep on 2026-04-24 so every spec in openspec/specs/ has a 1:1 tracking issue (see companion #24 for the retrofit-created legacy-widget-bridge).

What Hydra should do (when triggered)

Read the 10 REQs and re-implement them against the existing code. Expected outcome: minimal diff — existing code should already match the spec. Any meaningful diff is a signal:

• REQ language under-specifies observed behaviour
• Spec references code-conventions the builder doesn't know about (repo-specific ADRs not captured)
• Implementation has drifted from spec since the spec was written

Current blockers

Hydra's builder expects a openspec/changes/<name>/tasks.md to drive work. This spec has no active change — all current REQs are the archived state. Before adding ready-to-build, one of:

• Create a validate-dashboards change that copies each REQ into tasks.md as unchecked items, so the builder has a clear work list
• Or let a /opsx-annotate pass populate the Bucket 1 annotations and treat that as the validation (skip Hydra)

To trigger Hydra

1. Create the validation change (see above)
2. Run python3 concurrentie-analyse/scripts/sync_spec_content.py mydash to sync Specter
3. Add ready-to-build to this issue — Hydra supervisor picks it up on the next tick
4. Observe resulting PR — any diff is a finding

Reference

• Hydra docs: hydra/CLAUDE.md
• Companion issues (per-spec): [OpenSpec] [mydash] retrofit-legacy-widget-bridge #24 (legacy-widget-bridge, retrofit)
• Sibling repo: [OpenSpec] [app-versions] version-management app-versions#16