yaml-splice extraction and writer migrations
Status: closed/done · Version: 0.5.0
Extract determined-vault’s span-preserving YAML splice engine into the pure
yaml-splice crate defined by D-7N7I-pure-functional-yaml-editing, publish its
conformance corpus, and migrate existing whole-block writers. Independent of the
markdown CST (M-C6XN-lossless-cst-core consumes this; it does not gate it) and
startable alongside M-3PVK/M-8DQW. This is the strategy’s best early technical win:
real consumers exist, active corruption risk (lost YAML comments) is removed, and
nothing here waits on parsing, WASM, or vault work.
Success criteria
Section titled “Success criteria”-
determined-vault’s adversarial YAML/frontmatter fixtures move into a reusable conformance corpus with no behavior change. - The pure crate meets D-7N7I’s contract: no I/O, semantic no-op is byte-identical, structured refusals, batch atomicity — proven by the corpus.
-
determined-vaultkeeps compatibility re-exports;determined-notes::notekitanddetermined-photosstay green as the first two consumers. - At least two whole-block writers migrate and delete their old write logic —
first an SDLC writer touching only known top-level keys
(
_update.ts-class), then one more complex writer. - Machine-generated whole-document writers (e.g. site-builder) are classified, not auto-migrated: canonical generation stays a legitimate discipline.
Deliverables
Section titled “Deliverables”- Conformance corpus package.
- Extracted incubation crate (unpublished until the derived-library promotion bar is met).
- Compatibility re-exports in
determined-vault. - Two writer-migration PRs.
Out of scope
Section titled “Out of scope”- Nested-path edits, YAML CST/DOM, raw fragment insertion (D-7N7I V2 questions).
- Markdown fence handling (
markdown-util) and CAS/atomic writes (storage seam).