Document the new configuration and processing workflow

docs/migrations/v2.md

@@ -2,8 +2,8 @@
 
 Audita v2 adopts ConfigKit for configuration and PromptKit for LLM execution.
 Version-1 configuration files, environment overlays, and retired flags are not
-accepted. Copy a maintained [local](../../examples/minimal-config.yml) or
-[service](../../examples/production-config.yml) example, then select real models
+accepted. Copy a maintained [local](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/examples/minimal-config.yml) or
+[service](https://gitea.maximumdirect.net/eric/audita/src/tag/v3.1.1/examples/production-config.yml) example, then select real models
 in the accompanying `examples/profiles/` files. A testing overlay is shown at
 `examples/overlays/testing.yml`; its model choice carries no cost, speed, or
 quality guarantee.
@@ -122,7 +122,7 @@ capacity and usage fields retain known/complete flags. Debug runs write
 `effective-config.redacted.yaml`, `selected-profiles.yaml`,
 `config-origins.yaml`, `utilization-diagnostics.json`, and
 `llm-execution.json`. Request and response artifacts remain redacted debugging
-material. See [operations](../operations.md#diagnostics-directory) for placement
+material. See [operations](../operations.md#debug-evidence) for placement
 and paths, [configuration](../config.md) for all settings, and the
 [CLI reference](../cli.md) for current flags.
 

docs/migrations/v3.md

@@ -0,0 +1,23 @@
+# Migrating to application configuration v3
+
+Audita v3 is a hard cutover. Move application settings to `version: 3` and use
+[the configuration reference](../config.md) and [maintained examples](../../examples/)
+to construct the new files. The previous configuration and standalone glossary
+formats are not loaded by the new processing path.
+
+- Replace `pipeline.modules` with ordered `pipeline.stages` records containing
+  `module` and any per-entry overrides. An explicit empty list runs normalization.
+- Define named `glossary_collections` in configuration or its companion imports;
+  select them using `glossaries` and `protected_terms`. Remove `--glossary` and
+  `--modules` from invocations.
+- Move profiles and backends out of the application configuration and retired
+  `profiles_dir` layout into PromptKit resources. Use its current list records,
+  IDs, credential sources, and backend admission settings. Select proposal and
+  validation profiles in application `llm` settings.
+- Use the shared `--debug` flag for capture; `diagnostics.work_dir` remains the
+  parent directory. Review report and output destinations before running.
+
+Inspect configuration and resources before processing, then try a controlled
+small transcript. Processing preflight checks every glossary correction and
+selected role before preparing outputs or invoking a model. See [operations](../operations.md)
+for lifecycle and recovery.