list|tag:x field with emitTagresolveSequence's emit branch skips anything that is not a list, then replaces the field with only the emitted nodes (packages/runes/src/lib/resolver.ts:194):
Tracking started Sep 24 — check back for trends.
97231belist|tag:x field with emitTag yields both the emitted and the authored tags, in document orderlist-only field with emitTag is unchanged (cast, audio, plot)refrakt contracts --check and npm run seo:baseline:check report no driftnpm test passes unchangedPass a non-list node through into tagNodes rather than continue-ing past it. It is already a tag and needs no conversion — only to keep its position.
Verified before filing. Given - Song A, - Song B, {% track name="Song C" /%}, - Song D against such a field, the resolver returns ['Song A', 'Song B', 'Song D'].
The result is a homogeneous, document-ordered array, which is better than cast's current shape: cast collects list items and explicit tags in two separate fields and concatenates (const allMembers = [...asNodes(resolved.members), ...asNodes(resolved.items)]), so all list-derived members land before all explicit ones and interleaving is lost. cast is not changed here, but the option becomes available to it.
listNodes wrapper is [result[field.name]], so the same branch must handle it.tag:x where x is not the emitTag name: the node still passes through unconverted, which is correct — the content model said it was acceptable.