Adopt ReleaseKit module publishing

This commit is contained in:
2026-10-11 01:54:04 +00:00
parent e89cc2220f
commit 18e81a5579
9 changed files with 254 additions and 131 deletions

View File

@@ -1,6 +1,6 @@
# Implement the optional integration modules and captured registration API
Status: implementation in progress. Stages 1 through 13 are complete; subsequent work follows the ordered roadmap.
Status: implementation in progress. Stages 1 through 14 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.
@@ -687,10 +687,16 @@ required.
exercise to include a nested module with a distinct prefixed tag and module
note. Default tests remain offline and do not publish.
**Completion evidence:** ordinary launcher tests pass without network/publication.
The optional disposable exercise demonstrates one root and one nested module;
run it only when its dependencies are prepared. A sibling checkout or ad hoc
ReleaseKit source build is not the selected consumer tool.
**Completion evidence — complete:** offline launcher tests pass for all three
selectors, usage failures before bootstrap, paths containing spaces, exact
profile/module routing, delegated environment settings, and delegated exit
statuses. The opt-in disposable exercise passed for both a root module tag and
the prefixed `integrations/ckconfig/v0.0.1` tag with its module release note;
the endpoint guard also stopped a later publication before validation. ReleaseKit
v0.4.0 was resolved from its tagged module, and the workspace-off root module
graph contains no ConfigKit or PromptKit dependency. No publication occurred.
A sibling checkout or ad hoc ReleaseKit source build is not the selected
consumer tool.
## Stage 15: Reconcile documentation, licensing, and release preparation