WORK-060
ID:WORK-060Status:done

Annotate Rune Configs with Metadata Dimensions

Priority:highComplexity:moderateMilestone:v0.9.0Source:SPEC-024
main View source

Criteria completion

Criteria completion: 9 of 9 (100%) checked; history from Mar 24 to Mar 240%25%50%75%100%Mar 24Mar 24

Relationships

Implements 1
Related 1
Branches 4
main current done
claude/remove-travelers-attribute-F5Q0J doneclaude/file-naming-convention-LJdwR donechangeset-release/main doneclaude/align-sidenav-styling-4MuxV done
History 6
  1. f2b3512
    Content editedby Claude
    Add {ID}-{slug}.md filename convention + migrate filenames subcommand
  2. 59ded4a
    Content editedby Claude
    Implement SPEC-037 plan package hardening: all 7 work items
  3. f262d7b
    Content editedby Claude
  4. c3a9415
    • ☑ Core rune configs annotated: Budget (currency, travelers, duration)
    • ☑ Docs package configs annotated: Api (method, path, auth), Symbol (kind, lang, since, deprecated)
    • ☑ Learning package configs annotated: HowTo (estimatedTime, difficulty), Recipe (prepTime, cookTime, servings, difficulty)
    • ☑ Storytelling package configs annotated: Character (role, status), Realm (realmType, scale), Lore (category), Faction (factionType, alignment, size), Plot (plotType, structure), Bond (bondType, status)
    • ☑ Places package configs annotated: Event (date, endDate, location)
    • ☑ Media package configs annotated: Playlist (type)
    • ☑ Plan package configs annotated: Spec, Work, Bug, Decision, Milestone (all fields per SPEC-024 map)
    • ☑ `refrakt inspect` output for each annotated rune shows correct `data-meta-*` attributes
    • ☑ CSS coverage tests still pass (metadata attributes are additive, no BEM changes)
    by Claude
  5. a129a9e
    Content editedby Claude
  6. a333007
    Created (ready)by Claude
    Add work items for SPEC-024 (Metadata) and SPEC-025 (Universal Theming)

Summary

Once the identity transform supports metadata dimensions (WORK-059), annotate all existing rune configs across core and community packages with metaType, metaRank, and sentimentMap values. The full mapping is documented in SPEC-024's Rune Metadata Map table covering ~48 fields across all packages.

Acceptance Criteria

  • Core rune configs annotated: Budget (currency, duration)
  • Docs package configs annotated: Api (method, path, auth), Symbol (kind, lang, since, deprecated)
  • Learning package configs annotated: HowTo (estimatedTime, difficulty), Recipe (prepTime, cookTime, servings, difficulty)
  • Storytelling package configs annotated: Character (role, status), Realm (realmType, scale), Lore (category), Faction (factionType, alignment, size), Plot (plotType, structure), Bond (bondType, status)
  • Places package configs annotated: Event (date, endDate, location)
  • Media package configs annotated: Playlist (type)
  • Plan package configs annotated: Spec, Work, Bug, Decision, Milestone (all fields per SPEC-024 map)
  • refrakt inspect output for each annotated rune shows correct data-meta-* attributes
  • CSS coverage tests still pass (metadata attributes are additive, no BEM changes)

Approach

Work through SPEC-024's Rune Metadata Map table package by package. For each field, add metaType, metaRank, and optionally sentimentMap to the corresponding structure entry child in the rune's config. Verify with refrakt inspect <rune> after each package.

References

  • SPEC-024 (Metadata System — Rune Metadata Map)
  • WORK-059 (Metadata Dimensions on StructureEntry)