Document resilient reports and remove obsolete warning material
This commit is contained in:
@@ -3,7 +3,7 @@
|
||||
**Last updated:** 2026-09-24
|
||||
|
||||
**Status:** Production implementation complete. The selected configuration and
|
||||
overlay model is implemented; [implementation evidence](implementation.md)
|
||||
overlay model is implemented; [implementation evidence](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md)
|
||||
records verification. No release has been published.
|
||||
|
||||
## Purpose and Direction
|
||||
@@ -137,7 +137,7 @@ ConfigKit and PromptKit form one intentional breaking refactor. Intermediate
|
||||
commits need not build or run. The target contains no temporary old-runtime adapter,
|
||||
compatibility shim, processing gate, dual loader, or automatic legacy conversion.
|
||||
The [combined feature roadmap](library-adoption.md) owns execution/reporting intent;
|
||||
[implementation.md](implementation.md) alone owns stage order and implementation tasks.
|
||||
[implementation.md](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md) alone owns stage order and implementation tasks.
|
||||
|
||||
The final application loads all retained domain settings, assembles both selected
|
||||
profiles, and processes through PromptKit. Controlled HTTP evidence must connect
|
||||
|
||||
@@ -782,6 +782,17 @@ has no obsolete report/retention path keeping debug enabled implicitly.
|
||||
|
||||
## Stage 13 — Update Canonical Guidance, Examples, and Remove Obsolete Material
|
||||
|
||||
**Completed 2026-09-24.** Canonical CLI, configuration, operations, integration,
|
||||
internal, architecture, README, example, and migration guidance now describes
|
||||
three ordinary reports, independent debug selection, partial outcomes, fixed
|
||||
matrices, and finalization/exit behavior. The obsolete retention follow-up is
|
||||
resolved while timestamp policy remains open. Historical library-adoption
|
||||
links point to the prior plan's completion evidence. The unreferenced warning
|
||||
package and retention-only helper/tests were removed. Maintained config and
|
||||
profile inspection examples passed offline, relative file and heading links
|
||||
resolved, and `go test ./internal/framework/processreport
|
||||
./internal/core/config ./internal/cli` plus `git diff --check` passed.
|
||||
|
||||
**Work:** Update `docs/cli.md`, `config.md`, `operations.md`, integration output/subprocess/
|
||||
LLM contracts, internal pipeline/validators/LLM/diagnostics/overview guidance, README,
|
||||
and maintained examples/migration guidance. Architecture policy must distinguish
|
||||
|
||||
@@ -3,8 +3,9 @@
|
||||
**Last updated:** 2026-09-24
|
||||
|
||||
**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.
|
||||
v0.11.0 are adopted; [historical implementation evidence](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md) records the
|
||||
completed checks. The current `implementation.md` is a separate resilience
|
||||
roadmap. Release compliance and publication remain separate work.
|
||||
|
||||
## Goal and Ownership
|
||||
|
||||
|
||||
@@ -312,12 +312,12 @@ claims of completion for the prototype.
|
||||
The new profile/credential/capacity and deadline choices are explicit above; no
|
||||
unresolved upstream requirement prevents starting the ConfigKit implementation
|
||||
plan. Production report field names and final runtime wiring are selected in the
|
||||
[implementation plan](implementation.md), following the outcome and observation
|
||||
[implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md), following the outcome and observation
|
||||
contract here. The coordinated refactor targets both libraries directly; intermediate commits do not require a working legacy runtime.
|
||||
|
||||
### Production Implementation Reference
|
||||
|
||||
The [implementation plan](implementation.md) owns ordered production work,
|
||||
The [implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md) owns ordered production work,
|
||||
component changes, tests, and acceptance criteria. The [combined roadmap](library-adoption.md)
|
||||
and [configuration roadmap](configkit.md) own the final target. This evidence does
|
||||
not require an interim runtime bridge or separately runnable configuration migration.
|
||||
@@ -388,5 +388,5 @@ The tests use a controlled built-in HTTP transport and synthetic credentials;
|
||||
there were no live provider calls. The prototype still covers one representative
|
||||
proposal/assessment pair, not all production modules, prompts, CLI paths, or
|
||||
diagnostic artifacts. Root `go test ./...` does not run this nested module. No
|
||||
upstream API gap appeared in this extension. The [production implementation plan](implementation.md)
|
||||
upstream API gap appeared in this extension. The [production implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md)
|
||||
keeps implementation and release pending.
|
||||
|
||||
@@ -12,7 +12,7 @@ changes were made in that historical unit.
|
||||
|
||||
## Next Unit: Testing Overlays and Production Migration Plan
|
||||
|
||||
**Status:** Complete. The [production implementation plan](implementation.md)
|
||||
**Status:** Complete. The [production implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md)
|
||||
owns subsequent work; the [overlay findings](library-boundary-findings.md#selected-overlay-extension-2026-09-24)
|
||||
record this unit's checks. The original work packages below remain
|
||||
historical scope for the completed first unit.
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
**Reviewed:** 2026-09-24, source commit `7cefb3f`.
|
||||
**Scope:** The twelve implementation commits after `1ad2119`, compared with the
|
||||
[implementation plan](implementation.md), [combined target](library-adoption.md),
|
||||
[implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/cb405f6/docs/roadmap/implementation.md), [combined target](library-adoption.md),
|
||||
and [configuration target](configkit.md).
|
||||
**Status:** R1–R5 addressed and verified on 2026-09-24. The evidence in the
|
||||
original findings below describes source commit `7cefb3f`; line references are
|
||||
|
||||
@@ -2,13 +2,13 @@
|
||||
|
||||
**Last updated:** 2026-09-24
|
||||
|
||||
The documentation migration identified these existing behaviors for separate
|
||||
product consideration. Implementation status and any selected direction are noted
|
||||
below; this document does not claim that runtime changes have landed.
|
||||
The documentation migration identified existing behaviors for separate product
|
||||
consideration. The resilience implementation resolved the diagnostics-retention
|
||||
question; the input-timestamp question remains open.
|
||||
|
||||
- Decide whether the `never` retention selection should delete successful-run
|
||||
diagnostics; current behavior is documented in
|
||||
[operations](../operations.md#retention-behavior).
|
||||
- Resolved: legacy `auto`/`always`/`never` retention settings were removed.
|
||||
Debug is explicitly enabled with `diagnostics.debug` or `--debug`, creates no
|
||||
directory when disabled, and retains its directory on every outcome when enabled.
|
||||
- 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
|
||||
|
||||
Reference in New Issue
Block a user