Complete the ConfigKit v0.3.0 adoption

docs/internal/overview.md

@@ -53,11 +53,12 @@ adapters. The normative rules for these relationships remain in
 [Architecture](../policy/architecture.md).
 
 Command execution normalizes one private dependency value per invocation.
-Configuration reads, secret-directory reads, remote downloads, object-store
-construction, and restore phase functions use that value throughout the
-command. Public command entry points supply production defaults, while focused
-tests replace only the external or sequencing boundary they exercise without
-mutating package state.
+Pipeline configuration-path discovery, configuration reads, secret-directory
+reads, remote downloads, object-store construction, and restore phase functions
+use that value throughout the command. Public command entry points supply the
+canonical discovery and production defaults, while focused tests may provide
+invocation-owned discovery candidates or replace only the external or sequencing
+boundary they exercise without mutating package state.
 
 Pipeline execution and `session plan` share the same inclusive contiguous-range
 model and the same pure pre-execution decision over recorded status, force, and

docs/roadmap/configkit-v0.3.0.md

@@ -1,6 +1,6 @@
 # Adopt ConfigKit v0.3.0
 
-Status: Accepted — implementation pending
+Status: Implemented — 2026-09-16
 
 Execution order and stage acceptance checks belong to the
 [implementation plan](implementation.md). This roadmap owns scope, policy, and

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # ConfigKit v0.3.0 Implementation Plan
 
-Status: Not started
+Status: Complete — 2026-09-16
 
 Implement the [feature roadmap](configkit-v0.3.0.md) in sequential stage order.
 Each stage is a bounded assignment for a gpt-5.6-terra coding agent. Mark it
@@ -168,7 +168,30 @@ Acceptance:
 
 ## Stage 3 — Document and verify the completed adoption
 
-Status: Not started
+Status: Complete — 2026-09-16
+
+Completion: Narratio now uses released ConfigKit v0.3.0. The implementation
+adds invocation-local pipeline discovery for isolated command tests and adjusts
+the integer party-version expectation to Narratio's unsupported-version
+diagnostic; it requires no operator configuration migration. The internal
+command-dependency inventory documents the new seam. No unreleased Narratio
+release note exists, and the immutable v2.0.0 note was not changed.
+
+Checks:
+
+- `GOWORK=off go mod tidy -diff` — pass.
+- `GOWORK=off go mod verify` — pass.
+- `GOWORK=off go test -count=1 ./...` — pass.
+- `GOWORK=off go test -race -count=1 ./...` — pass.
+- `GOWORK=off go vet ./...` — pass.
+- `GOWORK=off go build ./...` — pass.
+- `GOWORK=off go test ./internal/doccheck` — pass.
+- `GOWORK=off go test ./internal/config -run '^TestExamplesLoadAndValidate$'` — pass.
+- `git diff --check` — pass.
+- `gofmt -l` on the changed Go files — no output.
+- `scripts/build-release-assets.sh v0.0.0-test OUTPUT_DIR` — pass with
+  Linux amd64, Linux arm64, and macOS arm64 assets. The macOS result is
+  cross-build evidence only, not native runtime validation.
 
 Purpose: Establish a clean, reproducible handoff for later release preparation.