Share immutable backend defaults during profile capture

This commit is contained in:
2026-11-21 17:55:06 +00:00
parent 6f45fd9fd0
commit ba5ac651e2
4 changed files with 56 additions and 7 deletions

View File

@@ -138,7 +138,9 @@ ConfigKit resolves profile inheritance before the handoff. Within a collection,
`extends: {id: parent}` names a sibling local ID; it is not a cross-collection reference.
The configuration adapter validates final effective resource references and
field values, then captures backend definitions and profile target snapshots
with backend defaults and outbound-control presence. Null profile endpoint,
with backend defaults and outbound-control presence. Profiles without provider
overrides share capture-owned immutable backend parameter maps; target lookups
still detach mutable values before runtime use. Null profile endpoint,
credential source, and whole provider map permit backend fallback after
composition, subject to the required-credential rule. A profile can remain
partial until runtime overrides complete it. Resource inspection selects indexed

View File

@@ -173,7 +173,13 @@ real-world benchmark is needed to establish that algorithmic change.
### 5. Share Immutable Backend Defaults Across Profiles Without Overrides
Status: open for consideration. Priority: P3. Implementation stage: 6.
Status: complete. Priority: P3. Implementation stage: 6.
Completion: profile construction now reads capture-owned backend definitions
directly and shares immutable provider maps when no overlay is needed. Registry
and runtime lookups remain defensive, and overlays still copy before merging.
Added lookup/overlay isolation coverage and updated internal documentation.
The full `go test -race ./...` suite and `go vet ./...` passed with Go 1.27.4.
Locations: `internal/configuration/targets.go:27–29` and `68–78`,
`internal/backend/registry.go:39–48`, and