Migrate examples and guidance and remove legacy test harness

docs/operations.md

@@ -8,9 +8,9 @@ for logical formats.
 ## Normal Workflow
 
 1. Choose a configuration and validate it using the
-   [configuration commands](cli.md#configuration-commands).
+   [configuration commands](cli.md#commands-and-help).
 2. Prepare input files conforming to the [input contract](integrations/transcript-glossary-files.md).
-3. Run the [processing command](cli.md#process-examples), choosing explicit output
+3. Run the [processing command](cli.md#commands-and-help), choosing explicit output
    and report destinations when those files must survive run-directory cleanup.
 4. Inspect the corrected transcript and process report. Review rejected or skipped
    corrections when the report indicates them; successful execution does not mean
@@ -25,7 +25,7 @@ artifact writes can fail, so a run directory need not contain every listed file.
 ## Output Files
 
 The caller chooses transcript and optional external report destinations using the
-[CLI](cli.md#process-output-and-exit-behavior). These are separate from the per-run
+[CLI](cli.md#streams-and-exit-status). These are separate from the per-run
 diagnostic directory unless the caller deliberately places them inside it.
 Choose existing, writable parent directories. Output/report files can be overwritten
 by subsequent runs using the same destinations.
@@ -99,7 +99,7 @@ artifact storage facility.
 
 ## Failure Inspection and Recovery
 
-1. Read stderr and the exit classification defined by the [CLI](cli.md#process-output-and-exit-behavior).
+1. Read stderr and the exit classification defined by the [CLI](cli.md#streams-and-exit-status).
 2. Locate the external report, or the run directory identified by the error when
    available. If a late error omits the path, inspect the selected work directory.
 3. Read the available report and error log. Use