Clarify definition inspection loading

This commit is contained in:
2026-10-04 14:25:38 +00:00
parent 1c8494ec20
commit cd0811a49e
3 changed files with 36 additions and 14 deletions

View File

@@ -7,13 +7,14 @@ Reviewed on 2026-10-04 at
commits after `b1bb55a`. The runtime architecture matches the accepted
[feature roadmap](promptkit.md) and [implementation plan](implementation.md).
No runtime regression, missing framework capability, or newly imposed runtime
restriction was identified. Three low-priority documentation/help gaps need
correction. The first retains a loading guarantee that is incompatible with
restriction was identified. Three low-priority documentation/help gaps were
identified; their status and resolutions are recorded below. The first retained
a loading guarantee that was incompatible with
the deliberately selected full-source engine construction.
### R3: Correct The Definition-Inspection Loading Contract
Priority: P3 (low). Status: Open.
Priority: P3 (low). Status: Complete.
Locations: `docs/cli.md:208–224`; related orientation in
`docs/internal/adapters.md:49–56`. The CLI wording was retained in `b913ef0`
@@ -48,6 +49,14 @@ Acceptance: the owning contract and internal summary agree with the roadmap,
shared engine construction, and existing tests. Review the documentation diff
and links; no production-code change or new runtime guarantee is needed.
Resolution: the CLI contract now distinguishes full-source engine construction
from inspecting a selected definition, explains eager validation/content capture
and unused-definition failures, and retains the request-time exclusions. It
states that no prompt collection is mandatory but selected prompts are not
ignored. The internal summary links to that contract without promising a
separate no-prompt-loading path. Existing definition-inspection tests and
documentation link/diff checks passed; no production code changed.
### R4: Update The Composed-Example Description
Priority: P3 (low). Status: Open.