Select CommandKit v0.6.0 and close the release gate

This commit is contained in:
2026-11-09 14:18:34 +00:00
parent 97f6f48098
commit f1fced498a
2 changed files with 95 additions and 137 deletions

View File

@@ -4,7 +4,7 @@
**Status:** Agreed direction with proposed sequencing. Initial outlines only;
no implementation or dependency changes have been made for this plan. Resolve
the three remaining [open decisions](#open-decisions) in the listed order.
the two remaining [open decisions](#open-decisions) in the listed order.
## Objective and Document Ownership
@@ -81,7 +81,7 @@ For each friction point, record the desired outcome, whether the constraint is
library behavior or an Audita domain requirement, the proposed adaptation or
upstream request, and its acceptance evidence. Distinguish agreed decisions from
recommendations. The [CommandKit outline](commandkit.md#upstream-review-shared-debug-input-and-reporting-mode)
records the reporting request and resulting upstream capability plan.
records the released reporting capabilities and adoption evidence.
## Baseline and Selected Dependency Set
@@ -90,34 +90,32 @@ The reviewed application revision is
uses old-path ConfigKit v0.7.1 and PromptKit v0.14.0, with no CommandKit.
The source minimum is Go 1.26.0; the release runbook selects Go 1.26.8.
The following versions were reviewed as published and mutually aligned.
CommandKit and its integrations are review baselines; final adoption selection
is subject to the release gate below:
The following published versions are selected for adoption. CommandKit core and
both integrations use the reviewed v0.6.0 release set; its release gate is
satisfied as recorded below:
| Module | Version | Reviewed source commit |
| --- | --- | --- |
| `go.maximumdirect.net/configkit` | v1.1.0 | `191015e289d7f2b91abb9fdd9c4f2f5cf75b4de9` |
| `go.maximumdirect.net/promptkit` | v0.20.0 | `8ff9aa3efdc9f16b9d2729e0a29ea083eb3c3eaf` |
| `go.maximumdirect.net/commandkit` | v0.5.0 | `49f2d09ccde3d91d8c412a44ab934f223bef8fe6` |
| `go.maximumdirect.net/ckconfig` | v0.5.0 | `5c960532552037d38119941389e558f78bf73aad` |
| `go.maximumdirect.net/ckprompt` | v0.5.0 | `88ac6e76e4b164571f4172c01d7679c043b94a02` |
| `go.maximumdirect.net/commandkit` | v0.6.0 | `1613ff95cab60581de5d86f6e9e2a3cc091a44a0` |
| `go.maximumdirect.net/ckconfig` | v0.6.0 | `5ed947bd26bf2c6d70d1d748b693eca89f18d605` |
| `go.maximumdirect.net/ckprompt` | v0.6.0 | `1ca660e35fb58fc0dc318e411afb6e3631a40ef1` |
The integration tags are `integrations/ckconfig/v0.5.0` and
`integrations/ckprompt/v0.5.0` in CommandKit's repository. Use the
[corrected module selection guide](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/88ac6e76e4b164571f4172c01d7679c043b94a02/docs/consumers/guide.md#module-selection);
the core tag's guide predates integration publication. The former missing
`AdaptDiagnostics` blocker is resolved. Changes to these reviewed targets need
an ordinary compatibility review, not an assumption that later releases are
interchangeable.
The integration tags are `integrations/ckconfig/v0.6.0` and
`integrations/ckprompt/v0.6.0` in CommandKit's repository. Use the
[released module selection guide](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/1ca660e35fb58fc0dc318e411afb6e3631a40ef1/docs/consumers/guide.md#module-selection).
The integration updates retain ConfigKit v1.1.0 and PromptKit v0.20.0 and require
Go 1.27. Changes to these selected versions require an ordinary compatibility
review rather than assuming later releases are interchangeable.
**CommandKit release gate:** adoption implementation waits for a published core
version providing both the independent shared debug binding for capture and the
resolved reporting-mode accessor for quiet destination validation, as required by
the [CommandKit outline](commandkit.md#adoption-gate-released-debug-binding-and-reporting-mode-access).
Either API alone is insufficient. Replace the reviewed v0.5.0
core target with that release and record compatible released integration versions
and exact source revisions after review. No replacement version is selected yet;
this is [open decision 1](#1-commandkit-released-dependency-set).
**CommandKit release gate — satisfied:** the published v0.6.0 core provides both
the independent shared debug binding for capture and the resolved reporting-mode
accessor for quiet destination validation. The matching released integrations
were reviewed together. The [CommandKit outline](commandkit.md#adoption-gate-released-debug-binding-and-reporting-mode-access)
records the API contract and review evidence. The selected release set removes
the upstream availability blocker; Audita implementation and acceptance remain
pending under the sequence below.
ReleaseKit v0.9.0 at `go.maximumdirect.net/releasekit` is also a required target.
The library graph already brings in that version, but Audita's direct tool still
@@ -153,13 +151,11 @@ for Audita's complete release workflow.
providers. Avoid a permanent replacement or dual configuration engine.
Identify and remove local code made redundant by the adopted facilities as
part of each migration, rather than leaving cleanup as an unspecified follow-up.
4. **After the CommandKit release gate opens, integrate core and both standard
integrations.** Confirm both required public APIs are published and
select the released dependency set as described above before starting this
implementation stage. Complete the previously designed operator interface,
adapting Audita domain handlers and resolving upstream issues. Earlier design
and independent library work may proceed while waiting. This remains required
scope for the next major release.
4. **Integrate the selected CommandKit core and both standard integrations.**
The upstream release gate is satisfied. Complete the designed operator
interface using the selected v0.6.0 set, adapting Audita domain handlers and
verifying the assembled application. Resolve concrete new integration gaps
upstream. This remains required scope for the next major release.
5. **Add stage-specific glossary inputs.** After all four library adoptions,
complete the [glossary-stage roadmap](glossary-stages.md). Use the adopted
configuration and CLI conventions to compose reusable glossary assets through
@@ -186,7 +182,7 @@ implementation stage is ready.
## ReleaseKit Adoption Work
The concrete workflow and validator selection remain
[open decision 2](#2-releasekit-workflow-and-validator-selection).
[open decision 1](#1-releasekit-workflow-and-validator-selection).
1. Review v0.9.0's supported release workflow, validators, and version integration.
Inventory Audita's launcher, scripts, CI responsibilities, and local release
@@ -220,8 +216,12 @@ contracts. Disposable checks using Go 1.27.3 established:
- CLI parent overrides do not rerun ConfigKit inheritance. PromptKit same-ID
replacement drops omitted provider settings; distinct native inheritance can
retain them. Profile null endpoints permit backend fallback.
- Tagged CommandKit core, ckconfig, and ckprompt suites pass independently with
released dependencies, `GOWORK=off`, and no local replacements.
- Tagged CommandKit core, ckconfig, and ckprompt v0.6.0 suites pass independently
with released dependencies, `GOWORK=off`, and no local replacements.
- A separate consumer of all three published v0.6.0 modules passes 33 cases
covering debug capture, reporting-mode ordering, aliases, and quiet transcript
destination validation. The assembled graph retains the selected ConfigKit and
PromptKit versions and brings in ReleaseKit v0.9.0.
These are review results, not implementation acceptance. They involved no live
provider calls and do not prove migrated Audita behavior or cross-platform
@@ -251,31 +251,10 @@ and retain shared license texts. Do not copy upstream policy inventories.
## Open Decisions
Work through these decisions in order. Recommendations below remain proposals;
the existing adoption principles and CommandKit release gate remain in force.
the existing adoption principles remain in force. CommandKit release selection
is resolved in the dependency set above.
### 1. CommandKit Released Dependency Set
Select and record published core, ckconfig, and ckprompt versions and exact
source revisions after verifying the required independent debug binding and
resolved reporting-mode accessor. The roadmap has not yet established that a
released set satisfies both requirements; historical review evidence does not
open the gate.
**Recommendation:** select a published core release that passes the required
behavior checks, retaining the reviewed integration versions if they remain
compatible. Verify the assembled dependency graph and capture/quiet-destination
cases before recording the gate as satisfied. This minimizes unrelated migration
scope while adopting the required public APIs. If no qualifying release is
available, keep the implementation gate closed and continue independent planning
and library work.
**Alternative:** adopt a newer compatible released set of core and both
integrations together. This may incorporate useful fixes and simplify alignment
with current upstream guidance, but requires reviewing additional behavior and
API changes. Neither option permits unreleased replacements, private-state
inspection, or duplicate argument parsing.
### 2. ReleaseKit Workflow and Validator Selection
### 1. ReleaseKit Workflow and Validator Selection
Inventory the current launcher, scripts, CI responsibilities, version integration,
and local release checks against ReleaseKit v0.9.0. Select the concrete workflow,
@@ -297,9 +276,9 @@ upstream except for justified domain checks. This can fit concrete CI needs but
retains local sequencing to maintain; prefer an upstream enhancement for a
reusable gap rather than permanently duplicating release machinery.
### 3. Output-Failure Behavior
### 2. Output-Failure Behavior
Resolve the [output-failure decision](commandkit.md#output-failure-behavior) in
the CommandKit roadmap after the two selections above. That document owns the
the CommandKit roadmap after the ReleaseKit selection above. That document owns the
recommendation, alternative, and behavior contract. This decision completes the
remaining write-failure detail before implementing the output/reporting boundary.