Document configuration comparison behavior

This commit is contained in:
2026-10-11 22:00:22 +00:00
parent f0853d1000
commit 8b46e12da7
11 changed files with 170 additions and 123 deletions

View File

@@ -1,6 +1,6 @@
# Implement ConfigKit adoption and configuration comparison
Status: implementation in progress; Stages 1–10 are complete.
Status: implementation in progress; Stages 1–11 are complete.
## Scope and authority
@@ -545,9 +545,20 @@ canonical owners, while future/deferred work stays clearly separate.
symbols. Keep accepted ADR decision text unchanged; presentation details
remain in CLI/API owners rather than returning to ADRs.
**Completion evidence:** current operator/API/consumer owners agree with the
implemented behavior; no stale four-operation convenience claims, text-diff
promises, or deferred markers for delivered ConfigKit comparison.
**Completion evidence — complete:** ckconfig GoDoc now describes all five
operations, paired input lifetimes, shared state, native records, diagnostics,
and supported error identity. The ckconfig README, CLI reference, consumer guide,
internal overview, development examples, and maintained example READMEs describe
current ConfigKit comparison behavior. The CLI owner covers independent right
inheritance and supplied presence, native effective-value semantics, reduced
safe YAML categories, null/deletion, concealed regions, empty output, root
ambiguity, diagnostics, and outcome delivery. The ConfigKit feature roadmap now
records implementation status; the deferred record no longer carries ConfigKit
comparison as pending work and retains PromptKit comparison, independent per-side
domain selectors, catalogs, and other unselected ideas. The accepted ADRs were
left unchanged. Local Markdown targets/fragments and copied commands were
reviewed; a local link check and `git diff --check -- '*.md'` passed. `go doc`
was inspected for the exported comparison API.
## Stage 12: Reconcile manifests, notices, and pending integration release notes