Correct inspection framing and callback ownership documentation

This commit is contained in:
2026-10-07 18:27:39 +00:00
parent b45cbb3bb6
commit 7e67d1adfc
2 changed files with 27 additions and 14 deletions

View File

@@ -152,20 +152,22 @@ Owners: [initial.md](initial.md) and [implementation.md](implementation.md).
Owner: [cli.md](../cli.md).
- [ ] Correct aggregate YAML framing prose: scope comments can precede an inline
- [x] Correct aggregate YAML framing prose: scope comments can precede an inline
document-start marker; they are not always after the marker. Preserve the
native content and one YAML document per scope.
- [ ] Qualify engine acquisition/construction wording. Standard handlers invoke
- [x] Qualify engine acquisition/construction wording. Standard handlers invoke
registered inspection callbacks; the bundled helper acquires an engine through
the application loader. Direct callbacks retain their own implementation and
lifecycle rather than guaranteeing fresh engine construction.
- [ ] Describe the absence of execution/provider/credential operations as the
- [x] Describe the absence of execution/provider/credential operations as the
behavior of CommandKit's inspection path, preserving application callback
ownership of its effects.
- [ ] Correct cancellation attribution: cancellation can be detected at
- [x] Correct cancellation attribution: cancellation can be detected at
CommandKit's standard-handler boundaries as well as returned by PromptKit.
Preserve supported error identity and operational classification.
**Completion:** Corrected native marker/comment placement, qualified callback and engine lifecycle claims, and reconciled cancellation attribution.
## D-08: remove stale policy status statements
Owners: [testing.md](../policy/testing.md) and [oss.md](../policy/oss.md).