Replace hardcoded density contexts with configurable childDensity

Remove the hardcoded COMPACT_CONTEXTS and MINIMAL_CONTEXTS sets from the identity transform engine and replace them with a childDensity field on RuneConfig. This lets community packages declare density behavior without modifying the engine.

claude/file-naming-convention-LJdwR View source

Criteria completion

Tracking started Apr 21 — check back for trends.

Relationships

ID:SPEC-033Status:accepted

Structure Slots and Declarative Flexibility

ID:WORK-112Status:done

Implement named slots with ordering for structure entries

Priority:highComplexity:moderateMilestone:v1.0.0

claude/file-naming-convention-LJdwR current done

changeset-release/main done claude/align-sidenav-styling-4MuxV done main done

Apr 21, 01:17 PMf2b3512
Created (done)by Claude
Add {ID}-{slug}.md filename convention + migrate filenames subcommand

Acceptance Criteria

RuneConfig in packages/transform/src/types.ts has childDensity?: 'compact' | 'minimal' field
The engine in packages/transform/src/engine.ts reads childDensity from the parent rune's config instead of checking hardcoded sets
data-density attribute is applied to child runes identically to current behavior
Core config in packages/runes/src/config.ts declares childDensity for Grid, Bento, Gallery, Showcase, Split (compact) and Backlog, DecisionLog (minimal)
Hardcoded COMPACT_CONTEXTS and MINIMAL_CONTEXTS sets are removed from the engine
Community packages can declare childDensity in their RunePackage.theme.runes config
All existing tests pass — HTML output is identical before and after
TypeScript compiles cleanly

Approach

Add childDensity to RuneConfig in types
Add childDensity entries to the 7 core runes in packages/runes/src/config.ts
Modify the engine's density resolution to look up the parent's RuneConfig.childDensity from the theme config map
Remove the hardcoded sets
Verify with refrakt inspect that output is unchanged for affected runes

References

SPEC-033 (Feature 4 — Configurable Density Contexts)