Verify constructor failure precedence

This commit is contained in:
2026-11-17 00:51:51 +00:00
parent 70b3818351
commit 49fee9f8ee
3 changed files with 65 additions and 2 deletions

View File

@@ -132,7 +132,14 @@ CommandKit outcomes, identity, diagnostics, reports, and comparison-side context
## Stage 3 — Preserve failure precedence and native report compatibility
Status — pending.
Status — completed. The focused constructor and preparation tests and
`GOWORK=off GOTOOLCHAIN=local go test ./...` passed against published
dependencies. Real missing-schema and malformed-YAML constructor failures
retain their causes; mixed operational and cancellation causes and pre-canceled
invocations select status 1. The prepared report retains `ParentRunID`.
Both native request adapters forward whole builder results; upstream preparation
and validation use the supplied context, while execution owns notifications and
operation timeouts.
1. Add `TestPromptConstructorFailurePrecedence` alongside Stage 2's tests.
Exercise a representative catalog command and `config show --scope=promptkit`