Resolve retirement of the curated profile summary

docs/roadmap/commandkit.md

@@ -31,6 +31,9 @@ known publication blocker to adoption.
   inspection, and captured engine configuration through its config scope.
   Native reports and namespace selection must remain available; a curated Audita
   subset is not a substitute. Inspection success is not execution readiness.
+- Apply the [resolved profile-summary decision](promptkit.md#profile-inspection-and-summary--resolved):
+  retire the curated profiles view, use standard configuration/resource inspection
+  and request preview, and add no replacement custom role summary at this stage.
 - Adopt standard ckconfig viewing, validation, sources, path discovery,
   explanation, and comparison. Use native evidence and common text/YAML/JSON
   rendering. Do not recreate removed provider-specific explanation writers.

docs/roadmap/library-adoption.md

@@ -66,8 +66,8 @@ They do not select unrelated work in [future.md](future.md).
   validation, structured-response contracts, and truthful partial-success
   behavior. Inspect each other restriction against a concrete domain need.
 - Standard library inspection and native redaction are part of the target.
-  Existing curated summaries may survive for a distinct domain purpose, but
-  cannot replace the full standard inspection surface.
+  Retire the curated profile summary in favor of the standard inspection and
+  preview interfaces, as resolved in the [PromptKit outline](promptkit.md).
 
 For each friction point, record the desired outcome, whether the constraint is
 library behavior or an Audita domain requirement, the proposed adaptation or

docs/roadmap/promptkit.md

@@ -115,6 +115,21 @@ External source selection remains part of the ConfigKit discovery/import
 decision. This workflow is required PromptKit adoption scope and should use
 native composition rather than a separate prompt loader or override system.
 
+### Profile Inspection and Summary — Resolved
+
+Retire `config print-effective --view profiles` and its Audita-owned summary
+code. Use application configuration inspection to show proposal/validation
+profile selections, standard PromptKit resource inspection for profile/backend/
+prompt definitions, and request preview for resolved execution settings and
+rendered messages. These views have distinct meanings and must be presented as
+such.
+
+Do not add a replacement custom role summary at this stage. Native interfaces
+cover the selected needs and reduce maintenance without a parallel target
+resolver. Include the retired view and its standard replacements in the
+hard-cutover guidance. The [CommandKit outline](commandkit.md) owns the operator
+surface and request-preview integration work.
+
 ### Migration Work
 
 1. Move to `go.maximumdirect.net/promptkit` together with ConfigKit's new types.
@@ -137,9 +152,10 @@ native composition rather than a separate prompt loader or override system.
 4. Adapt resource inspection to optional profile fields and separate backend
    inspection. These describe resources, not completed requests. Use real
    `PrepareExecution` details and `RunPrepared` for execution of the same captured
-   request. Do not duplicate PromptKit's full resolver or construct synthetic
-   requests merely to reproduce the old profile summary. Inspect bundled and
-   unselected partial resources without requiring them to be runnable.
+   request. Remove the curated profile view and its supporting projection code;
+   do not duplicate PromptKit's full resolver or construct synthetic requests
+   merely to reproduce that summary. Inspect bundled and unselected partial
+   resources without requiring them to be runnable.
 5. Implement the resolved backend and credential ownership decision above.
    Replace application backend/credential configuration with native resources
    and document the hard cutover. Preserve secret-safe diagnostics using the
@@ -199,23 +215,14 @@ its captured inputs. Check qualified-ID selection, effective prompt inspection,
 source provenance, and continued response-schema and domain validation with
 controlled responses. Include a maintained edit-and-rerun example for developers.
 
+Verify that role selections are visible in application configuration inspection,
+resources through standard inspection, and completed request settings through
+preview. Remove tests and examples that only preserve the retired curated view;
+cover its replacement workflows through the assembled CLI.
+
 No upstream request is yet selected. PromptKit is mature but pre-v1: significant
 blockers or awkward public boundaries can justify focused requests. Submit the
 minimal reproducer, desired outcome, and domain justification before building
 substantial local machinery. A review probe demonstrated distinct base/derived
 backend records preserving provider fields; that is an available native technique,
 not a decision to retain Audita's old backend ownership model.
-
-## Open Decisions
-
-### Existing Curated Profile Summary
-
-**Recommendation:** use standard resource inspection and prepared-request preview
-for their distinct meanings; retire the old completed-profile summary unless a
-specific Audita role summary remains useful. This avoids a parallel target resolver
-and aligns operator expectations.
-
-**Alternative:** retain a small role-to-resource summary alongside the full native
-commands. It helps transcript operators identify proposal and validation choices,
-but must clearly describe resource values rather than implying completed request
-settings. It adds maintenance and must not constrain native inspection.