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

Update PromptKit notices and release notes

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-12 02:42:52 +00:00
parent ee038df530
commit def9b90b7c
3 changed files with 45 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/roadmap/implementation.md
View File

@@ -636,6 +636,30 @@ Check graph/notice consistency, pinned links, required texts, and module-local
release/attribution URLs. Validate prose using existing procedures. No publication
exercise or new release gate is needed for this adoption sprint.
**Completion evidence (2026-10-12)**
- The ckprompt module graph selects PromptKit v0.14.0, ConfigKit v0.7.1,
ReleaseKit v0.4.1, and `golang.org/x/tools` v0.49.0. PromptKit's Go module
origin confirms tag v0.14.0 resolves to the roadmap-pinned commit
`143c6e9b3a675872117b0471e2ff8bcb25055a54`. The graph's Go tools module
origin confirms v0.49.0 resolves to `18332fec72972efbb8ab9881984fec2d8cfc2b58`.
- Updated ckprompt attribution to the selected PromptKit release and source.
Inspected its released module's grant and LGPL license text; its copyright and
grant are unchanged, and it contains no separate NOTICE file. Reconciled the
stale Go tools attribution and included its applicable PATENTS notice. The
core ReleaseKit v0.4.0 declaration and notices remain unchanged; ckprompt's
graph selects v0.4.1. No module manifests or sums changed during workspace use.
- Updated the prepared ckprompt v0.1.0 note for native PromptKit comparison,
prompt/profile catalogs, named inspection, and callback narrowing, removing
the obsolete claim that PromptKit scopes lack comparison. The user confirmed
both ckprompt and ckconfig v0.1.0 tags are unpublished, so the prepared note
was eligible for revision. No release was published and no tag was changed.
- `GOTOOLCHAIN=local go list -m all` reported the graph above. `go mod download
-json` confirmed both pinned origins. Local Markdown link targets in the two
changed files exist, and `git diff --check -- '*.md' COPYRIGHT` passed.
- Complete repository, consumer, and isolated graph/import validation remains
assigned to Stage 12.
## Stage 12: Validate the complete end state and finish
**Outcome:** features work together, distribution boundaries remain intact, and