| Callback composition | Application defaults, version acceptance, resolution, validation warnings, sensitivity, and sequence identities survived registration. A second component ran explicitly after PromptKit normalization. |
| Independent loads | Reusing one configured definition preserved omitted versus explicit input values across successive loads. Concurrent independent loads passed under the race detector. |
| Final presence | Final native metadata supplied required/content-type/description presence, including inherited values, normalized text, explicit false, omission, and nullable metadata. Resolver-side capture was unnecessary for the tested facts. |
| Source context | A mounted collection inherited messages and schemas from one filesystem while an overriding message used another. Capture opened effective message files without reopening configuration documents. Inherited schemas remained usable during preparation and execution. |
| Ownership | Later mutations to model pointers, input slices, nested provider maps, schema paths, and inline schema maps/arrays did not change captured execution. Inspection stayed frozen. |
| Extension fields | Section, collection, backend, profile, and prompt extensions survived composition and normalization. Focused configuration output retained them with application sensitivity. Prompt resource reporting omitted them, and they did not become provider parameters. Nested output objects remained strict. |
| Missing and invalid sections | Missing fields, declared zero settings, typed nil pointers, explicit null, and empty settings were exercised. Bundles contributed only when selected before loading. Wrong section types failed construction. Legacy-looking application root keys were left to the application. |
| Resource helpers | Wrapperless collection documents and `id`-first prompt files mounted through native destinations/item placement; resource IDs and listings were unchanged by the wrapper. |
| Inspection | The actual PromptKit facade forwarded diagnostics, focused output, enumeration, explanations, and cross-root-type comparisons. Native checks also covered absent/null scopes, historical-only paths, additions/removals, sibling exclusion, atomic ancestor differences, and ancestor sensitivity. Metadata and explicit queries remained unfiltered. |
| Version ownership | The application retained its own version rule. Resource-level `version` fields could be application data without a PromptKit-specific version check. |
| Repair presence | The prototype's pointer-valued configuration budget selected mode defaults after composition. Omission/null, explicit zero, budgets two/three, `none` rejection of positive budgets, and null clearing an inherited budget passed. Captured budgets were concrete. |
The repair checks establish compatibility of configuration defaulting with the
handoff. They do not constitute implementation or validation of the separate
runtime output-contract API migration or the complete repair-default feature.
## Simplest Supported Integration
### Registration
Retain a small generic helper accepting an existing `configkit.Definition[T]`
and a `func(*T) *Settings` selector. The experiment preserved existing callbacks,
appended library sequence registrations, combined sensitivity predicates, and
left application defaults and version policy intact. Existing callbacks ran
before library callbacks; a consumer could wrap the returned callbacks to run
another component afterward. No component registry was needed.
Keep actual normalization and validation in one internal rule implementation.