SPEC-141's main change. Replace the three whole-AST passes (walkAndReplaceIncludes, walkAndReplaceSnippets, walkAndReplaceData) and their hand-written order in config.ts with one walk that dispatches per tag, and move each preprocessor into the tag module that owns it:
Tracking started Oct 7 — check back for trends.
Node[] splices.PluginPipelineHooks.preprocess stays, undeprecated.include keeps its own nested expansion and cycle stack; data's internal subquery walk is removed in favour of the generic descent.data's enclosing check reads it.snippet's throwing transform stays.emitTag stays declarative; no content model is narrowed.ContentModelSchemaOptions accepts preprocess, receiving the rune's own node and returning a replacement, several, or nothingwalkAndReplaceIncludes, walkAndReplaceSnippets and walkAndReplaceData no longer exist as three separate traversalsdata's internal subquery walk is removed in favour of it (D3)include keeps its own nested expansion and its cycle stack; a direct and an indirect cycle are still named rather than overflowingsnippet's and include's preprocessors live in their tag modules; snippet-pipeline.ts and include-pipeline.ts are gone as top-level modulesconfig.ts no longer states a preprocessor order{% snippet %} inside a {% data %} row template resolves against the bound row — BUG-027, with a regression test{% data %} still resolves its subquery per outer row, with the outer row binding the inner tag's attributes and not its body (SPEC-127 / WORK-553){% snippet %} and {% data %} inside an included file still resolve — the existing include-pipeline.test.ts cases pass unchangedemitTag remains a declarative field; no rune's content model is narrowed to match the emitted tag, and match still states the authored input shape (D8)refrakt contracts --check and npm run seo:baseline:check report no driftpreprocess, and says when to reach for the plugin-level hook instead (D2)data a producer