Complete Phase 16 default pipeline integration

docs/rewrite-notes.md

@@ -71,7 +71,18 @@ Implemented:
 - Production spoken_word module package with Python-aligned prompt intent and guardrails.
 - Explicit `--modules spoken_word` runtime path through runner, shared proposal generation, validators, application, reporting, and diagnostics.
 - Focused multi-module runtime tests for already-implemented interoperability (for example `spoken_word,grammar`) without claiming full default-pipeline completion.
-- All production modules now exist (`glossary`, `homophones`, `spoken_word`, `grammar`), but default full-sequence integration remains Phase 16 work.
+- All production modules now exist (`glossary`, `homophones`, `spoken_word`, `grammar`) and are integrated into the default full-sequence runtime path.
+- Default runtime sequence is now active and ordered as:
+  - `glossary`
+  - `homophones`
+  - `glossary`
+  - `spoken_word`
+  - `grammar`
+- Repeated glossary stages resolve and report deterministically as `glossary_1` and `glossary_2`.
+- Full-pipeline module reports and run-level summaries aggregate applied/skipped/failed metadata across all module instances.
+- Mid-pipeline failure reporting preserves partial progress and failed-module metadata.
+- Full-pipeline diagnostics include proposal/validator prompt-response artifacts with redaction.
+- Skip-aware retention uses actual module skipped/rejected correction data.
 - Broad deterministic and CLI/subprocess test coverage for implemented phases through `go test ./...`.
 - Internal typed structured LLM contract (`StructuredLLMClient.CompleteStructured(ctx, req, out)`).
 - `internal/framework/llm` instructor-go-backed adapter with:
@@ -87,7 +98,9 @@ Implemented:
 - Generic JSON diagnostics primitives for LLM interactions (request metadata, request payload, response payload, optional error payload) with secret redaction.
 
 Not yet implemented in runtime pipeline:
-- End-to-end transcript polishing behavior with the full default module sequence.
+- Python parity fixture suite and parity verification workflow.
+- Operational hardening beyond current Phase 16 runtime/reporting/diagnostics scope.
+- Rollout/Python retirement work.
 
 ## Completed phases
 
@@ -192,7 +205,7 @@ Not implemented in Phase 7 (by design):
 - End-to-end transcript polishing.
 
 Current runtime behavior note:
-- Default user-facing CLI behavior remains deterministic normalization/chunking output unless test-only module injection is used during tests.
+- Default user-facing CLI behavior now executes the full production module sequence unless `--modules` explicitly overrides it.
 
 ## Phase 8: Runtime validator framework and deterministic validators
 Completed.
@@ -225,7 +238,7 @@ Not implemented in Phase 8 (by design):
 
 ## Remaining work plan
 
-Next recommended phase: **Phase 16 (default full pipeline integration)**.
+Next recommended phase: **Phase 17 (Python parity fixture suite)**.
 
 ## Phase 9: Structured LLM client and scheduler infrastructure
 
@@ -446,6 +459,8 @@ Not implemented in Phase 15 (by design):
 
 ## Phase 16: Default full pipeline integration
 
+Completed.
+
 ### Purpose
 
 Enable and harden the full default module sequence in the Go runtime path.
@@ -489,6 +504,27 @@ Running `audita process transcript.json --glossary glossary.yaml --output correc
 - CLI stdout/stderr behavior remains subprocess-safe.
 - `go test ./...` passes without requiring external LLM credentials.
 
+### Phase 16 completion status
+
+Implemented:
+- Normal `audita process` runs without `--modules` now execute the full sequence:
+  - `glossary`
+  - `homophones`
+  - `glossary`
+  - `spoken_word`
+  - `grammar`
+- Explicit `--modules` still overrides the default sequence.
+- Repeated glossary stages are deterministic (`glossary_1`, `glossary_2`) and reported distinctly.
+- Full-pipeline module reports aggregate applied changes, application skips, validator rejections, and failed-module metadata.
+- Full-pipeline diagnostics include prompt/response artifacts for module proposal generation and validator LLM interactions with secret redaction.
+- Mid-pipeline failure preserves partial module progress in reports and retains diagnostics + `error.log`.
+- Auto-retention keeps successful runs with actual skipped/rejected corrections and always retains failed runs.
+
+Intentionally deferred:
+- Phase 17 parity fixture suite.
+- Phase 18 operational hardening.
+- Phase 19 rollout/Python retirement work.
+
 ## Phase 17: Python parity fixture suite
 
 ### Purpose