Compile configuration selector metadata during capture

This commit is contained in:
2026-10-11 13:05:22 +00:00
parent fba917f5bd
commit cec4da69d3
4 changed files with 115 additions and 79 deletions

View File

@@ -3,7 +3,8 @@
Reviewed on 2026-10-11, against committed implementation
`cc574915ee17e2d738f27874d2c8857aa1f51a47`. The implementation sprint starts
after planning commit `0d23676144ab1ce5047924e98f1ab6a2a9d6aeb6`.
Completion status and evidence are recorded per issue below. P1 identifies a functional contract violation; P2
Completion status and evidence are recorded per issue below. P1 identifies a
functional contract violation; P2
identifies architecture or documentation corrections; P3 identifies smaller
maintenance corrections. These priorities do not add publication gates.
@@ -82,7 +83,16 @@ Avoid assertions about a particular private representation.
## R2: Finish declaration-time compilation of configuration metadata
**Status:** Open. **Priority:** P2.
**Status:** Completed (2026-10-11). **Priority:** P2.
**Completed work:** family capture orders scope references and prepares each
scope's original binding list, each operation's binding union, and scope-choice
text. Inspection preparation reads those lists without static sorting or
membership compilation. A behavioral regression covers operation-specific flags
and capture of capabilities/applicability/handles after source edits. Existing
ordering, metadata-only, unused/required-selector, isolated-input, and shared-state
coverage passes; all three module suites pass offline with Go 1.26.8. No provider
cache or performance guarantee was introduced.
**Evidence:** [ckconfig/input.go](../../integrations/ckconfig/input.go),
`newConfigOperationCommand`, `selectorIndexesForOperation`, and