eric/narratio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 27 Wiki Activity

Complete the ConfigKit v0.3.0 adoption

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-16 04:33:19 +00:00
parent e08de98ae6
commit cd75bf6d5a
3 changed files with 32 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/internal/overview.md
View File

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

2
docs/roadmap/configkit-v0.3.0.md
View File

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

27
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# ConfigKit v0.3.0 Implementation Plan # 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. 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 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 ## 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. Purpose: Establish a clean, reproducible handoff for later release preparation.