Verify PromptKit requirements command behavior

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implement PromptKit requirements inspection
 
-Status: in progress; Stages 1 through 3 are complete.
+Status: in progress; Stages 1 through 4 are complete.
 
 ## Authority and working rules
 
@@ -306,6 +306,22 @@ diagnostics for the command path and existing helper evidence for that native
 limitation; do not add a test-only engine injection API or claim an unavailable
 native warning scenario was exercised.
 
+**Completed:** Added installed-command coverage in
+`integrations/ckprompt/requirements_command_test.go` for native report
+equivalence across conditional discovery, selected/default identities,
+session-template discovery and bypass, and complete discovery with an
+unsupplied required variable. The tests also cover captured selectors and
+callback data, repeated invocation lifecycles, omitted pointer factories,
+input rejection and pre-acquisition cancellation, warning diagnostics,
+provider error identity, post-callback cancellation, nil results, partial report
+delivery, short writes, and diagnostic writer failure. The focused command
+`GOTOOLCHAIN=local go test ./integrations/ckprompt -run
+'TestRequirementsCommand(MatchesNativePromptKitDiscovery|PreservesNativeSelectionErrors|KeepsLifecycleAndCapturedDeclaration|ChecksInputAndCancellationBeforeAcquisition|PreservesDiagnosticsCancellationAndDelivery)$'
+-count=1` passed. `GOTOOLCHAIN=local go test ./...` from
+`integrations/ckprompt` passed, including the composed example suite. Native
+successful-acquisition warnings remain unavailable through PromptKit v0.14.0's
+public API; custom callback diagnostics exercise the installed command path.
+
 ## Stage 5: Demonstrate requirements in the maintained composed consumer
 
 **Outcome:** the existing consumer shows partial discovery and contextual