Validate independent module boundaries

docs/roadmap/implementation.md

@@ -1,18 +1,22 @@
 # Implement the optional integration modules and captured registration API
 
-Status: implementation in progress. Stages 1 through 15 are complete; subsequent work follows the ordered roadmap.
+Status: implementation complete. Stages 1 through 16 are complete.
 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.
 
 ## Scope and authority
 
-Deliver the target in the [module roadmap](modules.md), the exact declarations
-and behavior in the [registration API](registration-api.md), and the selected
-mechanics in the [registration backend design](registration-backend.md).
-Read [development orientation](../development.md) and its applicable policy guide
-before implementation. The [architecture policy](../policy/architecture.md) and
-accepted ADRs control if a planning instruction conflicts with them.
+This report retains the implementation sequence and completion evidence.
+Current contracts belong to the [core GoDoc](../../doc.go),
+[ckconfig GoDoc](../../integrations/ckconfig/doc.go),
+[ckprompt GoDoc](../../integrations/ckprompt/doc.go),
+[consumer guide](../consumers/guide.md), [CLI reference](../cli.md),
+[internal overview](../internal/overview.md), and
+[release procedure](../release.md). Read [development orientation](../development.md)
+and its applicable policy guide before related work. The
+[architecture policy](../policy/architecture.md) and accepted ADRs control
+architecture decisions.
 
 The governing decisions include [optional modules](../adr/0010-optional-integration-modules.md),
 [captured declarations](../adr/0011-captured-declarations-and-installation.md),
@@ -51,9 +55,8 @@ Go 1.26.8.
 
 The planning review found one module, integration source and examples in the
 root, ReleaseKit v0.3.0 selected as a Go tool, and a root-only release launcher.
-The [backend findings](registration-backend.md#baseline-findings) identify the
-parallel installation paths, repeated validation, mixed input/state storage, and
-help special case that this sprint replaces.
+The selected owners and current mechanics are recorded in the
+[internal overview](../internal/overview.md) and current package GoDoc.
 
 One factual correction to earlier planning is necessary: core `v0.1.0` is
 already published on `origin`. The observed annotated tag object is
@@ -614,7 +617,7 @@ dependency ownership.
 2. Rewrite ckconfig's simple example using `AppCommand`, with no dummy input/state
    types at its consumer call site. Retain a useful typed application command.
 3. Rewrite ckprompt's composed example using the finalized
-   [three consumer examples](registration-api.md#complete-consumer-registration-examples)
+   [three consumer examples](../consumers/guide.md)
    as API evidence: combined app/promptkit configuration scopes, applicable typed
    selectors, scope-aware checks, pointer input isolation, shared app-owned state,
    independent named inspection, and `session restore`.
@@ -845,11 +848,20 @@ publication wiring are verified with no compatibility scaffolding.
     pending real dependency/sum preparation. The workspace should contain no
     unrelated generated files or temporary replacement manifests.
 
-**Completion evidence:** all three module suites and representative consumers
-succeed; module/package graph checks prove the requested exclusion boundaries;
-current docs and licensing reflect distribution ownership; publication tooling
-selects one module through released contracts. Actual publication and upstream
-version adoption remain separate from this sprint.
+**Completion evidence — complete:** all three module suites pass with the local
+workspace, and the five maintained consumer invocations succeed. Workspace-off
+tests and three external consumer modules also pass using temporary module files
+with local replacements only for unpublished CommandKit modules; package and
+module graph checks confirm the intended core, ckconfig, and ckprompt dependency
+boundaries. Root tidy is clean, nested manifests were reconciled from temporary
+tidy runs, and no future-version checksums or distributed filesystem
+replacements were added. Public exports and ownership, installation/input cost
+paths, maintained guides, local links, license distribution, release notes, and
+the selected-module source-only release wiring were reviewed. Obsolete module,
+registration API, and backend planning documents were retired after their current
+owners and links were updated. No real publication was attempted. Actual
+dependency downloads and checksum preparation remain part of ordered release
+preparation after the prerequisite versions are published.
 
 ## Release handoff