Verify span deletion through complete CLI workflows

docs/internal/prompts.md

@@ -38,6 +38,6 @@ path. Prepared runtime metadata belongs in diagnostics rather than the registry.
 
 The structured-call contract carries prompt ID/version, string variables,
 response-schema key, and logical-call attribution. Module and validator callers
-are being migrated in their respective work units. See the
+pass these values through the role-bound adapter. See the
 [LLM runtime](llm-runtime.md) for runtime assembly and
 [configuration](../config.md) for operator-selected profiles.

docs/migrations/v2.md

@@ -125,3 +125,11 @@ capacity and usage fields retain known/complete flags. Debug runs write
 material. See [operations](../operations.md#diagnostics-directory) for placement
 and paths, [configuration](../config.md) for all settings, and the
 [CLI reference](../cli.md) for current flags.
+
+Debug ledger consumers should recognize the deterministic validator key
+`non_empty_resulting_segment` in place of `non_empty_corrected_text`. The
+`empty_resulting_segment` reason is unchanged. Candidate-backed ledger entries
+now include `proposed_corrected_text: ""` for an empty replacement, and applied
+deletions also include `applied_corrected_text: ""`; omitted fields still mean
+there was no candidate or no applied edit, respectively. See the
+[debug artifact contract](../integrations/output-files.md#debug-only-files).

docs/roadmap/implementation.md

@@ -2,7 +2,7 @@
 
 **Last updated:** 2026-09-25
 
-**Status:** In progress; Stages 1–3 complete.
+**Status:** Implemented; all stages complete.
 **Source baseline:** `a83a518` (feature roadmap); application baseline `0b6cd98`.
 **Audience:** gpt-5.6-terra coding agent.
 
@@ -12,7 +12,8 @@ Implement [Consistent Span Deletion](span-deletion.md). That document owns the
 product intent, target semantics, and acceptance criteria. This document owns the
 concrete decisions, ordered work, and validation. Execute Stage 1 through Stage 4
 in order. Record actual completion and checks beneath each stage when implemented.
-Do not interpret this ready status as implemented behavior.
+The completion evidence below records the implemented behavior; the source
+baseline remains historical.
 
 Read [development guidance](../development.md) and all [agent](../policy/agents.md),
 [architecture](../policy/architecture.md), [documentation](../policy/documentation.md),
@@ -351,6 +352,13 @@ schema/adapter tests, domain/application tests, serialized debug tests, and
 representative complete CLI workflows. The workspace is committed and the docs
 describe implemented behavior without claiming whole-segment removal.
 
+**Completed 2026-09-25.** Four offline CLI workflows verified clean deletion,
+literal spacing, partial success with blank-result filtering, and an ordinary
+negative meaning-review decision. Metadata was checked against normalized
+input; the existing runner test covers fixed section membership and order.
+`go test ./...` passed. Documentation references, affected links, and whitespace
+were checked. Whole-segment removal remains deferred.
+
 ## Open Questions
 
 None requiring a product decision remain. Validator names, schema/prompt identity,

docs/roadmap/library-adoption.md

@@ -4,8 +4,8 @@
 
 **Status:** Production implementation complete. ConfigKit v0.4.0 and PromptKit
 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.
+completed checks. The current `implementation.md` covers span deletion instead.
+Release compliance and publication remain separate work.
 
 ## Goal and Ownership
 

docs/roadmap/remediation.md

@@ -3,7 +3,7 @@
 **Reviewed:** 2026-09-25, source commit `ec78b5a`.
 **Scope:** Review of the resilience implementation for unintentionally strengthened
 invariants, contracts, guarantees, and test requirements, compared with
-[resilience.md](resilience.md), [implementation.md](implementation.md), and the
+[resilience.md](resilience.md), [historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/a83a518/docs/roadmap/implementation.md), and the
 [agent policy](../policy/agents.md).
 **Status:** R11–R14 addressed. The findings below describe the reviewed source;
 see the resolution record for the implemented changes and verification.

docs/roadmap/resilience.md

@@ -4,7 +4,7 @@
 
 **Status:** Implemented. This document records the selected behavior and user
 intent. Concrete design decisions and completion evidence are in
-[implementation.md](implementation.md).
+[historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/a83a518/docs/roadmap/implementation.md).
 
 ## Purpose and User Intent
 
@@ -283,7 +283,7 @@ volume, and a short reason breakdown. Detailed inspection belongs in YAML or deb
 
 ## Implementation Reference
 
-The product decisions are settled. [implementation.md](implementation.md) defines
+The product decisions are settled. The [historical implementation plan](https://gitea.maximumdirect.net/eric/audita/src/commit/a83a518/docs/roadmap/implementation.md) defines
 the selected settings and precedence, YAML schemas, counts and ordering, interrupted
 work presentation, destination checks, and output finalization. It also owns the
 ordered implementation stages and validation work. This document remains the

docs/roadmap/span-deletion.md

@@ -2,7 +2,7 @@
 
 **Last updated:** 2026-09-25
 
-**Status:** Accepted target; not implemented. This document owns the desired
+**Status:** Implemented. This document owns the desired
 behavior and user intent. [implementation.md](implementation.md) owns the concrete
 steps, selected implementation details, and completion evidence.
 
@@ -19,7 +19,7 @@ authorize whole-segment removal, broaden module responsibilities, or introduce
 new recovery machinery. The accepted [resilience behavior](resilience.md) remains
 in effect, including partial success, fixed chunks, and validation before mutation.
 
-## Current Baseline
+## Historical Baseline (`0b6cd98`)
 
 The source reviewed at `0b6cd98` contains a mismatch: