[dashboard-language] Built-in pages required-source coverage

Milestone

Built-in pages

What shipped

• Extended the conservative Section 10 built-in-page validator so every canonical built-in page now rejects missing declarative built-in definitions for each required logical source.
• Kept the implementation aligned with the recorded specification ambiguity: until the specification defines where declarative built-in definitions live, built-in pages fail with explicit per-source DLS-E003 errors instead of inventing unsupported YAML semantics.
• Expanded unit coverage for built-in pages across organizations, repositories, workflows, experiments, graders, evals, usage, engines-models, operational-value, and findings.

Specification coverage

• Section 10 Built-in Pages
• Requirement identifiers: DLS-PAGE-003, DLS-PAGE-004, DLS-PAGE-005, DLS-PAGE-007, DLS-PAGE-008, DLS-PAGE-009, DLS-PAGE-010, DLS-PAGE-011, DLS-PAGE-012, DLS-PAGE-013, DLS-PAGE-014
• Regression coverage kept for DLS-PAGE-001, DLS-PAGE-002, and DLS-PAGE-006

Verification

• npm install ✅
• npm run typecheck ✅
• npm run lint ✅
• npm test ✅
• npm run test:e2e ⚠️ blocked by infrastructure: Playwright Chromium executable is not provisioned in this environment (browserType.launch: Executable doesn't exist)

Blockers

• End-to-end Playwright tests could not run to completion because the required Chromium executable is missing in the runner environment.

Next milestone

Built-in pages — define and validate a concrete declarative built-in page-definition vocabulary once the Section 10/Section 4 YAML-shape ambiguity is resolved.

Generated by 🧩 Daily Dashboard Language Renderer · pi · gpt54 · 26.8 AIC · ⌖ 5.77 AIC · ⊞ 5.2K · ◷