Document ConfigKit adoption
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# ConfigKit v1.1.0 adoption implementation plan
|
||||
|
||||
Status: Stages 1–3 complete; Stages 4–6 are not started.
|
||||
Status: Stages 1–4 complete; Stages 5–6 are not started.
|
||||
|
||||
This plan is for a Luna coding agent implementing the selected
|
||||
[ConfigKit adoption target](configkit-v1.1.0.md). Follow Stage 1 through Stage 6
|
||||
@@ -187,6 +187,10 @@ classifies sensitive data correctly.
|
||||
|
||||
## Stage 4: Update current guidance and prepare the release note
|
||||
|
||||
**Completed.** Current guidance describes the new source report, consumer and
|
||||
toolchain migration, and temporary ckprompt mismatch. The v0.3.0 candidate
|
||||
note is prepared; published notes remain unchanged.
|
||||
|
||||
1. Update ckconfig README, GoDoc, and `examples/simple/README.md` for the new
|
||||
dependency identity and Go minimum, and the planned ckconfig v0.3.0 with
|
||||
core v0.3.0. Keep package/provider usage consistent with actual code.
|
||||
|
||||
Reference in New Issue
Block a user