Fleet coverage retrofit: bring mydash to 100% spec coverage

[rubenvdlinde]

Fleet coverage retrofit — mydash

Goal: bring this app to 100% spec coverage per opsx-coverage-scan v1 — every lib/ method either carries @spec openspec/changes/.../tasks.md#task-N or is classified as plumbing; Buckets 2/3 drain to zero; Bucket 4 ADR findings clear.

Baseline (generated 2026-05-24): see openspec/coverage-report.md on this repo for the full report.

annotated	plumbing-or-other	Bucket 1 (matched)	Bucket 2a (cap, no REQ)	Bucket 2b (no cap)	Bucket 3a (broken)	Bucket 3b (unimpl)	Bucket 4 (ADR)
29 files	—	112	4 / 2 clusters	3 / 1 clusters	0	23	0 findings / 5 rules

Fleet roll-up: apps-extra/COVERAGE-FLEET.md in hydra (and your local checkout).

---

Phase 0 — Foundation cleanup

• Decide canonical @SPEC format (currently 26 files use shorthand @spec dashboards:REQ-DASH-003, 3 files use canonical @spec openspec/changes/.../tasks.md#task-N)
• Fix orphan @SPEC tag in ManifestController referencing non-existent spec manifest-v2-runtime

Phase 1 — REQ-ID format normalization

• Audit openspec/specs/**/spec.md — adopt canonical ### Requirement: <title> format if not already
• Migrate any non-canonical REQ headings (shorthand, plain bullets, ID-in-title) to canonical form

Phase 2 — Bucket 1 annotation sweep (112 methods)

• Run /opsx-annotate mydash → ghost change retrofit-YYYY-MM-DD-annotate-mydash → PR
• Reviewer + applier pass on the resulting PR

Phase 3 — Reverse-spec for Bucket 2 (7 methods, 3 clusters)

• Run /opsx-reverse-spec mydash --extend <cap> per Bucket 2a cluster (bias toward --extend per skill guidance)
• Run /opsx-reverse-spec mydash --cluster <name> per Bucket 2b cluster, after pre-splitting any namespace-word labels

Phase 4 — Bucket 3 triage (0 + 23 entries)

• 3a: open fix PR for each (REQ has evidence in removed git lines — implementation is possibly broken/removed)
• 3b: for each, decide implement / defer (mark status: deferred in spec) / archive

Phase 5 — Bucket 4 ADR conformance (0 findings across 5 rules)

• Sweep via hydra-gate-spdx autofix for license/copyright/SPDX gaps
• i18n-wrap any hardcoded user-facing strings
• Case-by-case review of direct-SQL findings (some may be justified cross-schema ops)
• Verify file-docblock @spec tags follow Phase 2 annotation

Phase 6 — Verify

• Re-run /opsx-coverage-scan mydash — verify Bucket 1 + plumbing + annotated == total methods; Buckets 2/3 == 0
• Close this issue when the re-scan summary is clean

---

References

• Fleet roll-up: apps-extra/COVERAGE-FLEET.md
• Skill: hydra/.claude/skills/opsx-coverage-scan/SKILL.md
• This app's full coverage report: openspec/coverage-report.md

Tracking issue created by Claude on behalf of @rubenvdlinde as part of the 2026-05-24 fleet coverage audit.