Reconcile reporting tests and boundaries

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Invocation reporting implementation plan
 
-Status: Stages 1–17 complete. Stage 18 is next.
+Status: Stages 1–18 complete. Stage 19 is next.
 
 ## Objective and authority
 
@@ -676,7 +676,7 @@ ConfigKit, aliased quiet help, and offline PromptKit smoke commands also pass.
 
 ## Stage 18: Reconcile the full test suite and architectural boundaries
 
-Status: pending.
+Status: complete.
 
 1. Find and migrate remaining callers of removed constructors, raw invocation
    streams, terminal `SeverityError`, outcome diagnostic submission, and old
@@ -704,6 +704,19 @@ Validation: the suite should now build as a whole using the local three-module
 workspace. Focused reporter race testing is justified by the selected concurrent
 reporter contract; it does not establish a new permanent repository-wide gate.
 
+Completion: migrated the remaining core tests and benchmark caller to reporter,
+explicit explanation/cause, and presentation-result APIs. Updated reporting
+expectations for unprefixed Info, routed flag-alias parsing, quiet selection on
+routing failures, and causes remaining separate from terminal explanations.
+Reporter tests cover delivery states, retained failures, ignored errors,
+finalization, domain statuses, quiet late handles, independent healthy
+destinations, complete concurrent operations, and caller-owned writers.
+`GOTOOLCHAIN=local go test -count=1 ./...` passes in the root, ckconfig, and
+ckprompt modules; `GOTOOLCHAIN=local go test -race -run '^TestReporter' .` passes.
+Boundary checks confirm Cobra/pflag imports stay under `internal/cobra`, public
+Go documentation exposes no backend or internal types, and core does not depend
+on either optional integration module.
+
 ## Stage 19: Update canonical documentation and compatibility guidance
 
 Status: pending.