Correct documentation refresh findings

docs/internal/app-orchestration.md

@@ -40,8 +40,9 @@ ordered work:
 3. Build and save the prompt data package, run Scriptorium render preflight,
    save any preflight result, and save initial metadata.
 4. Produce managed Markdown according to the report generation mode.
-5. Finalize metadata, optionally make an output copy, and optionally notify
-   Distributor from the managed report path.
+5. Optionally make an output copy, save final metadata, optionally notify
+   Distributor from the managed report path, and save metadata again when a
+   notification path is produced.
 
 Direct-Markdown reports prepare the managed report and invoke the Scriptorium
 run boundary. Generated-text-template reports look up their catalog definition,

docs/internal/scriptorium-adapter.md

@@ -1,6 +1,6 @@
 # Scriptorium Adapter Internals
 
-`internal/adapters/scriptorium` translates Weather Reporter render requests to
+`internal/adapters/scriptorium` translates Weatherreporter render requests to
 Scriptorium process arguments and translates process results back to local
 types. The external CLI and output contract belongs to the
 [Scriptorium integration guide](../integrations/scriptorium.md); prompts,

docs/internal/state.md

@@ -53,7 +53,7 @@ writes use `fileutil.WriteJSONAtomic`, so readers do not observe a partially
 written state file.
 
 The data package itself follows the shared
-[weather-data contract](weather-data.md). Report text, templates, and external
+[prompt-input contract](prompt-input.md). Report text, templates, and external
 delivery payloads remain owned by their respective packages and integration
 references.