Record PromptKit adoption verification

This commit is contained in:
2026-11-17 00:53:48 +00:00
parent 3112068722
commit b1e7c1ee09
2 changed files with 14 additions and 1 deletions

View File

@@ -222,7 +222,14 @@ updated pinned references, and a version-matched release note.
## Stage 5 — Verify the assembled candidate and complete the records
Status — pending.
Status — completed. With Go 1.27.0 and the aligned three-module workspace,
`GOTOOLCHAIN=local go test ./...`, `go test ./integrations/ckconfig/...`, and
`go test ./integrations/ckprompt/...` all passed, including the composed
consumer. The independent ckprompt suite passed in Stage 3 with unchanged Go
and module inputs. Aggregate whitespace and Go formatting checks passed; local
documentation links and the selected upstream paths and fragments were reviewed.
The companion-YAML report records resolution. The subsequent cleanup commit
retires these completed records and links this evidence from future work.
1. Ensure the ignored local workspace includes root, ckconfig, and ckprompt,
following the developer guide. Run the following from the repository root

View File

@@ -1,5 +1,11 @@
# PromptKit companion YAML still exits with status 1 in v0.8.0
Status — resolved in the prepared ckprompt v0.9.0 candidate with PromptKit
v0.23.1. `TestPromptConstructorConfigurationOutcomes` exercises real malformed
companion construction through both integrations, including source and validation
reports and both comparison sides. `TestPromptConstructorFailurePrecedence`
checks operational and cancellation precedence and preserved causes.
The original Audita report covered invalid configuration passing through both
`ckprompt` and `ckconfig` v0.7.0. Retesting with both integrations at v0.8.0
confirmed that malformed main configuration now exits with status `2`. A