Document configuration outcomes and release handoff

This commit is contained in:
2026-11-16 18:08:33 +00:00
parent 20d2924338
commit 8a22dd6a4f
6 changed files with 109 additions and 28 deletions

View File

@@ -1,6 +1,7 @@
# Invalid configuration outcome implementation
Status — ready for implementation. Stages are pending.
Status — complete. Release coordination remains in the
[future work handoff](future.md#configuration-outcome-release-handoff).
## Sprint scope and baseline
@@ -290,7 +291,15 @@ classification broadening.
## Stage 5 — Update documentation, validate, and record release coordination
Status — pending.
Status — complete. Updated the CLI and consumer contracts, development
guidance, ckconfig v0.8.0 release note, and dependency-first release handoff.
With Go 1.27.0 and a temporary writable Go build cache, the independent ckconfig
suite passed with `GOWORK=off GOTOOLCHAIN=local GOPROXY=off go test
-mod=readonly ./...`. In the aligned workspace, the three prescribed
`GOTOOLCHAIN=local GOPROXY=off go test -mod=readonly` commands passed for
`./...`, `./integrations/ckconfig/...`, and `./integrations/ckprompt/...`.
Reviewed the diff, local Markdown links and fragments, and whitespace. The
independent ckprompt build remains pending publication and dependency alignment.
Update the implemented CLI contract in `docs/cli.md`, including the outcome
table and affected load-failure wording in configuration comparison, inspection,