Verify the integrated application and complete the migration

This commit is contained in:
2026-09-24 02:40:48 +00:00
parent 80804a038f
commit 7cefb3fb04
12 changed files with 314 additions and 26 deletions

View File

@@ -2,9 +2,9 @@
**Last updated:** 2026-09-24
**Status:** Final target selected; production implementation pending. The boundary
and selected overlays are verified. The [implementation plan](implementation.md)
owns execution stages; no production migration or release has begun.
**Status:** Production implementation complete. The selected configuration and
overlay model is implemented; [implementation evidence](implementation.md)
records verification. No release has been published.
## Purpose and Direction
@@ -20,15 +20,14 @@ guide instead of legacy loaders, aliases, dual operating modes, or an ongoing
compatibility layer. Retain existing syntax only when it independently suits the
new model, not because compatibility requires it.
The initial review and prototype used ConfigKit v0.3.1. The prototype now pins
v0.4.0 and verifies its selected-overlay path; original v0.3.1 findings remain
historical. The installed
application must depend on a versioned module, not a sibling checkout or local
module replacement.
The initial review and prototype used ConfigKit v0.3.1, then verified v0.4.0
selected overlays. Those findings remain historical; the prototype was removed
after production integration. The application depends on a versioned module,
without a sibling checkout or local module replacement.
The shared boundary/prototype unit is complete. Its [selected contract, inventory,
and evidence](library-boundary-findings.md) define the detailed target alongside
this roadmap. Production configuration migration has not begun.
this roadmap. Production configuration migration is complete.
## Target End State

View File

@@ -2,7 +2,7 @@
**Last updated:** 2026-09-24
**Status:** Ready for implementation. All stages below are pending. This replaces
**Status:** Implemented. All twelve stages are complete. This replaced
the completed testing-overlay prototype plan; its results remain in the
[boundary findings](library-boundary-findings.md#selected-overlay-extension-2026-09-24).
@@ -583,7 +583,21 @@ belongs to Stage 12.
## Stage 12: Verify the Combined Application and Close the Refactor
**Status:** Pending. **Depends on:** Stages 1–11.
**Status:** Complete. Controlled HTTP subprocess tests passed for base and testing
overlay selection, explicit validation-profile and domain overrides, both outbound
models, accepted repair, domain rejection without semantic retry, warning-only
repair exhaustion, empty and repeated module pipelines, and safe partial failure
diagnostics. `go test ./...`, `go build -o ./bin/audita ./cmd/audita`, focused
race tests for runtime/runner/subprocess code, and both Linux release builds
passed. The full suite also passed under Go 1.25.5 with offline module access.
Maintained examples and local documentation links validated; `git diff --check`
passed. No native macOS or live provider call was run. Release preparation remains
separate: propose Audita v2.0.0 with [one migration guide](../migrations/v2.md),
the actual pinned production dependency/license inventory, and LGPL
notice/source/rebuild-distribution review before publication. No release was
published here.
**Depends on:** Stages 1–11.
**Owns:** final integration tests, final defect fixes within this scope, and status/evidence.
1. Complete representative production subprocess workflows against controlled HTTP:

View File

@@ -2,10 +2,9 @@
**Last updated:** 2026-09-24
**Status:** Final target selected; production implementation pending. The shared
boundary and offline prototype, including ConfigKit v0.4.0 overlays, are verified.
[Implementation stages](implementation.md) are owned by the implementation plan.
This roadmap defines the end state and user intent; it authorizes no publication.
**Status:** Production implementation complete. ConfigKit v0.4.0 and PromptKit
v0.11.0 are adopted; [implementation evidence](implementation.md) records the
completed checks. Release compliance and publication remain separate work.
## Goal and Ownership