Record adoption validation and release follow-up

This commit is contained in:
2026-11-21 19:50:40 +00:00
parent 2a086b6389
commit e70a0ef301
3 changed files with 41 additions and 7 deletions

View File

@@ -1,6 +1,7 @@
# Future work
Status — optional shell validation and future capability proposals.
Status — integration release coordination, optional shell validation, and future
capability proposals.
No delivery dates are selected here.
## Purpose and authority
@@ -37,6 +38,23 @@ govern any future implementation. The [CLI reference](../cli.md), public GoDoc,
and [consumer guide](../consumers/guide.md) own implemented behavior. Retaining
an idea here does not select its syntax, API, priority, or delivery date.
## Pending integration release coordination
The ConfigKit v1.4.0 and PromptKit v0.24.0 adoption is implemented locally;
publication remains separate. Follow the [release procedure](../release.md)
and obtain the required publication authorization. Prepare and release ckconfig
v0.10.0 first. Then select that actual release in ckprompt, tidy with real
checksums, update matching-version attribution, and run ckprompt's independent
default suite before preparing its v0.11.0 release. Core remains v0.7.0 for this
adoption. Candidate notes and planned versions must be checked again at release
time. Hosted delivery is separately authorized.
The current ckprompt checkout still requires published ckconfig v0.9.0, which
lacks the new path-reader API. Its aligned workspace and isolated local-replace
tests passed; those checks do not establish an independent build against the
published requirement. See the [implementation record](implementation.md) for
the validation evidence and upstream missing-file error-identity limitation.
## Optional verification
### Optional shell completion validation