Add determinism tests for verdict artifact generation and update SHA256 sums script

- Implemented comprehensive tests for verdict artifact generation to ensure deterministic outputs across various scenarios, including identical inputs, parallel execution, and change ordering.
- Created helper methods for generating sample verdict inputs and computing canonical hashes.
- Added tests to validate the stability of canonical hashes, proof spine ordering, and summary statistics.
- Introduced a new PowerShell script to update SHA256 sums for files, ensuring accurate hash generation and file integrity checks.

docs/governance/SHA256SUMS

@@ -1,7 +0,0 @@
-# Hash index for governance/exception docs
-# <sha256>  <relative-path>
-8a5d1429a307eff95d86476e330defb381bc447239e569bea8c2b641db72ff98  docs/governance/exceptions.md
-bc91b827793ea36a079b0f68de102424034f539d497f50fa90cb8a6c4da4dec4  docs/governance/approvals-and-routing.md
-ec33d6612473d997196ec463042cc5cff21e107ab9d267fd2fa4ffd166e6f25c  docs/api/exceptions.md
-1b571fb4d5b8112a60fe627633039aea154f3c35dc9d9ab9f3b21eec636e3161  docs/ui/exception-center.md
-9967d66765f90a31e16d354e43dd6952566d3a359e3250f4f5f9d4b206ba1686  docs/modules/cli/guides/exceptions.md

docs/governance/approvals-and-routing.md

@@ -1,15 +0,0 @@
-# Approvals & Routing (stub)
-
-> Status: BLOCKED — awaiting routing matrix, MFA rules, audit trail requirements (DOCS-EXC-25-002).
-
-## Outline
-1. Roles and approvers (matrix TBD)
-2. Routing rules per tenant/environment/resource
-3. MFA requirements and enforcement points
-4. Audit trail fields and retention
-5. Offline readiness (export/import of approvals)
-6. Verification steps (hash list + sample events)
-
-## Determinism
-- Add hashes to `docs/governance/SHA256SUMS` when populated.
-- Keep tables sorted by role/tenant/environment to minimize churn.

docs/governance/default-approval-protocol.md

@@ -58,7 +58,7 @@ When a decision is needed, create a **Decision Contract** document:
 After 48 hours without objection:
 1. Update `Status:` to `DEFAULT-APPROVED`
 2. Update dependent sprint files
-3. Log in `docs/governance/decisions-log.md`
+3. Record the decision in the relevant sprint file execution log (`docs/implplan/SPRINT_*.md`)
 
 ## Owner Manifest Pattern
 
@@ -103,5 +103,5 @@ If a decision is contested after default approval:
 
 ## References
 
-- [Approvals and Routing](./approvals-and-routing.md)
-- [Exceptions](./exceptions.md)
+- Exceptions API entry point: `docs/api/exceptions.md`
+- Exception governance migration guide: `docs/migration/exception-governance.md`

docs/governance/exceptions.md

@@ -1,24 +0,0 @@
-# Exception Governance (stub)
-
-> Status: BLOCKED — awaiting lifecycle/routing matrix and API contract from Governance/Authority/Platform guilds. This stub sets structure and determinism requirements for DOCS-EXC-25-001.
-
-## Scope
-- Exception lifecycle, scope patterns, compliance checklist.
-- Deterministic artifacts for offline/air-gap use.
-
-## Pending inputs
-- Final lifecycle states and transitions.
-- Scope pattern examples (tenant/env/service/resource).
-- Compliance checklist from Governance Guild.
-
-## Outline
-1. Imposed rule banner (to be filled)
-2. Exception lifecycle (states, transitions, allowed actors)
-3. Scope patterns and examples
-4. Compliance checklist
-5. Offline/air-gap packaging notes
-6. Verification (hash + replay of fixtures)
-
-## Determinism
-- When content is added, record hashes in `docs/governance/SHA256SUMS`.
-- Use UTC timestamps and stable ordering of tables.