Set inspection boundary for application-specific fields

This commit is contained in:
2026-11-21 04:18:22 +00:00
parent d3523000bf
commit 2a726d60ff

View File

@@ -240,11 +240,14 @@ such as output contracts. Maps beneath application-specific keys retain ConfigKi
ordinary dynamic-value behavior. Standalone and application-owned loading use the
same settings model.
**Open decision:** whether `InspectPrompt`, `InspectProfile`, and `InspectBackend`
also expose the resource's additional fields, and how those fields appear in their
public reports. Configuration inspection already includes them. Settle resource
reporting separately; acceptance of application fields does not by itself require
adding them to execution objects.
**Accepted inspection boundary:** retain application-specific fields in the
resolved configuration and ConfigKit-backed `InspectConfiguration()` reports.
`InspectPrompt`, `InspectProfile`, and `InspectBackend` continue to report
PromptKit-understood fields and omit application-specific fields. This keeps
resource reports simple: no additional metadata storage, copying, redaction
integration, or public report fields are needed for these extensions. Applications
can access their fields through the resolved configuration and configuration
inspection; execution objects need not carry them.
### Focused Configuration Inspection
@@ -390,6 +393,8 @@ compatibility resolver.
configuration inspection, including application-defined sensitivity. They remain
available to application validation and do not enter provider requests merely
because they appear on a resource definition.
- Resource inspection omits application-specific fields while configuration
inspection retains them under ConfigKit's native sensitivity rules.
- Engine independence from later caller mutation of settings, including nested
maps and slices; trusted lookup does not replace redacted inspection.
- Resource listings, resource reports, and load diagnostics through PromptKit's
@@ -402,9 +407,9 @@ compatibility resolver.
are excluded while ancestor differences remain; comparison works across different
application root types selecting the same scope.
The product direction includes focused inspection, removal of resource-version
validation, and application-specific fields. Exposure of those additional fields
through resource inspection remains open as described above.
The product direction, including focused inspection, removal of resource-version
validation, and the configuration-only inspection of application-specific fields,
is settled. No product decisions remain before implementation planning.
Concrete public API shapes, diagnostic forwarding, and verification of the actual
PromptKit integration are implementation-planning work.