Internal-only cleanup that lands the rest of WORK-323 once WORK-331 has stopped emitting the dual-emit metas. Remove the now-dead legacy read/strip path so data-rune-fields is the engine's only field-data input. No external/contract benefit beyond Tier 1 — this is for a single internal representation and a smaller engine.
Tracking started Jun 3 — check back for trends.
ed0293cDelete, in packages/transform/src/engine.ts:
readField meta-fallback (read modifier/field values from the bag only — the readMeta fallback branch goes away);consumedModifierFields set that drives that strip;Genuine schema.org <meta property> and the directly-built cross-page sentinel metas (collection-*, aggregate-*, …) are untouched — they never went through the readField path.
Removing the engine meta-fallback breaks the engine-unit-test fixtures that feed <meta data-field> directly to the engine with no bag (the "168-break" seen in the original WORK-323 attempt). Measured surface (2026-06-03): ~10 files — engine-core, engine-blocks, metadata, value-mapping, computed, repeat, engine-features, context-modifiers, fields, extract-interface (~80 data-field references) — must be migrated to construct data-rune-fields instead. Moderate risk: this changes the engine input contract to bag-only, a behaviour change for any external producer of a serialized tree (cached content, third-party tooling) that emits metas without a bag.
data-rune-fields; the readMeta data-fallback, step-7 modifier strip, and kebab set are removed.<meta data-field> directly are migrated to data-rune-fields.<meta property> and cross-page sentinel metas still pass through unchanged.