base-layer/configkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use entry metadata for resolution presence

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-26 14:30:25 +00:00
parent 0dd16aa8a9
commit 28ef9b6200
4 changed files with 154 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Interface Contract Remediation Implementation Plan
Status: pending. All stages below remain unimplemented.
Status: in progress. Stage 1 is complete; Stages 2–18 remain pending.
Baseline: `f6d54a094a2b5ada5748686620659399dce7ebf0`.
Audience: a Luna coding agent executing the stages sequentially.
@@ -290,7 +290,9 @@ change only defect expectations and tests tied to retired representations.
Finding 1. Owners: `resolution.go`, `load_metadata.go`, resolution/provenance tests,
and one root regression in `facade_compatibility_test.go` or a focused new facade
test file. Status: pending.
test file. Status: complete. Validation:
`GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test ./internal/engine -run 'Resolution|Provenance|Default' -count=1`
and `GOTOOLCHAIN=local GOPROXY=off GOTELEMETRY=off go test . -run 'TestFacadeResolutionPresenceUsesDynamicEntryShape' -count=1`.
1. Add a private entry-presence helper using `resolutionInput.lookup` and its
`FieldInfo.Explicit`. Use it in `Resolution.IsExplicit` after existing