Phase 1 proof case for SPEC-079. Migrates the plan plugin's entity runes (work, bug, spec, decision, milestone) from the legacy slots + structure config shape to the new metaFields + zones + sections model. Lands together with WORK-305 so v0.18 ships the spec end-to-end.
Tracking started Jun 1 — check back for trends.
plugins/plan/src/config.ts rewritten. Each of the five entity runes (Work, Bug, Spec, Decision, Milestone) replaces its slots: [...entitySlots] + structure: { … } block with:
metaFields declaring each field's metaType, metaRank, label, condition, tag (for <time> etc.), and sentimentMap where applicable.zones.eyebrow = { left: ['id'], right: ['status'] } for the primary header.zones.metadata = { fields: [...] } for the descriptive header (priority, complexity, assignee, milestone, source, created, modified, tags — varies per entity type).sections.title, sections.blurb, sections.body retained as today.entitySlots constant deleted. The slots: [...entitySlots] array is no longer needed (engine derives render order from the canonical vocabulary).
Per-entity field shapes mirror today's behaviour.
sentimentMap values preserved verbatim from today's config.plugins/plan/src/index.ts theme.runes entry updated. The exported theme config for the plugin reflects the new shape. Existing per-rune CSS (work.css, bug.css, etc.) inspected for selectors that referenced the old class names (__header-primary, __header-secondary); rewritten to the new zone-named selectors (__eyebrow, __metadata).
Rune-specific CSS quirks preserved. Complexity dots on work ([data-complexity="…"] > .rf-work__metadata > .rf-work__complexity dd::after) continue to render correctly under the new DOM. Assignee @ prefix preserved. Body section dividers untouched.
Plan-site rendering passes. All existing plan-site snapshot tests in packages/content/test/plan-site-dogfood-real.test.ts pass with the new DOM shape (zone-named classes, def-list metadata). Visual QA on a representative work / bug / decision / spec / milestone page in the rendered plan site.
Backwards-compat shim NOT exercised by plan plugin itself. Plan plugin is fully migrated; the shim only catches third-party consumers (which the plan plugin is not). Verify via the shim's first-encounter warning — it should not fire for any plan rune.
Plan plugin tests updated. Tests in plugins/plan/test/ that snapshot rune output reflect the new DOM. Scanner tests untouched (they read frontmatter / rune attributes, not output DOM).
Docs. Plan-rune doc pages (site/content/runes/plan/{spec,work,bug,decision,milestone}.md) updated:
__header-primary etc. updated to __eyebrow / __metadata.Mechanical config rewrite + selective CSS adjustment. The work splits into per-entity passes that can land as small commits:
name as id, integrates with WORK-281 progress rollup).Each pass is small enough to review independently. CSS sweep follows the config migration (rename class selectors). Snapshot tests get regenerated last after all five entities migrate.
checkedCount / totalCount on milestone entities.Completed: 2026-06-01
Branch: claude/spec-079-implementation (same branch as WORK-305 — Phase 1 lands together).
Plan plugin config (plugins/plan/src/config.ts):
slots: [...entitySlots] + structure: { 'header-primary': …, 'header-secondary': … } to SPEC-079 metaFields + zones + contentSlots.{ left: ['id'], right: ['status'] } for all entities (Milestone uses name as id). Metadata zone declared with the appropriate field list per entity.entitySlots constant removed — engine derives render order from canonical vocabulary (eyebrow → title → blurb → metadata → body).projection: preambleProjection removed — engine auto-derives the .rf-{block}__preamble wrapper around header positions.editHints collapsed to { body: 'none' } — per-field hints ('id-badge': 'none' etc.) no longer needed since the engine derives row identity from data-field.sentimentMap values preserved verbatim from the old config.Per-rune CSS (packages/lumina/styles/runes/):
work.css, bug.css, spec.css, decision.css, milestone.css — renamed __header-primary / __header-secondary selectors to __eyebrow / __metadata. Layout geometry comes from [data-zone-layout=…] selectors (universal), so per-rune CSS now carries only spacing and rune-specific quirks..rf-work__metadata [data-field="complexity"] dd::after (with content driven by [data-complexity=…] on the work root). Assignee @ prefix targets [data-field="assignee"] dd::before.Tests + docs:
packages/content/test/plan-site-dogfood-real.test.ts, plan-site-dogfood.test.ts) pass with the new DOM shape — the snapshots re-derive from the live config so the rename rides along.plugins/plan/test/{work,bug,spec,decision,milestone,plan-config}.test.ts) all pass — they read frontmatter / rune attributes, not output DOM.site/content/runes/plan/{work,bug,spec,decision,milestone}.md) have no __header-primary / __header-secondary references — nothing to update there.warnLegacySlots first-encounter warning doesn't fire for any plan rune (it only triggers when a rune has config.slots + config.structure AND legacy slot names, neither of which the plan plugin sets anymore).metaFields entry. The engine reads the value via the existing modifier-from-meta machinery and renders it via the new layout primitives. No data-flow changes; only the rendering shape moved from plugin to theme.name instead of id — the milestone rune's identifier modifier is name (not id), so its metaFields.name = idField and zones.eyebrow.left = ['name']. The rendered DOM is identical to other entities (left slot = monospace identifier, right slot = sentiment-tinted status chip).condition — fields like assignee, milestone, source, created, modified, tags use condition to render only when the corresponding modifier has a value. Same conditional-rendering semantics as the legacy structure[…].condition field.contracts/structures.json (main site) and packages/lumina/contracts/structures.json (Lumina theme test surface) both updated to reflect the new DOM shape. The plan rune contracts now show zones + contentSlots instead of slots + structure.