Archive Audita reports as polish diagnostics

docs/internal/stage-polish.md

@@ -12,21 +12,26 @@ Run Audita polishing on base transcript and produce polished transcript.
 ## Outputs
 
 - `transcripts/polished.json`
-- optional `artifacts/audita.report.json`
+
+The transcript is the only canonical output. Available `errors.yml`,
+`recoveries.yml`, and `report.md` remain beside the run-local transcript and
+are recorded as diagnostics, not artifact outputs.
 
 ## Key Behavior
 
 - resolves base transcript only from verified merge manifest output evidence.
-- invokes an Audita runner configured with static model/runtime options; the
-  invocation supplies paths and modules.
+- invokes an Audita v2 runner with external configuration selectors and
+  explicitly forwarded provider credentials; the invocation supplies paths.
 - validates processed transcript structure (`segments` array required).
-- validates optional report JSON.
-- materializes canonical outputs; records logs/generated config and adapter metadata.
+- validates reported diagnostic paths against the three fixed adjacent names.
+- materializes only the canonical transcript; records available reports with
+  stdout/stderr logs, generated invocation, and safe adapter metadata.
 
 ## Invariants
 
 - polished transcript schema validation is mandatory.
-- report output is config-gated.
+- reports are optional diagnostics; Audita's external configuration may disable
+  them. A failed invocation never promotes an incidental transcript.
 
 ## Resume Semantics
 

docs/operations.md

@@ -426,6 +426,9 @@ tree and reports which stream exceeded the limit.
 
 Run-local diagnostics are:
 
+- `runs/{run_id}/polish/outputs/transcripts/errors.yml`,
+  `recoveries.yml`, and `report.md` when Audita writes them beside its
+  run-local polished transcript
 - `runs/{run_id}/extract/notarius.receipt.json`
 - `runs/{run_id}/extract/notarius.stderr.log`
 - `runs/{run_id}/extract/notarius-output/` before durable promotion
@@ -439,6 +442,10 @@ Unlisted files and unsafe entries are never uploaded; a run with no declared
 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 inspect a published polish report remotely, read its declared object under
+the run archive's `polish/outputs/transcripts/` prefix. Session restore does
+not restore run-archive diagnostics as canonical session files; it restores only
+the committed manifest and declared transcript/artifact objects.
 
 To intentionally replace the current extraction result, run:
 

docs/roadmap/implementation.md

@@ -316,7 +316,10 @@ semantic integration; all stages are required before release.
 
 ## Stage 5: Integrate polish reports with diagnostic lifecycle
 
-Status: Not started.
+Status: Complete (2026-09-25).
+
+Verification: `go test ./internal/stage ./internal/app ./internal/manifest ./internal/artifacts`,
+`go test -race ./internal/stage ./internal/app`, and `git diff --check` passed.
 
 Preparation: `internal/stage/polish.go`, `polish_test.go`, `run_local.go`,
 `stage.go`, `publish_sources.go`; result application in `internal/app/runner.go`;