Verify span deletion through complete CLI workflows

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,