Add PromptKit configuration scope

docs/cli.md

@@ -102,6 +102,11 @@ runtime context or acquire configuration. It reports the intersection between
 declared scope capabilities and installed handlers, so an operation is listed
 only when the corresponding command is available.
 
+Applications can register the `promptkit` scope with `NewPromptKitScope` to
+expose PromptKit engine configuration through these handlers. This configuration
+scope can be installed without registering PromptKit prompt or profile
+definition commands.
+
 ### Validate configuration
 
 `config validate` loads and validates the selected scope. The default scope is

docs/development.md

@@ -6,8 +6,8 @@ declarations, an instance-owned registry, a Cobra-backed routing and parsing
 adapter, public `App.Execute` coordination, and generated help/version commands.
 Configuration suite registration, scope discovery, ConfigKit integration,
 validation, native effective YAML display, source inventory, and path
-explanation reports are implemented; other configuration and PromptKit
-operations remain pending. The
+explanation reports, and PromptKit engine configuration inspection are
+implemented; named prompt/profile inspection remains pending. The
 [README](../README.md) provides project orientation; the
 [documentation policy](policy/documentation.md#canonical-ownership) assigns
 canonical documentation owners.

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Initial CommandKit implementation plan
 
-Status: implementation underway; Stages 1-11 complete and Stages 12-14 pending.
+Status: implementation underway; Stages 1-12 complete and Stages 13-14 pending.
 
 Date: 2026-10-07.
 
@@ -716,7 +716,7 @@ and CLI reference describe the feature.
 
 ## Stage 12: integrate the PromptKit configuration scope
 
-**Status:** pending. **Prerequisite:** Stage 11.
+**Status:** complete. **Prerequisite:** Stage 11.
 
 ```go
 func NewPromptKitScope[C any](
@@ -744,6 +744,10 @@ all display with app first/promptkit second, configuration-only installation,
 caller context/selection propagation, and metadata discovery without engine load.
 Fixtures do not depend on provider services or sibling repository runtime files.
 
+**Completion evidence:** `promptkit_scope_test.go` exercises a real in-memory
+PromptKit engine, native reports, aggregate order, lazy discovery, and preserved
+PromptKit/ConfigKit error identities. `go test ./...` passes.
+
 ## Stage 13: implement named prompt/profile inspection
 
 **Status:** pending. **Prerequisite:** Stage 12.