[dashboard-language] Compliance suite

Milestone

Compliance suite

Specification coverage

• Added machine-readable T-PAGE-001 coverage for DLS-PAGE-001 and retained T-PAGE-001 coverage for DLS-PAGE-014 using the Appendix A presenter fixture.
• Tightened T-LINK-001 checks in src/compliance.js for available finding issue, pull-request, and run associations rendered as concrete anchors with expected labels and href values, but left unit assertions for that stricter slice deferred because the current presenter output does not yet satisfy them.

Files changed

• pages/dashboard/src/compliance.js
• pages/dashboard/test/unit/compliance.test.js
• pages/dashboard/PLAN.md

Gates

• ✅ cd pages/dashboard && npm install
• ✅ cd pages/dashboard && npm run build
• ✅ cd pages/dashboard && npm run typecheck
• ✅ cd pages/dashboard && npm run lint
• ❌ cd pages/dashboard && npm test
  • Current failures are in the compliance suite:
    • pre-existing/deferred DLS-SEM-003 Appendix C expectation
    • stricter T-LINK-001 checks do not yet pass against current presenter output
• ⏭️ Browser coverage not rerun after the failing unit gate.

Blockers

• The compliance suite still has a pre-existing failing DLS-SEM-003 negative-fixture expectation.
• The newly tightened T-LINK-001 smoke checks expose a remaining mismatch between the Appendix A presenter surface and the intended link-coverage assertion.

Next milestone

Compliance suite: resolve the existing DLS-SEM-003 fixture gap or align presenter/fixture behavior for conservative T-LINK-001 coverage, then rerun unit and browser gates.

Generated by 🧩 Daily Dashboard Language Renderer · pi · gpt54 · 50.5 AIC · ⌖ 5.8 AIC · ⊞ 5.9K · ◷