Explain framework configuration paths safely
This commit is contained in:
@@ -3,8 +3,8 @@
|
||||
## Status, Baseline, And Authority
|
||||
|
||||
Planned on 2026-10-04 against Scriptorium
|
||||
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–9 are complete; stages
|
||||
10–13 are pending.
|
||||
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–10 are complete; stages
|
||||
11–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
|
||||
@@ -565,7 +565,19 @@ scope with application inspection or altering existing presentation contracts.
|
||||
|
||||
## Stage 10: Add Literal-Path Explanations And Prove Scoped Redaction
|
||||
|
||||
Status: Pending. Depends on Stage 9.
|
||||
Status: Complete. `inspect configuration explain` now requires an explicitly
|
||||
provided JSON Pointer, accepts the empty root, parses with ConfigKit, detects
|
||||
unknown paths before writing, and delegates explanations to the captured
|
||||
PromptKit inspection view. Tests cover inherited and overlaid history, escaped
|
||||
slash IDs, dotted keys, root output, malformed/unknown paths, native writer
|
||||
errors, effective and historical `token`/`password` redaction, visible
|
||||
environment-reference names and ordinary values, and the unchanged disclosure
|
||||
behavior of profile inspection and prepared output. Application validation
|
||||
remains independent of invalid framework definitions, while framework
|
||||
validation rejects them without a partial report. Focused inspection tests,
|
||||
`go test ./...`, `go test -race ./...`, `go vet ./...`, the CLI build,
|
||||
`gofmt`, `git diff --check`, and all four operations against
|
||||
`examples/config.yml` pass.
|
||||
|
||||
Files: framework inspection parser/handler/tests from Stage 9.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user