Migrate examples and guidance and remove legacy test harness

This commit is contained in:
2026-09-24 02:37:20 +00:00
parent 9561e80efb
commit 80804a038f
102 changed files with 328 additions and 8371 deletions

View File

@@ -535,7 +535,17 @@ JSON golden dumps. Reuse Stage 9 evidence rather than retest every event sequenc
## Stage 11: Finish Examples, Migration Guidance, and Removal
**Status:** Pending. **Depends on:** Stages 1–10.
**Status:** Complete. Maintained schema-2 local and service examples, role profiles,
and a testing overlay validate offline with a synthetic credential. The v2
migration guide maps retired files, flags, environment inputs, timing, secrets,
inspection, and reports. Removed the isolated prototype and obsolete CLI test
fixtures/hooks; production config, runtime, proposal, validator, and runner tests
retain their respective boundaries, with assembled subprocess coverage assigned
to Stage 12. Canonical references, Go requirements, historical links, and the
retry follow-up were updated. `go mod tidy`, `go mod verify`, focused tests,
local-link validation, and `git diff --check` passed.
**Depends on:** Stages 1–10.
**Owns:** maintained examples, affected canonical documentation, obsolete code/tests,
prototype removal, and final dependency cleanup.

View File

@@ -12,12 +12,12 @@ evidence; they do not establish overlay integration.
## Selected Boundary
The prototype lives in [examples/library-adoption](../../examples/library-adoption/README.md),
a separate Go module now using published ConfigKit v0.4.0, PromptKit v0.11.0, and
The former prototype is retained in Git history at `590604b`; it was a separate
Go module using published ConfigKit v0.4.0, PromptKit v0.11.0, and
Audita v1.1.0. The Audita dependency lets this consumer reuse actual internal domain
helpers through its Audita module namespace without a local replacement. It does
not make those internal packages a new public API. Remove this dependency along
with the prototype when equivalent production integration tests exist.
with the prototype after equivalent production integration tests landed.
The initial prototype results below were recorded with ConfigKit v0.3.1. On
2026-09-24, upgrading only its ConfigKit pin and sums to v0.4.0 required no source

View File

@@ -4,10 +4,11 @@
**Status:** Original boundary-design and offline-prototype unit completed;
overlay extension and production-planning handoff completed, 2026-09-24.
Production migration has not started. The work packages below retain the original
scope; [decisions, evidence, limitations, and handoff](library-boundary-findings.md)
record the outcome. The [executable prototype](../../examples/library-adoption/README.md)
is isolated from production. No publication or upstream changes were made.
The work packages below retain the original scope;
[decisions, evidence, limitations, and handoff](library-boundary-findings.md)
record the outcome. The executable prototype was removed after production
integration; Git history at `590604b` retains it. No publication or upstream
changes were made in that historical unit.
## Next Unit: Testing Overlays and Production Migration Plan

View File

@@ -1,6 +1,6 @@
# Runtime Behavior Decisions
**Last updated:** 2026-09-23
**Last updated:** 2026-09-24
The documentation migration identified these existing behaviors for separate
product consideration. Implementation status and any selected direction are noted
@@ -9,10 +9,8 @@ below; this document does not claim that runtime changes have landed.
- Decide whether the `never` retention selection should delete successful-run
diagnostics; current behavior is documented in
[operations](../operations.md#retention-behavior).
- The [library-adoption plan](library-adoption.md) selects explicit zero as disabling
transient retries, alongside separately enabled structural repair. Implement this
as part of the migration; the current adapter behavior documented in
[configuration](../config.md) remains unchanged until then.
- Resolved: [configuration](../config.md) now treats explicit zero as disabling
transient retries or structural repair independently; PromptKit performs both.
- Decide whether missing or null input timestamps should be rejected; current
decoding is documented in the [input contract](../integrations/transcript-glossary-files.md).