Add captured framework configuration inspection

This commit is contained in:
2026-10-04 12:37:02 +00:00
parent c2e2b74f83
commit 2ba2ce1b91
4 changed files with 347 additions and 3 deletions

View File

@@ -3,8 +3,8 @@
## Status, Baseline, And Authority
Planned on 2026-10-04 against Scriptorium
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–8 are complete; stages
9–13 are pending.
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–9 are complete; stages
10–13 are pending.
This plan is for a Luna coding agent: implement the stages in sequential order,
normally one stage per implementation prompt. The
[feature roadmap](promptkit.md) owns the target state, scope, and confirmed
@@ -522,7 +522,16 @@ definition plumbing are protected at the actual application boundary.
## Stage 9: Add Captured Framework Validate, Show, And Sources Commands
Status: Pending. Depends on Stage 8.
Status: Complete. `inspect configuration validate`, `show`, and `sources` now
load application settings, construct one engine, and use its captured public
inspection view without preparing a request or resolving credentials. Effective
output remains PromptKit's native YAML; source JSON uses the selected DTO fields
and preserves imported locations and source order. Tests cover source-free and
credential-required configurations, invalid final definitions, source layering
and imports, stdout/stderr separation, positional rejection, and writer
failures. Focused inspection tests, `go test ./...`, `go test -race ./...`,
`go vet ./...`, the CLI build, `gofmt`, and `git diff --check` pass. Literal-path
explanations and their redaction coverage remain for Stage 10.
Files: `internal/adapter/cli/inspect.go`, a small
`framework_config.go` and `framework_config_test.go` in that package.