Consolidate development policy docs and remove legacy documentation paths

docs/policy/architecture.md

@@ -25,14 +25,12 @@ The current built-in modules are `glossary`, `homophones`, `spoken_word`, and `g
 
 For external behavior and compatibility details, prefer links to existing behavior docs:
 
-- [Architecture overview](../architecture/architecture.md)
-- [Public contract](../architecture/public-contract.md)
-- [Diagnostics](../architecture/diagnostics.md)
-- [Structured LLM](../architecture/structured-llm.md)
-- [Validators](../architecture/validators.md)
-- [Prompts](../architecture/prompts.md)
-- [Output schemas](../architecture/output-schemas.md)
-- [Configuration](../configuration.md)
+- [CLI reference](../cli.md)
+- [Configuration](../config.md)
+- [Operations](../operations.md)
+- [Troubleshooting](../troubleshooting.md)
+- [Integration docs](../integrations/subprocess.md)
+- [Internal docs](../internal/overview.md)
 
 ## Core Design Principles
 
@@ -124,7 +122,7 @@ Config behavior is owned by `internal/core/config`; command usage and process wi
 
 `audita process` uses implemented precedence: defaults, config file, environment, then CLI flags. `config validate` validates defaults plus a file config and intentionally does not apply environment overrides. `config print-effective` applies defaults, file config, and environment overrides, then prints redacted JSON.
 
-Do not duplicate full CLI or config reference material here. Use [Configuration](../configuration.md), the README, and [Public contract](../architecture/public-contract.md) for current external behavior.
+Do not duplicate full CLI or config reference material here. Use [Configuration](../config.md), [CLI reference](../cli.md), [Operations](../operations.md), and integration docs under [`docs/integrations/`](../integrations/subprocess.md) for current external behavior.
 
 When adding config fields or CLI flags, update: