Verify mounted composition and version ownership

This commit is contained in:
2026-10-14 13:24:06 +00:00
parent a2fab66aba
commit a1c557603f
2 changed files with 337 additions and 3 deletions

View File

@@ -253,7 +253,7 @@ double wrapping or application-level directive leakage.
## Stage 5 — Complete strict tiers and main version ownership
Status: planned. Scope: assembly and version interactions, not a new merger.
Status: complete. Scope: assembly and version interactions, not a new merger.
1. Review `acquireUnderlayGroup`: version checks must use placed content, and
documents taken from `acquired.composition.applications` must already be
@@ -273,8 +273,14 @@ Status: planned. Scope: assembly and version interactions, not a new merger.
Preserve exact configured-path integer conversion and ordinary nested typing.
Validate: destination/composition/overlay/version/grouped tests and everyday
check. Done: placed and authored equivalents agree on values and conflicts;
main ownership and lifecycle timing are preserved.
check. Validated with `go test ./internal/engine -run 'LayeredDestination'`,
`go test ./internal/engine -run 'Destination|Composition|Overlay|Version|Grouped'`,
and `./scripts/check.sh` (go1.26.8 linux/amd64); all passed. The new mounted
cases verify strict same-tier conflicts and disjoint composition, independent
destinations and nested paths, recursive/atomic overlay behavior, explicit
null/false/zero, and main-only nested version checking after imports compose.
Done: placed and authored equivalents agree on values and conflicts; main
ownership and lifecycle timing are preserved.
## Stage 6 — Reconcile diagnostic coordinate systems