fieldMetas and groupByHeadingThe two utilities with actual design in them, as opposed to the spellings in WORK-602.
fieldMetas(attrs, spec) collapses the declare-then-name-again cycle into one declaration, returning a Record<string, Tag> usable directly as properties. plugins/plan/src/tags/work.ts goes from 36 lines of plumbing to about 13:
Tracking started Sep 24 — check back for trends.
fieldMetas' spec is data: a bare string, or { from: [...], default } — no entry accepts a functionJSON.parse(JSON.stringify(...)) unchangedfrom resolves only the declared roots (attrs.*, file.*); an unknown root is rejected at call time rather than resolving to emptyconfig.variables.file express their created / modified fallback without a closurefieldMetasfieldMetas is adopted where a rune's metas are all plain attrs reads mapped into properties; runes needing a meta outside properties, or conditionally, keep the explicit formgroupByHeading is adopted at the seven loop sites, with each rune's per-item parser left rune-specificfieldMetas; nothing in the codebase or docs introduces a second metaFields, and RuneConfig.metaFields is unchangedrefrakt contracts --check and npm run seo:baseline:check report no driftnpm test passes unchangedfieldMetas writes into the same flat key space as refs (ADR-008), so the collision check has to keep working against a computed object rather than a literal — worth a test, since the current check reads Object.keys of both and a generated object is the case nobody has exercised.
Key order matters for data-rune-fields, which is JSON.stringifyd: iterate the spec in declaration order so the bag's key order stays stable and the contracts diff stays empty.
groupByHeading shares only the traversal. parseColorEntry, parseNameValue, parseFontEntry and parseLocationItem stay where they are — the loop is the duplication, not the parsing.
fieldMetas produces the properties object, so it lands after the children emission is gone rather than having to reproduce itproperties and refs shareCompleted: 2026-10-06
Branch: claude/v0-37-post-release-plan-dc3va1 PR: refrakt-md/refrakt#657
packages/runes/src/lib/field-metas.ts: fieldMetas(attrs, config, spec) — spec is data (bare-string default, or { from: ['attrs.x' | 'file.x', …], default }); every source is validated before one is chosen, so an unknown root throws even after a hit; keys emerge in declaration order. Exported with FieldMetaSpec / FieldMetaEntry / FieldMetaSource.fileVars closures are gone) and the seven other calls whose properties are all plain attrs.X ?? 'literal' reads: sidenote, pullquote, map-pin (gained its config param), event, organization, comparison-row, api.packages/runes/src/lib/node.ts: groupByHeading(nodes, { initial, heading, item, other? }) — shares only the traversal; the rune's heading callback decides the next group. Adopted at tint (unrecognised heading keeps the section), palette ×2 (same-titled headings stay separate groups), spacing ×2 (unrecognised heading closes the section; one shared sectionOf), map (non-list nodes pass through in order).packages/runes/test/field-metas.test.ts: JSON round-trip, root rejection (incl. a bad source after a hit), declaration order, ADR-008 collision on a computed properties object, traversal incl. other.hintType ← type) or whose metas are conditional keep the explicit form; neither utility is mandatory.refrakt inspect --json over every rune × variant on both sites was byte-identical to main.