Complete session-only manifest migration

docs/cli.md

@@ -165,7 +165,7 @@ Behavior:
 - continues interrupted or partially completed sessions by running non-succeeded stages;
 - writes the session manifest as the sole durable progress ledger. Each
   invocation also creates its run-local directory and returns an immediate
-  command summary; neither produces a run manifest.
+  command summary; neither creates another durable progress record.
 - reports the resolved profile (or `none`) and effective configuration digest.
 
 When `--artifacts` is present, the selected range must contain `analyze` or

docs/internal/stage-analyze.md

@@ -154,7 +154,7 @@ Supported source families:
 
 - `analyze` performs no remote storage calls for previous-session source resolution.
 - input-identity resolution is read-only: it does not invoke adapters,
-  materialize outputs, update status, or create run records.
+  materialize outputs, update status, or create run-local files.
 - fingerprints exclude timeouts, retries, timestamps, producer and Narratio run
   IDs, executable and config paths, workspace roots, diagnostic locations, and
   executable or private transitive configuration contents. A change that is

docs/internal/stage-extract.md

@@ -101,8 +101,8 @@ has passed validation and installation.
 When a replacement attempt begins, the current session-stage record no longer
 advertises payload from the previous success. A failed replacement therefore
 has no current outputs, logs, generated configuration references, or metadata,
-while the earlier invocation manifest and immutable promoted bundle remain
-available for audit and recovery.
+while the earlier immutable promoted bundle remains available for audit and
+recovery.
 
 ## Implementation And Focused Tests
 

docs/internal/stage-publish.md

@@ -7,7 +7,7 @@ Upload run/session outputs to object storage and atomically advance remote curre
 ## Inputs
 
 - successful preceding stages from the [canonical stage set](overview.md#pipeline-stage-set)
-- invocation-scoped run files
+- declared run-local diagnostic files
 - resolved publish output rules
 - effective publish locks (static + remote merged lock set), revalidated at the
   remote commit boundary
@@ -15,7 +15,8 @@ Upload run/session outputs to object storage and atomically advance remote curre
 
 ## Outputs
 
-- uploaded invocation record and selected publish outputs;
+- uploaded session manifest, declared run-local diagnostics, and selected
+  publish outputs;
 - uploaded durable previous-session cache files when present;
 - immutable run-scoped commit manifest; and
 - current commit pointer, written last.
@@ -27,13 +28,15 @@ Exact remote placement and the operator workflow belong in
 
 - when publishing or run upload is disabled, completes successfully with no
   outputs and records explanatory metadata. This is not an explicit self-skip:
-  both manifests record success. Enablement and upload policy are fingerprinted,
-  so changing either automatically makes the prior result non-resumable.
+  the session manifest records success. Enablement and upload policy are
+  fingerprinted, so changing either automatically makes the prior result
+  non-resumable.
 - validates prerequisite stage success and object-store availability.
 - derives a deterministic run-archive allowlist from the session manifest's
   declared current-run outputs, logs, and generated configurations. References
   outside the current run root, including canonical session files and prior-run
-  diagnostics, are not archive candidates. No run manifest is read or uploaded.
+  diagnostics, are not archive candidates. No distinguished diagnostic file is
+  read or uploaded.
 - opens each archive candidate beneath its archive root without following
   symlinked ancestors or leaf entries, verifies that it is a regular file and
   checks a declared checksum when present, then streams the opened descriptor.

docs/operations.md

@@ -168,11 +168,11 @@ selected artifact evidence is still semantically current.
 Before a bounded run or plan whose range starts after `prepare`, every excluded
 prefix stage must already have a session-manifest status of `succeeded` or
 `skipped`. Narratio reports the first absent, pending, running, failed, stale,
-or interrupted prerequisite without creating a run record or changing session
-state. Widen `--from` to include that stage, or recover it explicitly before
-retrying. Excluded prefix stages are not resume-validated or repaired as part
-of the bounded invocation; selected stages still reject missing, unsafe, or
-manifest-inconsistent inputs at their owning boundary.
+or interrupted prerequisite without creating a run-local directory or changing
+session state. Widen `--from` to include that stage, or recover it explicitly
+before retrying. Excluded prefix stages are not resume-validated or repaired as
+part of the bounded invocation; selected stages still reject missing, unsafe,
+or manifest-inconsistent inputs at their owning boundary.
 
 Stages after `--through` are not prerequisites and are never scheduled by the
 bounded invocation. A selected forced stage can mark one of those succeeded
@@ -279,9 +279,9 @@ narratio run-stage prepare 2026-04-04 --force
 
 Starting a replacement clears the previous extraction payload from the current
 session-stage record. If that replacement fails or self-skips, the current
-record does not fall back to the earlier outputs. The earlier run manifest and
-immutable bundle remain available for inspection, but downstream resolution
-requires a new current successful extraction record.
+record does not fall back to the earlier outputs. The earlier immutable bundle
+remains available for inspection, but downstream resolution requires a new
+current successful extraction record.
 
 Notarius extraction validates its run-local bundle and moves it once to the
 unique durable bundle path. A pre-existing durable destination is a collision;
@@ -314,9 +314,9 @@ References to canonical session files and prior-run paths are excluded. Each
 declared source is opened without following symlinked ancestors or the leaf,
 verified as a regular file, and streamed from that verified descriptor.
 Unlisted files and unsafe entries are never uploaded; a run with no declared
-current-run diagnostics uploads no run-local files. No run manifest is
-uploaded. The durable bundle is never scanned for implicit publication; only
-lanes named by explicit `pipeline.publish.outputs` rules are uploaded.
+current-run diagnostics uploads no run-local files. No distinguished diagnostic
+file is uploaded. The durable bundle is never scanned for implicit publication;
+only lanes named by explicit `pipeline.publish.outputs` rules are uploaded.
 
 To intentionally replace the current extraction result, run:
 
@@ -482,10 +482,9 @@ Durable session paths:
 - `config/**`
 - `runs/**`
 
-`manifest.json` is a versioned local-state document. Narratio accepts only
-`narratio.session-manifest.v1`; each invocation record under `runs/**` accepts
-only `narratio.run-manifest.v1`. Do not edit an older manifest to add missing
-markers. Move unsupported state aside and regenerate it, restore a verified
+`manifest.json` is the versioned session-progress document. Narratio accepts
+only `narratio.session-manifest.v1`. Do not edit unsupported session state to
+add missing markers. Move it aside and regenerate it, restore a verified
 current committed snapshot, or republish healthy regenerated state as the
 relevant workflow requires.
 

docs/roadmap/implementation.md

@@ -7,9 +7,10 @@ This is the executable plan for [`refactoring.md`](refactoring.md), Workstream
 [`contract-audit.md`](contract-audit.md) and rows H14, H15, H17, C02, and C03
 of [`audit-decisions.md`](audit-decisions.md) own the approved decisions.
 
-All five stages are pending and must be implemented in order. Each stage is
-bounded for one `gpt-5.6-terra` prompt. Workstreams 1 through 3 are complete.
-Workstreams 5 and later are out of scope: do not decompose the runner into a
+**Status: Completed**
+
+All five stages are completed. Workstreams 1 through 4 are complete.
+Workstreams 5 and later remain out of scope: do not decompose the runner into a
 new lifecycle type, redesign pre-execution decisions, add per-artifact analyze
 checkpoints, split publish into separate transactions, add cleanup as a stage,
 or change remote lock policy while following this plan.
@@ -333,7 +334,7 @@ path, and mechanism tests from their owning packages.
 
 ## Stage 5 — Reconcile Current Documentation And Close Workstream 4
 
-**Status: Pending**
+**Status: Completed**
 
 ### Goal
 

docs/roadmap/refactoring.md

@@ -189,7 +189,7 @@ code and fail clearly instead of being inferred or normalized.
 
 ### Workstream 4 — One durable local manifest authority
 
-**Status:** Pending
+**Status:** Complete
 
 **Audit sources:** H14, H15, H17, C02, and C03.
 

docs/troubleshooting.md

@@ -197,8 +197,9 @@ Safe fix:
 
 - widen the bounded range to include the first reported stage, or recover that
   stage explicitly with `run-stage` before retrying. The failed check does not
-  create a run record or modify the manifest. Narratio does not resume-validate
-  excluded prefix stages, and stages after `--through` are not prerequisites.
+  create a run-local directory or modify the manifest. Narratio does not
+  resume-validate excluded prefix stages, and stages after `--through` are not
+  prerequisites.
 
 If prerequisite statuses are terminal but a selected stage reports a missing,
 unsafe, or checksum-inconsistent artifact, repair the artifact at the stage