Specify automatic PromptKit source discovery

docs/roadmap/commandkit.md

@@ -266,7 +266,10 @@ released dependency set when implementing this outline.
    streams, and exit behavior against standard declarations. Record intentional
    migrations rather than recreating the old parser around CommandKit.
 2. Establish shared loaders and scopes using the native ConfigKit and PromptKit
-   integrations. Keep configuration/resource inspection distinct from preparing
+   integrations. Use the same engine-loading path for processing and every
+   PromptKit inspection, preview, validation, and smoke command, following the
+   [automatic source contract](promptkit.md#automatic-prompt-sources--resolved).
+   Keep configuration/resource inspection distinct from preparing
    an actual domain request. Standard scope validation need not reproduce the
    current combined settings-and-two-roles command; process setup must still
    establish what execution needs. Review generic override forwarding explicitly.
@@ -308,6 +311,12 @@ configuration and supplied-value handling through domain settings. Exercise
 stdout transcript isolation, file output, quiet/verbose/debug behavior, completion
 summary placement, cancellation, partial success, and output failures.
 
+Verify that automatic prompt replacements and their origins agree between
+processing, resource/configuration inspection, and request preview. Apply the
+shared loader's source selection to validation and smoke commands as well, using
+controlled provider boundaries for smoke acceptance. Inspection must retain the
+same source behavior without requiring processing inputs or starting preflight.
+
 Verify that the completion summary and created artifact locations appear only
 in verbose/debug diagnostics, never in transcript stdout. Reject quiet processing
 with a stdout destination; requested file outputs remain enabled in valid quiet