Carry destinations through imported configuration
This commit is contained in:
@@ -228,7 +228,7 @@ private integration step.
|
||||
|
||||
## Stage 4 — Carry placement through import acquisition
|
||||
|
||||
Status: planned. Scope: source-local directives and placed imported applications.
|
||||
Status: complete. Scope: source-local directives and placed imported applications.
|
||||
|
||||
1. Thread a normalized destination through `loadImportedDocumentsTracked`,
|
||||
`loadImportedWithAccessTracked`, and `importTraversal`, retaining root defaults
|
||||
@@ -246,9 +246,10 @@ Status: planned. Scope: source-local directives and placed imported applications
|
||||
paths. Verify a repeated file at two destinations in one group still fails,
|
||||
including an import/direct-input alias. Reuse cycle/containment regressions.
|
||||
|
||||
Validate: focused destination/import/glob/grouped tests and everyday check.
|
||||
Done: every retained imported contribution has effective placement and physical
|
||||
source identity, with no double wrapping or application-level directive leakage.
|
||||
Validated with `go test ./internal/engine -run 'Destination|PlaceDocument|Import|Grouped'`
|
||||
and `./scripts/check.sh` (go1.26.8 linux/amd64); both passed. Retained imported
|
||||
contributions have effective placement and physical source identity, with no
|
||||
double wrapping or application-level directive leakage.
|
||||
|
||||
## Stage 5 — Complete strict tiers and main version ownership
|
||||
|
||||
|
||||
Reference in New Issue
Block a user