Define comparison artifact contracts

docs/roadmap/profile-comparison.md

@@ -280,8 +280,8 @@ The completed feature includes:
 
 - the `compare` CLI command for every implemented generated-text report;
 - repeatable explicit profile selection and validation;
-- configured and CLI output-directory integration after the prerequisite
-  feature lands;
+- configured and CLI output-directory integration through the implemented
+  destination policy;
 - one-time report resolution, collection, deterministic preparation, and YAML
   serialization;
 - concurrent execution through one Promptkit executor with backend capacity
@@ -353,9 +353,10 @@ owns the statelessness, concurrency, notification, and publication invariants.
 
 The [Promptkit integration guide](../integrations/promptkit.md) should describe
 the consumer-visible multi-profile execution boundary without duplicating
-Promptkit's backend-capacity reference. App orchestration, prompt input,
-generated text, prompt debugging, and any new bundle implementation details
-belong in focused documents under `docs/internal/`.
+Promptkit's backend-capacity reference. The versioned manifest and flat bundle
+format belong in a focused contract under `docs/integrations/`. App
+orchestration, prompt input, generated text, prompt debugging, and bundle
+publication mechanics belong in focused documents under `docs/internal/`.
 
 Current-state documentation must not describe profile comparison as available
 until the implementation lands.
@@ -393,5 +394,5 @@ affected canonical documentation must describe the implemented behavior.
 
 ## Open Questions
 
-None. The scope, prerequisites, user intent, and target behavior required for a
-future staged implementation plan are defined above.
+None. The scope, prerequisites, user intent, and target behavior are defined
+above.