WORK-673
ID:WORK-673Status:done

A vocabulary report per plugin rune and a token-only lint for plugin CSS

ADR-044 lets a plugin rune bring its own structure CSS only for genuinely novel parts, written only in theme tokens. Two checks make the tiers checkable rather than advice. Neither exists.

Priority:lowComplexity:moderateMilestone:v0.46.0Source:ADR-044
main View source

Criteria completion

Criteria completion: 5 of 5 (100%) checked; tracking started on Nov 2, no incremental history yet0%25%50%75%100%Nov 2Nov 4

Tracking started Nov 2 — check back for trends.

Relationships

Implements 1
Related 2
Branches 3
main current done
claude/milestone-v0-44-0-ism7ni doneclaude/value-primitives-and-grid readyclaude/post-v0.43-roadmap-mf1ngx ready
History 5
  1. 703d741
    Created (done)by bjornolofandersson
  2. b24c95c
    Content editedby Claude
    plan: WORK-672, WORK-673 done (#754)
  3. ff8b000
    Content editedby Claude
    v0.46.0 batch 2: theme vocabulary coverage; plugin vocabulary report and
  4. 0ec343f
    Content editedby Claude
    plan: draft v0.45.0 and v0.46.0; WORK-660 joins v0.44.0
  5. c527aa0
    Content editedby Claude
    plan: accept ADR-042 to ADR-045; SPEC-166 D6 formats; WORK-669 to WORK-6

Acceptance Criteria

  • A report built from refrakt contracts lists, per plugin rune, the elements in its output that carry no vocabulary; it is a report, not an error, because tier 3 is legitimate
  • A lint flags literal colours, sizes and font stacks in a plugin's stylesheets; it starts as a report, and a plugin that passes can say it is theme-portable
  • Both run over the nine first-party plugins, and the results are recorded as the baseline Lumina's per-rune CSS drains from
  • The plugin-authoring guide (site/content/extend/plugin-authoring/authoring.md) is rewritten around ADR-044's three tiers, with its styles/ example as a tier-3 example
  • The token set is documented as a public contract for plugins as well as themes

References

  • ADR-044: Consequences.
  • WORK-672: the theme half of the coverage.

Resolution

Completed: 2026-11-02

Branch: claude/milestone-v0-44-0-ism7ni

What was done

  • packages/transform/src/plugin-vocabulary.ts (new):
    • novelElements(contract, config): contract elements that are not a block zone, section role, media slot or ordinal;
    • lintTokenOnly(css): literal colours, sizes and font stacks, ignoring tokens, keywords, 0, token definitions and var() fallbacks.
    • Tests in test/plugin-vocabulary.test.ts.
  • packages/cli/src/commands/plugin-validate.ts: a vocabulary report (novel elements per themed rune; literals per styles/ sheet; themePortable), printed and in --json. Never an error.
  • scripts/plugin-vocabulary.mjs with its test: the baseline for the nine first-party plugins, at contracts/plugin-vocabulary.json (68 runes, 44 novel elements; literals 21 colour, 687 size, 1 font across skeleton and Lumina per-rune CSS). Added npm run plugins:vocabulary[:check], and excluded the file from Biome like the other generated baselines.
  • Docs:
    • extend/plugin-authoring/authoring.md opens with ADR-044's three tiers, and its styles/ example is now a tier-3, token-only sheet.
    • theme-authoring/css.md states the token set is a public contract for plugins.
    • The cli-overview row.

Notes

  • First-party plugins ship no CSS; their runes are styled by skeleton and Lumina per-rune files, so the baseline lints those.
  • Some "novel" findings are runes whose sections lack an autoLabelled role (for example Changelog's eyebrow and blurb). Those are worth declaring, not styling.