base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Adopt ConfigKit v0.7.1 in integrations

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 21:33:22 +00:00
parent e8b44ca765
commit c883c64be9
5 changed files with 57 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/roadmap/implementation.md
View File

@@ -78,9 +78,20 @@ graph and an honest distinction between local and published dependency evidence.
Fix actual upstream API incompatibilities within this scope, if any. Do not
compensate for a test that independently freezes a superseded upstream detail.
**Completion evidence:** reviewed manifest/sum changes; upgraded integration
graph selections; existing inspection and PromptKit suite results. Record any
unpublished dependency limitation explicitly.
**Completion evidence — complete:** both integration modules now require
ConfigKit v0.7.1, with Go 1.26.0 and PromptKit v0.12.0 unchanged. The pinned
release notes and comparison contract were reviewed at source commit
`6fffde4af8f31f99d3ee295c426eb3234cb0fb77`; they confirm the YAML dependency
and runtime/API remain unchanged and the upstream tool moves to ReleaseKit
v0.4.1. Normal module files contain no filesystem replacements. Real checksum
entries for released dependencies were generated through temporary paired
module files with local replacements only for unpublished CommandKit modules;
no CommandKit version checksums were added. Both integration suites pass with
the local workspace and with workspace-off temporary manifests. Each integration
graph selects ReleaseKit v0.4.1. The root module still declares ReleaseKit
v0.4.0, and no upstream API incompatibility was found by the suites. These
workspace-off checks validate local source wiring, not availability of the
unpublished CommandKit versions.
## Stage 2: Add the comparison capability and captured provider contract