docs consolidation

docs/modules/cli/guides/exceptions.md

@@ -90,4 +90,4 @@ Options:
 ## Related Docs
 
 - Exceptions API entry point: `docs/api/exceptions.md`
-- Exception governance migration guide: `docs/migration/exception-governance.md`
+- Exception governance migration guide: `docs/technical/migration/exception-governance.md`

docs/modules/cli/guides/packs-profiles.md

@@ -53,4 +53,4 @@ StellaOps:
 
 The CLI reads the profile, applies the Authority configuration, and requests the listed scopes so the resulting tokens satisfy Task Runner and Packs Registry expectations.
 
-> **Pack approval tip** – `stella pack approve` now relays `--pack-run-id`, `--pack-gate-id`, and `--pack-plan-hash` to Authority whenever it asks for `packs.approve`. Profiles don’t store these values (they change per run), but keeping the approver profile loaded ensures the CLI can prompt for the metadata, validate it against the plan hash, and satisfy the Authority procedure documented in `docs/task-packs/runbook.md#4-approvals-workflow`.
+> **Pack approval tip** – `stella pack approve` now relays `--pack-run-id`, `--pack-gate-id`, and `--pack-plan-hash` to Authority whenever it asks for `packs.approve`. Profiles don’t store these values (they change per run), but keeping the approver profile loaded ensures the CLI can prompt for the metadata, validate it against the plan hash, and satisfy the Authority procedure documented in `docs/modules/packs-registry/guides/runbook.md#4-approvals-workflow`.

docs/modules/cli/guides/policy.md

@@ -1,7 +1,7 @@
-# Stella CLI — Policy Commands
-
-> **Audience:** Policy authors, reviewers, operators, and CI engineers using the `stella` CLI to interact with Policy Engine.  
-> **Imposed rule:** Submit/approve/publish flows must include lint, simulate, coverage, and shadow evidence; CLI blocks if required attachments are missing.
+# Stella CLI — Policy Commands
+
+> **Audience:** Policy authors, reviewers, operators, and CI engineers using the `stella` CLI to interact with Policy Engine.  
+> **Imposed rule:** Submit/approve/publish flows must include lint, simulate, coverage, and shadow evidence; CLI blocks if required attachments are missing.
 > **Supported from:** `stella` CLI ≥ 0.20.0 (Policy Engine v2 sprint line).  
 > **Prerequisites:** Authority-issued bearer token with the scopes noted per command (export `STELLA_TOKEN` or pass `--token`).
 > **2025-10-27 scope update:** CLI/CI tokens issued prior to Sprint 23 (AUTH-POLICY-23-001) must drop `policy:write`/`policy:submit`/`policy:edit` and instead request `policy:read`, `policy:author`, `policy:review`, and `policy:simulate` (plus `policy:approve`/`policy:operate`/`policy:activate` for promotion pipelines).
@@ -219,15 +219,15 @@ Options:
 `stella policy run status <runId>` retrieves run metadata.  
 `stella policy run list --status failed --limit 20` returns recent runs.
 
-### 4.3 History
-
-``` 
-stella policy history P-7 --limit 20 --format table
-```
-
-Shows version list with status, shadow flag, IR hash, attestation, submission/approval timestamps. Add `--runs` to include last run status per version. Exit code `0` success; `12` on RBAC error.
-
-### 4.4 Replay & Cancel
+### 4.3 History
+
+``` 
+stella policy history P-7 --limit 20 --format table
+```
+
+Shows version list with status, shadow flag, IR hash, attestation, submission/approval timestamps. Add `--runs` to include last run status per version. Exit code `0` success; `12` on RBAC error.
+
+### 4.4 Replay & Cancel
 
 ```
 stella policy run replay run:P-7:2025-10-26:auto --output bundles/replay.tgz
@@ -239,7 +239,7 @@ Replay downloads sealed bundle for deterministic verification.
 ### 4.4 Schema artefacts for CLI validation
 
 - CI publishes canonical JSON Schema exports for `PolicyRunRequest`, `PolicyRunStatus`, `PolicyDiffSummary`, and `PolicyExplainTrace` as the `policy-schema-exports` artifact (see `.gitea/workflows/build-test-deploy.yml`).
-- Each run writes the files to `artifacts/policy-schemas/<commit>/` and stores a unified diff (`policy-schema-diff.patch`) comparing them with the tracked baseline in `docs/schemas/`.
+- Each run writes the files to `artifacts/policy-schemas/<commit>/` and stores a unified diff (`policy-schema-diff.patch`) comparing them with the tracked baseline in `docs/modules/policy/schemas/`.
 - Schema changes trigger an alert in Slack `#policy-engine` via the `POLICY_ENGINE_SCHEMA_WEBHOOK` secret so CLI maintainers know to refresh fixtures or validation rules.
 - Consume these artefacts in CLI tests to keep payload validation aligned without committing generated files into the repo.
 
@@ -324,4 +324,4 @@ All non-zero exits emit structured error envelope on stderr when `--format json`
 
 ---
 
-*Last updated: 2025-11-26 (Sprint 307).* 
+*Last updated: 2025-11-26 (Sprint 307).*