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

Reconcile integration dependency notices

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 22:03:58 +00:00
parent 8b46e12da7
commit 976b55309c
6 changed files with 44 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/roadmap/implementation.md
View File

@@ -590,9 +590,20 @@ notices without altering core's release tool or publishing a release.
copy workspace-selected dependency versions into core attribution. Verify
the normal manifests have no disposable local replacements or invented sums.
**Completion evidence:** reviewed integration notices and pending release notes,
normal distributed manifests/sums reflecting actual resolved external dependencies,
and unchanged root maintainer tool declaration, launcher, and release profiles.
**Completion evidence — complete:** module-local ConfigKit notices now identify
v0.7.1 at `6fffde4af8f31f99d3ee295c426eb3234cb0fb77`; both integration graphs
select ReleaseKit v0.4.1 at `2d5a8110c61e31daf8698766114ae305d0e0e469`, with
matching source-pinned notices and the existing Goldmark and Go modules entries.
The root attribution now reflects only the core module graph, which still selects
ReleaseKit v0.4.0. Both integration manifests and sums match their tidy
workspace-off alternate files with only local CommandKit replacements; each
retains its intended versioned CommandKit requirements and contains no local
replacement or CommandKit checksum. Both integration v0.1.0 tags were confirmed
unpublished before their release notes were updated for ConfigKit adoption and
comparison availability; PromptKit comparison remains explicitly unsupported.
Module-local links resolve, release footers use each integration's tag prefix,
and the core maintainer tool declaration, launcher, and release profiles are
unchanged.
## Stage 13: Validate the complete sprint and finish