[dashboard-language] Built-in pages: conservative required-source validation

Milestone

Built-in pages

Shipped in this increment

Implemented a conservative Section 10 validation slice for built-in pages:

DLS-PAGE-002 overview built-in page required-source validation
DLS-PAGE-006 runs built-in page required-source validation

Changes:

added a built-in page required-source catalog in pages/dashboard/src/specification.js
updated pages/dashboard/src/validator.js to reject overview and runs built-in pages until declarative built-in definitions exist for the required logical sources
added unit coverage in pages/dashboard/test/unit/validator.test.js that names the missing required sources and asserts DLS-E003
updated pages/dashboard/PLAN.md with the completed slice, blockers, and next step

Specification coverage

Section 10 Built-in Pages
Requirement identifiers: DLS-PAGE-002, DLS-PAGE-006

Quality gates

Ran from pages/dashboard/:

npm install ✅
./node_modules/.bin/tsc -p tsconfig.json --noEmit ✅
./node_modules/.bin/eslint . ✅
./node_modules/.bin/vitest run --environment jsdom ✅
npm run test:e2e ⚠️ blocked by environment/tooling mismatch: Playwright Test did not expect test() to be called here

Blockers

Section 10 requires built-in pages to be expressed as declarative page definitions built from custom-view primitives, but the specification does not currently define YAML vocabulary for embedding those definitions alongside kind: built-in / page.
End-to-end Playwright package execution remains blocked in this environment by the runner mismatch above. Per the workflow instructions, the built-in Playwright MCP browser tools should be preferred until the package harness is aligned.

Next milestone

Built-in pages: define and validate a concrete declarative vocabulary for built-in page definitions once the Section 10 specification ambiguity is resolved.

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