Record configuration handoff integration results
This commit is contained in:
@@ -149,8 +149,6 @@ The proposed constructor can consume a PromptKit-owned interface such as:
|
||||
```go
|
||||
type Configuration interface {
|
||||
Value(configkit.Path) (any, bool)
|
||||
Metadata() configkit.Metadata
|
||||
SourceContext(string) (configkit.ResourceContext, bool)
|
||||
InspectSubtree(configkit.Path) (configkit.Inspection, bool)
|
||||
Diagnostics() []configkit.Diagnostic
|
||||
}
|
||||
@@ -161,6 +159,8 @@ resources using native metadata and source contexts. Effective field origins are
|
||||
authoritative; do not recover a missing effective location from historical evidence.
|
||||
A serialized section loaded again is not an equivalent handoff.
|
||||
Retain the inspection view selected at `/promptkit` for configuration reporting.
|
||||
That view also supplies metadata and source contexts during capture, so the
|
||||
constructor interface need not repeat those methods.
|
||||
Load diagnostics come from the original result's `Diagnostics()` method; the
|
||||
inspection view does not supply that method. Retain and forward those records
|
||||
through PromptKit's configuration inspection facade. Concrete PromptKit API names
|
||||
@@ -318,6 +318,12 @@ adding a second load.
|
||||
|
||||
### Validate The Pattern Against PromptKit
|
||||
|
||||
The actual PromptKit prototype check is complete; see the
|
||||
[integration assessment](configuration-integration-check.md) for evidence,
|
||||
the smaller three-method handoff interface, and remaining implementation work.
|
||||
The checklist below records what the check needed to establish and guides
|
||||
implementation coverage; production implementation is not complete.
|
||||
|
||||
ConfigKit's released APIs and maintained
|
||||
[one-library](../../../ConfigKit/examples/consumers/result_component.go) and
|
||||
[two-library](../../../ConfigKit/examples/consumers/result_composition.go) examples
|
||||
@@ -328,12 +334,13 @@ source context without another load.
|
||||
The release review passed PromptKit's full test suite against the published
|
||||
v1.4.0 module using a temporary dependency file and Go 1.27.4. ConfigKit's focused
|
||||
lookup, inspection, comparison, history, and component-example checks also passed.
|
||||
This establishes compatibility with PromptKit's existing implementation; the new
|
||||
PromptKit handoff remains to be implemented and verified.
|
||||
This establishes compatibility with PromptKit's existing implementation. The
|
||||
isolated prototype now also verifies the proposed handoff pattern; the production
|
||||
handoff remains to be implemented.
|
||||
|
||||
Prepare an actual PromptKit prototype demonstrating the typed registration helper,
|
||||
one application-owned load, and whole-result engine construction. Also exercise
|
||||
the standalone convenience path through the same rules. Focus on these checks:
|
||||
The prototype demonstrates the typed registration helper,
|
||||
one application-owned load, and whole-result engine construction. It also exercises
|
||||
the standalone convenience path through the same rules. The checks cover:
|
||||
|
||||
1. **Public settings and callback composition.** Define a supported public settings
|
||||
model suitable for ConfigKit decoding; existing typed source helpers are not
|
||||
|
||||
Reference in New Issue
Block a user