Demonstrate requirements discovery in composed example

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Implement PromptKit requirements inspection
 
-Status: in progress; Stages 1 through 4 are complete.
+Status: in progress; Stages 1 through 5 are complete.
 
 ## Authority and working rules
 
@@ -365,6 +365,20 @@ Run the composed example's tests and both commands from its directory. Record
 actual report semantics, not explanatory wording snapshots. Documentation of
 these copyable commands belongs in Stage 6.
 
+**Completed:** Extended the synthetic prompt in
+`integrations/ckprompt/examples/composed/main.go` with the conditional
+`notes` dependency while retaining the declared `topic` input. Added assembled
+App coverage in `main_test.go` for selected spring identity, missing and
+supplied `mode`, conditional versus required classification of undeclared
+`notes`, incomplete versus complete discovery, and success for both reports.
+`GOTOOLCHAIN=local go test ./examples/composed -run
+'TestComposedRequirementsDiscoveryUsesSelectedCampaign$' -count=1` and
+`GOTOOLCHAIN=local go test ./examples/composed` passed from
+`integrations/ckprompt`. Both roadmap commands passed from
+`integrations/ckprompt/examples/composed`: the first report was incomplete with
+a missing `mode` issue and conditional `notes`; the second was complete with
+`mode` supplied and required `notes`. No material limitations were encountered.
+
 ## Stage 6: Align canonical documentation with the delivered feature
 
 **Outcome:** API, operator, and consumer documentation describes the implemented