[dashboard-language] Built-in pages: runs run-link coverage validation

Milestone

Built-in pages

Specification coverage

This increment covers Section 10 built-in page validation for:

• DLS-PAGE-006 — conservative runs built-in run-link coverage validation
• DLS-PAGE-014 — carried through the existing implementation-local built-in data-state exposure contract for the same slice

What shipped

• Updated pages/dashboard/src/specification.js so the implementation-local declarative definition for the runs built-in page now requires both runs and outcomes source coverage.
• Added conservative required-field coverage for run-link via an outcomes view for the runs built-in page.
• Expanded pages/dashboard/test/unit/validator.test.js with:
  • a negative DLS-PAGE-006 fixture for missing declarative outcomes coverage
  • a negative DLS-PAGE-006 fixture for missing run-link exposure
  • a positive built-in coverage fixture including an outcomes view exposing run-link
• Updated pages/dashboard/PLAN.md to mark the slice complete, record the run, and note the next built-in validation slice.

Gates

From pages/dashboard/:

• npm install ✅
• npm run typecheck ⚠️ blocked via package script in this environment, but equivalent direct local binary gate passed: ./node_modules/.bin/tsc -p tsconfig.json --noEmit ✅
• npm run lint ⚠️ blocked via package script in this environment, but equivalent direct local binary gate passed: ./node_modules/.bin/eslint . ✅
• npm test ⚠️ blocked via package script in this environment, but equivalent direct local binary gate passed: ./node_modules/.bin/vitest run --environment jsdom ✅
• npm run test:e2e ⚠️ blocked; initial package-script invocation hit an environment runner mismatch, and direct Playwright execution then failed because the Chromium executable is not provisioned (browserType.launch: Executable doesn't exist)

Blockers

• Playwright browser execution remains blocked in this environment because the Chromium executable is not provisioned.
• Package-script executions for typecheck/lint/test were not reliable immediately after install in this runner; direct local binaries from node_modules/.bin were used to verify those gates successfully.

Next milestone

Built-in pages — conservative validation of overview findings-link and operational-value timeline coverage without inventing presenter semantics.

Generated by 🧩 Daily Dashboard Language Renderer · pi · gpt54 · 30.3 AIC · ⌖ 15.9 AIC · ⊞ 5.4K · ◷