Complete cleanup stage workstream

docs/internal/manifest.md

@@ -183,7 +183,7 @@ manifests remain compatible when those fields are absent. A successful forced
 rerun marks only succeeded transitive dependent session-stage records stale.
 The application owns a fixed dependency relation distinct from execution order;
 dependents are returned in canonical order. Render and extract therefore never
-stale one another, while either can stale analyze, publish, and notify.
+stale one another, while either can stale analyze, publish, notify, and cleanup.
 
 Starting an execution clears the current session-stage record's prior outputs,
 logs, generated configuration references, metadata, and semantic fingerprint.
@@ -216,11 +216,11 @@ match the current resolved stage semantics. Missing semantic evidence, malformed
 evidence, or a mismatch makes the stage and its fixed transitive dependents
 stale. The existing stage-specific resume
 validator runs only after this semantic check succeeds; both checks are
-required. Extraction and analyze have resume validators and may reject an
-otherwise eligible skip when their selected durable evidence is obsolete; the
-runner marks the aggregate record stale and executes it. Analyze's validator
-can still accept a partial selection when only unrelated artifact records are
-stale.
+required. Extraction, analyze, and cleanup have resume validators and may
+reject an otherwise eligible skip when their selected durable evidence is
+obsolete; the runner marks the aggregate record stale and executes it.
+Analyze's validator can still accept a partial selection when only unrelated
+artifact records are stale.
 
 Implemented reuse coverage is deliberately split between aggregate semantic
 evidence and focused durable validators:
@@ -238,6 +238,7 @@ evidence and focused durable validators:
 | analyze artifacts | per-artifact fingerprint, reconciliation, and output validator | [analyze](stage-analyze.md), [Scriptorium](../integrations/scriptorium.md) |
 | publish | aggregate semantic fingerprint plus immediate lock/commit checks | [publish](stage-publish.md), [storage adapter](adapters.md) |
 | notify | aggregate delivery-mode fingerprint | [pipeline overview](overview.md), [configuration](../config.md#notifications) |
+| cleanup | aggregate semantic fingerprint plus publish-evidence and target-absence validator | [cleanup](stage-cleanup.md), [workspace](workspace.md) |
 
 These contracts record resolved choices Narratio can observe, not operational
 runner tuning. External model, module, prompt, profile, and configuration-file

docs/internal/stage-analyze.md

@@ -158,9 +158,10 @@ Supported source families:
   artifact failed without output authority, and stales its current transitive
   dependents.
 - the runner's ordinary error path marks aggregate analyze failed, clears its
-  aggregate outputs, invalidates publish and notify through the application
-  dependency relation, and persists the live retry collection. Terminal-save
-  errors are joined with the original artifact or checkpoint failure.
+  aggregate outputs, invalidates publish, notify, and cleanup through the
+  application dependency relation, and persists the live retry collection.
+  Terminal-save errors are joined with the original artifact or checkpoint
+  failure.
 
 ## Invariants
 

docs/roadmap/implementation.md

@@ -285,7 +285,7 @@ documents fail strict decoding rather than entering a compatibility path.
 
 ## Stage 5 — Consolidate, Validate, And Close Workstream 9
 
-**Status:** Pending
+**Status:** Completed
 
 ### Goal
 

docs/roadmap/refactoring.md

@@ -420,7 +420,7 @@ version of a locked artifact while unlocked artifacts advance.
 
 ### Workstream 9 — Cleanup as the final pipeline stage
 
-**Status:** Pending
+**Status:** Complete
 
 **Audit sources:** H20, H21, C02, and C04.