Record PromptKit roadmap scope and backend inspection deferral

docs/roadmap/future.md

@@ -33,13 +33,33 @@ under the [release procedure](../release.md).
 The published ckprompt v0.2.0 retains its earlier dependencies; see the
 [consumer guide](../consumers/guide.md#module-selection) for module selection.
 
-### Later PromptKit release review
+### PromptKit v0.19.0 roadmap preparation
 
-The completed adoption used PromptKit v0.18.0 as released.
-Review v0.19.0 separately once it is published; do not inspect or monitor
-unreleased upstream work in anticipation of that review. A later released
-version requires its own contract and compatibility assessment before selection
-and does not reopen the completed v0.18.0 adoption.
+The completed adoption used PromptKit v0.18.0 as released. PromptKit v0.19.0
+has now been released and reviewed. The working adoption scope includes the
+dependency, checksum, attribution, and unpublished candidate-note updates;
+consumer compatibility guidance and corrected credential-report wording;
+focused authentication-reason and smoke preparation-error coverage; and final
+independent-module and aligned-workspace validation.
+
+The proposed additional CLI scope is agreed in principle, subject to review of
+the adoption roadmap: concrete request preview, applicable request-override
+flags, namespace selection, configuration path discovery and explicitness,
+and detailed configuration comparison. Configuration failure investigation is
+also proposed for this roadmap, combining failed-load source inventory and
+structured diagnostics under
+[configuration inspection extensions](#configuration-inspection-extensions).
+Successful evidence reporting must retain the failed configuration outcome;
+report-delivery failures remain separately observable.
+
+These proposals concern standard operator commands, flags, and reports, not
+general-purpose helpers for application-internal PromptKit use. Exact CLI/API
+contracts and implementation sequencing remain for roadmap review. Focused
+backend inspection remains deferred pending released upstream support, as
+recorded under
+[PromptKit inspection and selection extensions](#promptkit-inspection-and-selection-extensions).
+Use released upstream contracts only; do not inspect or monitor unreleased
+upstream work in anticipation of future adoption.
 
 ## Future capability targets
 
@@ -107,6 +127,16 @@ metadata remains the recommended next functional sprint, under
 The OD identifiers below belong to the PromptKit adoption roadmap, separately
 from the ConfigKit review identifiers above.
 
+- **Focused backend inspection.** Defer a standard backend detail command
+  until a released PromptKit version provides a suitable public backend
+  inspection capability. The operator task is to inspect one backend's
+  endpoint, credential environment reference, concurrency and queue settings,
+  provider defaults, and smoke-probe configuration without running a probe.
+  PromptKit v0.19.0 has no dedicated backend inspection API. Do not implement
+  this proposal by reconstructing backend selection from captured
+  configuration. Review the released upstream capability before selecting
+  command syntax and report fields; this feature is outside the v0.19.0
+  adoption scope.
 - **Prepared-request inspection (PromptKit OD-4).** Consider an optional provider
   and report based on the released native `Engine.Prepare` and `PreparedRun`,
   reusing the concrete request-builder pattern. This would extend standard