Add ConfigKit scope contracts and adapters

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implement the optional integration modules and captured registration API
 
-Status: implementation in progress. Stages 1 through 7 are complete; subsequent work follows the ordered roadmap.
+Status: implementation in progress. Stages 1 through 8 are complete; subsequent work follows the ordered roadmap.
 Execute the stages in order. Each stage is sized as a separate Luna coding-agent
 assignment. This document authorizes no publication or changes to sibling
 repositories.
@@ -392,9 +392,17 @@ snapshot-isolation guarantee is added.
    core-owned severity. Preserve diagnostics returned with failures and appropriate
    warning/error behavior; caller-owned effects remain caller-owned.
 
-**Completion evidence:** adapter metadata without loader calls, native view facets,
-nil original loaders, retained scope causes after repeated attachments/narrowing,
-diagnostic provenance and warning/error mapping, and public signature ownership.
+**Completion evidence — complete:** ckconfig now owns the selected typed
+contracts, with ConfigKit paths and records confined to the integration module.
+`WithScopeError` copies retained causes without mutating the original and keeps
+wrapping identity through repeated attachment and operation narrowing. The
+ConfigKit adapter declares all four capabilities without loading during
+construction, retains original nil-loader issues, passes context/selection/input/
+state to the loader, and exposes the result's native effective/source/explanation
+facets directly. Failed ConfigKit loads retain their original error and structured
+diagnostics; diagnostic severity and source legends use core severity and native
+ConfigKit writing. Focused adapter tests pass. The complete ckconfig suite remains
+for the later family and report implementation stages.
 
 ## Stage 9: Assemble configuration families and prepare selected inputs