Setting up your dashboard0 entities found · 9/32 branches scanned
ID:WORK-384Status:ready
Typed page entities
SPEC-092 Layers 2 + 3 — let a page declare a registry type so collection/ aggregate can query it by domain (collection type="rune"), not just type:page.
A page with frontmatter type (and optional id) registers as that entity type in addition to its page registration; id defaults to the page URL. Duplicate (type, id) at site scope warns (as page/heading already do).
No parallel config block. The url-pattern → type rule reuses routeRules: add an optional entity field (it already maps a pattern → {layout}; now {layout, entity}). Frontmatter type overrides the rule. This deliberately avoids confusion with the inverse entityRoutes (entity → page, SPEC-069).
Acceptance Criteria
Frontmatter type (+ optional id) registers a typed entity alongside page, with the reserved-filtered frontmatter as data; explicit id honoured, else URL.
routeRules accepts an optional entity field mapping a url pattern → type; frontmatter type overrides; unmatched pages stay page-only.