WORK-383
Setting up your dashboard 0 entities found · 9/32 branches scanned
ID:WORK-383Status:ready

Frontmatter indexing on the page entity

SPEC-092 Layer 1 — the small first strike that proves the registry-authoring loop. Core registers every page as a page entity but copies only a fixed frontmatter subset (config.ts register hook). Merge the rest of the page's frontmatter onto the page entity's data so any field is queryable by the field-match grammar (which already normalises arrays).

Priority:highComplexity:simpleMilestone:v0.21.0Source:SPEC-092
claude/v0.21-work-breakdown View source

Criteria completion

Criteria completion: 0 of 3 (0%) checked; tracking started on Jun 11, no incremental history yet0%25%50%75%100%Jun 11Jun 15

Tracking started Jun 11 — check back for trends.

Relationships

Implements 1
Related 3
Branches 3
claude/v0.21-work-breakdown current ready
changeset-release/main doneclaude/work-383-frontmatter-indexing donemain done
History 1
  1. 5a2b530
    Created (ready)by bjornolofandersson

Decisions (locked)

  • Passthrough-minus-reserved, not an allowlist. Reserved (excluded) set: layout, tint-mode, tint-lock, region/regions, seo.
  • The existing curated fields win (title, description, date, order, icon, draft keep their normalised values over a same-named raw value).
  • Arrays pass through unchanged (tags: [a, b] matches member-wise).

Acceptance Criteria

  • Page frontmatter (minus the reserved set) is merged onto the page entity data; curated fields still win; arrays pass through.
  • Filtering/grouping page entities by a frontmatter field (incl. tags) works with no resolver/grammar change — verified with a live collection type="page" filter="tags:…" and an aggregate type="page" group="…".
  • The reserved-key exclusion list is unit-tested (layout/tint plumbing never appears in query data).

References

  • SPEC-092 · packages/runes/src/config.ts (register hook) · packages/runes/src/field-match.ts