Document value access and focused inspection

This commit is contained in:
2026-11-21 04:16:46 +00:00
parent 37f38f3e54
commit 7a9ce01064
10 changed files with 78 additions and 10 deletions

View File

@@ -1,6 +1,6 @@
# Implementation plan: typed result values and focused inspection
Status: implementation in progress; Stages 1–8 complete.
Status: complete; all stages implemented and validated.
## Scope and working instructions
@@ -309,6 +309,8 @@ or claim completion of real PromptKit integration.
## Stage 9 — Document the implemented boundary and validate the sprint
**Complete.**
Update documentation only once the corresponding behavior exists:
- Declaration comments own signatures, nil/absence behavior, ordinary aliasing,

View File

@@ -1,6 +1,7 @@
# Typed value access and focused inspection from a result
Status: agreed feature scope; OD-1 through OD-5 settled; not implemented.
Status: implemented; OD-1 through OD-5 settled. See the current
[configuration contract](../config.md) and declaration comments for behavior.
Baseline: v1.3.0, commit `652ddb6`.
## Purpose and baseline
@@ -11,12 +12,12 @@ checks its public settings type, and constructs its runtime objects. Libraries
can also offer inspection focused on their section. Section names remain library
conventions, not ConfigKit reserved keys.
Today, [Result.Config](../../lifecycle.go) supplies trusted typed values, but its
generic root type prevents a library from selecting a field without knowing the
At the baseline, [Result.Config](../../lifecycle.go) supplied trusted typed values, but its
generic root type prevented a library from selecting a field without knowing the
application type or adding its own traversal. Existing metadata and
[source contexts](../../resource_context.go) already support field provenance and
resource lookup. Existing inspection and comparison operate on completed-load
snapshots, but there is no reusable subtree reporting view. Redacted inspection
resource lookup. Baseline inspection and comparison operated on completed-load
snapshots, but there was no reusable subtree reporting view. Redacted inspection
snapshots are not execution inputs.
PromptKit has accepted the typed-value direction. The subsequently agreed