Separate PromptKit messages from terminal context

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Invocation reporting implementation plan
 
-Status: Stages 1–12 complete. Stage 13 is next.
+Status: Stages 1–13 complete. Stage 14 is next.
 
 ## Objective and authority
 
@@ -496,7 +496,7 @@ old invocation API and is scheduled for migration in Stage 17.
 
 ## Stage 13: Migrate PromptKit acquisition adapters
 
-Status: pending.
+Status: complete.
 
 Primary files: [adapters.go](../../integrations/ckprompt/adapters.go),
 [validation.go](../../integrations/ckprompt/validation.go),
@@ -521,6 +521,18 @@ Validation: establish correct forwarding, passive data, separated context,
 and supported error identity. Preserve offline fixtures and existing builder/
 acquisition lifecycle protections. No live provider or credentials are needed.
 
+PromptKit engine loading now separates independent warning batches from native
+terminal records and carries both through catalogs, inspection, requirements,
+ConfigScope comparison, concrete request validation, and smoke acquisition.
+Native rendering retains scope/side headings, source legends, and diagnostic
+locations; original errors and reports returned with errors remain available.
+Offline adapter tests cover mixed record separation, writer propagation,
+comparison-side context, error identity, and existing request lifetimes. The
+ckprompt suite cannot execute yet: compiler diagnostics identify legacy
+reporting calls in `command.go`, `smoke_command.go`, and their tests, which are
+scheduled for Stages 14 and 15. No compile errors were reported in the migrated
+adapter files; Stage 20 will run the assembled suite.
+
 ## Stage 14: Migrate PromptKit listing and inspection commands
 
 Status: pending.