eric/ConfigKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Verify accumulated import resource accounting

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-14 17:29:54 +00:00
parent 430985c629
commit 43e55dfa85
2 changed files with 214 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/roadmap/implementation.md
View File

@@ -270,7 +270,7 @@ root-scoped upper tiers. No limitations.
## Stage 5 — Verify accumulated resource accounting
Status: planned. Scope: limit regressions and any necessary narrow correction.
Status: complete. Scope: limit regressions and any necessary narrow correction.
1. Audit `placeDocument`, `destinationWrapperNodeCount`, `importAccounting`,
and composition totals. Each body uses the full effective destination for
@@ -290,6 +290,16 @@ Status: planned. Scope: limit regressions and any necessary narrow correction.
Validate: focused import/destination/limit/override tests and everyday check.
Done: accumulation cannot bypass current bounds or falsely charge absent input.
Evidence (2026-10-14): based on `430985c6293ca8f9151149f1af34481ac325eed3`,
using `go1.26.8 linux/amd64`. The focused engine import/glob/destination/grouped/
overlay/override/history/inheritance suite and `./scripts/check.sh` passed.
Exact, below, and above node-budget fixtures cover nested empty imports and
multiple glob matches using their accumulated destinations. Additional cases
verify accumulated depth bounds and that absent optional path/glob contributions
at unused depth add no source or wrapper charge. Existing
`TestSelectedOverlayAndCLIUsePlacementNodeCharges` continues to cover later
overlay/CLI accounting. No limitations.
## Stage 6 — Preserve diagnostics, source inspection, and resource contexts
Status: planned. Scope: coordinates, detached records, and resource ownership.