eric/audita
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Simplify the library migration to target the final integration

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-24 01:09:43 +00:00
parent 5b7d2e6e81
commit 116648fa78
5 changed files with 75 additions and 137 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/roadmap/implementation.md
View File

@@ -6,6 +6,12 @@
unit in the [prototype roadmap](library-boundary.md#next-unit-testing-overlays-and-production-migration-plan),
not the production ConfigKit or PromptKit migrations.
**Production handoff revision:** The completed prototype stages remain recorded
below. The current [production plan](configkit.md#ordered-production-migration-handoff)
targets both libraries in one refactor; intermediate commits need not build or run.
It supersedes the earlier interim-runtime design. No temporary adapter,
compatibility shim, or processing gate is required.
Execute Stage 1 through Stage 6 in order. Each stage is sized as a separate coding
prompt for a gpt-5.6-terra agent and ends with a reviewable result. When assigned
one stage, finish that stage and report the next stage; when assigned the entire
@@ -250,7 +256,7 @@ to a passing test or observed demonstration result. Verify affected links and
## Stage 6: Prepare the Production Migration Plan and Close the Unit
**Status:** Complete (2026-09-24). **Depends on:** Stage 5. The ordered ConfigKit
production handoff records bounded packages, interim runtime behavior, tests,
production handoff records bounded packages, runtime integration, tests,
dependencies, and acceptance criteria. Prototype evidence and scope audit passed;
links and `git diff --check` verified.
@@ -272,19 +278,16 @@ components, tests, and acceptance criteria for:
- Profile loading/inspection and configuration snapshots, including relative-path
bases, secret redaction, provenance, and clear separation of ConfigKit settings
from PromptKit execution controls.
- Runtime conversion and the temporary connection to the existing LLM runtime.
For each new setting, state whether the interim runtime honors it or cannot yet
do so. Decide the explicit interim behavior and its tests; do not silently map
per-backend limits to the old global/role pools or pretend old retries implement
PromptKit repair/zero semantics. Avoid recreating PromptKit inside the bridge.
- Direct integration of the final configuration with PromptKit execution. Specify
the final behavior and tests for each setting; do not preserve the old runtime
through temporary adapters or add interim processing gates.
- Removal of superseded configuration machinery, retained domain checks, maintained
examples, canonical documentation updates, and the combined migration guide.
- The later PromptKit replacement/removal point and release follow-up. Preserve
- Removal of superseded LLM machinery and release follow-up. Preserve
the agreed ordering and defer release compliance/publication to the final unit.
If an interim behavior cannot be settled from the evidence, identify that concrete
open decision as a prerequisite to its production work package. Do not hide it in
an adapter or describe an unresolved production step as implementation-ready.
Resolve final integration decisions against the evidence. Record genuine open
questions without creating scaffolding to support intermediate commits.
Final audit: map every acceptance criterion in the prototype extension to actual
files and command results. Verify new relative links/anchors, run `git diff --check`,