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

Reconcile module docs and release materials

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 02:06:06 +00:00
parent 18e81a5579
commit d2b5b0f3a8
45 changed files with 2380 additions and 362 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Implement the optional integration modules and captured registration API
Status: implementation in progress. Stages 1 through 14 are complete; subsequent work follows the ordered roadmap.
Status: implementation in progress. Stages 1 through 15 are complete; subsequent work follows the ordered roadmap.
Execute the stages in order. Each stage is sized as a separate Luna coding-agent
assignment. This document authorizes no publication or changes to sibling
repositories.
@@ -751,10 +751,21 @@ its own usable licensing and release material.
use the reported exact endpoint, full tag, and annotated tag object. Successful
source-tag publication remains release completion.
**Completion evidence:** inspect affected current docs, examples, local links,
module-local licensing contents and source links, note titles/full-tag footers,
and policy/procedure agreement. Future tag URLs need not resolve. Release preparation
is complete without claiming that unpublished dependencies already resolve remotely.
**Completion evidence — complete:** the three package GoDoc surfaces and current
consumer, CLI, internal, and development guides describe the captured factories,
module ownership, retained errors, input/state timing, and explicit installation.
Each integration has a module README, module-local `COPYRIGHT`/`LICENSE`, a
scoped attribution document, and local standard license texts. The LGPL/GPL
texts and copied license texts match the root texts; upstream entries use pinned
source revisions. The root attribution now identifies ReleaseKit v0.4.0 and its
direct tool dependencies. Release policy and procedure agree on independent
module versions, full nested tags, module-local note paths and shared files,
core-to-ckconfig-to-ckprompt publication order, dependency preparation, and the
selected-module suite. The three notes have the required titles, compatibility
explanations, and immutable full-tag footers. Local links and whitespace checks
pass for Markdown prose; standard license texts remain byte-for-byte copies,
including upstream formatting. No future CommandKit version is claimed to be
available remotely, and no tag, push, or publication was performed.
## Stage 16: Validate the complete end state and finish the sprint