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

Check projection budgets before container allocation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-25 21:25:00 +00:00
parent ae3408a096
commit ea27f17f5c
4 changed files with 130 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/roadmap/implementation.md
View File

@@ -159,6 +159,9 @@ Focused check: `go test ./internal/engine -run 'Mapping|Value|Projection|Clone|O
Finding: **A04**.
Owners: `internal/engine/projection.go`, `value_operation.go`, `projection_test.go`.
Status: **complete** (A04). Prior stage commits: `2736ddf`, `deb9aa5`,
`ae3408a`. Validation passed: `GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -run 'Projection|Inline|Resolution' -count=1` and `GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -count=1`.
1. After charging a container node and before its bulk reservation, compare its
minimum remaining cost with the current node allowance: at least one node per
sequence element and one key plus one value node per map entry. Use comparisons