Migrate PromptKit validation and smoke reporting

This commit is contained in:
2026-10-26 03:35:39 +00:00
parent 4ace616bc2
commit 401232a1b0
6 changed files with 158 additions and 113 deletions

View File

@@ -1,6 +1,6 @@
# Invocation reporting implementation plan
Status: Stages 1–14 complete. Stage 15 is next.
Status: Stages 1–15 complete. Stage 16 is next.
## Objective and authority
@@ -569,7 +569,7 @@ Stage 20 will validate the assembled module.
## Stage 15: Migrate request validation and smoke commands
Status: pending.
Status: complete.
Primary files:
[validation_command.go](../../integrations/ckprompt/validation_command.go) and
@@ -599,6 +599,15 @@ bindings, reports alongside errors, diagnostic ordering, cancellation,
render/write failures, and quiet semantics. Test CommandKit coordination,
not whether PromptKit's validation or smoke checks implement their domain rules.
Concrete request validation and PromptKit smoke commands now submit passive
messages through the reporter and render confirmation, native, and aggregate
reports inside managed output. Smoke reports remain available alongside
operation failures, with native explanations and causes retained separately;
aggregate collection order and shared input/state lifetimes remain covered.
`GOTOOLCHAIN=local go test -count=1 .` passes in `integrations/ckprompt`. The
module-wide `go test ./...` reaches and passes that package but cannot compile
`examples/composed`, whose legacy API callers are scheduled for Stage 17.
## Stage 16: Maintain a core reporting consumer
Status: pending.