Plan the ConfigKit inheritance upgrade

docs/roadmap/configkit.md

@@ -10,7 +10,8 @@ ConfigKit owns source composition and inheritance. Notarius continues to own
 typed configuration, domain defaults and validation, pipeline resolution, and
 execution. This work does not introduce a second configuration-merging engine.
 
-This is a feature roadmap, not an implementation sequence or release approval.
+The [implementation plan](implementation.md) owns the ordered work and
+validation sequence. Release preparation and publication remain separate.
 
 ## Reviewed Baseline
 
@@ -198,12 +199,13 @@ Use focused Notarius boundary tests, not a duplicate of ConfigKit's full suite:
 - Maintained examples and their imported fragments validate offline without
   credentials or provider calls.
 
-Start with configuration and CLI tests, including document/path/operational,
-effective/explanation, and maintained-example coverage. Add framework-resolution
-coverage only where a distinct handoff risk requires it. Before handoff, run
-the offline default suite, vet, and build with `GOWORK=off`, plus dependency
-tidiness and documentation diff/link checks appropriate to the changes.
-These are upgrade validation activities, not additional permanent release gates.
+Configuration and CLI boundary coverage should protect document/path/operational,
+effective/explanation, and maintained-example behavior. Framework-resolution
+coverage is appropriate where a distinct handoff risk requires it. Acceptance
+includes the offline default suite, vet, and build with `GOWORK=off`, dependency
+tidiness, and documentation diff/link checks appropriate to the changes. The
+implementation plan owns their sequencing; these checks are not additional
+permanent release gates.
 
 ## Deferred Capabilities And Non-Goals