data-meta-rank is the channel by which density compaction is meant to drop secondary metadata. It is specified, it is styled, and no code path ever puts it on an element.
Specified — SPEC-026 (lines 242, 264, and meta-ranks.css in its file list) and SPEC-079 (line 53, and the worked example at 461–465, where a header zone emits data-meta-type="id" data-meta-rank="primary").
Styled — four rules in packages/lumina/styles/dimensions/density.css:
[data-density="compact"] [data-meta-rank="secondary"] { display: none; } [data-density="minimal"] [data-meta-rank="secondary"] { … } [data-density="compact"] [data-density="full"] [data-meta-rank="secondary"], { … } [data-density="minimal"] [data-density="full"] [data-meta-rank="secondary"], { … }
Nowhere else. A repo-wide search for meta-rank outside node_modules returns only those four Lumina rules and the two specs. In particular it is absent from:
packages/transform/src/types.ts — MetaField has metaType, sentimentMap, label, condition, renderWhenEmpty, href, rating, icon, tag, splitOn, transform. No rank.RuneConfig in packages/runes/src/config.ts and plugins/*/src/config.tsDensity compaction cannot drop anything. [data-density="compact"] currently does three things only: shrinks --rune-padding, shrinks --rf-title-size, and line-clamps [data-section="description"] to two lines. The "compact shows less metadata" behaviour the dimension documents does not happen, and the four rules are dead selectors.
Render any metadata-bearing rune at density="compact" and inspect the emitted chips. Every field present at full is present at compact.
Fields the rune marks as secondary are hidden at compact and minimal.
All fields render at every density. No element in the document carries data-meta-rank.
Genuinely open, and the reason this is filed rather than fixed.
Wire it. Add rank?: 'primary' | 'secondary' to MetaField, emit data-meta-rank alongside data-meta-type, and annotate the existing metaFields manifests. This is what SPEC-079 designed, and the rank is a rune-level judgement — the rune knows which of its facts are essential — so it belongs on the manifest rather than in theme config.
Or delete the rules. If density is deliberately spacing-only, the four Lumina rules and the spec passages are misleading and should go.
The first is preferable, and not only for tidiness: ADR-029 decision 5 bounds what a theme may omit from a rune's rendered structure, and names the density/rank channel as that bound. If the channel does not exist, the bound is unenforceable and a theme's only way to hide a part is to drop it from a layout tree — which is exactly the unbounded omission that decision was written to prevent.
This is the reverse direction of the drift BUG-024 shows. There, per-rune CSS shadows a dimension that works. Here, theme CSS targets a dimension that was never wired. Both are invisible to packages/lumina/test/css-coverage.test.ts, which only asks whether generated selectors have CSS — never whether CSS selectors have generators. SPEC-137 covers both directions.