feat: SOP staleness detection — cross-reference SOPs against governed code

[4444J99]

Description

67 SOPs in praxis-perpetua govern operational procedures across the system, but there is no automated mechanism to detect when an SOP is outdated relative to the code it governs.

Additionally, some SOPs appear in the Active Directives table with both system and unknown scope (duplicates): pitch-deck-rollout, document-audit-feature-extraction, ira-grade-norming.

Proposed

1. organvm sop audit --stale — compare SOP modification dates against governed code modification dates
2. Fix scope classification to prevent unknown duplicates in SOP discovery
3. Add SOP→code mapping in seed.yaml or a dedicated sop-governance.yaml

Priority

P2 for staleness detection, P1 for the duplicate scope bug (it clutters every CLAUDE.md).

Source

Documentation handoff architecture audit (2026-04-03).

[4444J99]

Backlog engagement 2026-07-19 — disposition: evolving.

Verified current main: SOP discovery/audit/resolve commands exist, but there is no src/organvm_engine/sop/staleness.py and no shipped organvm sop audit --stale implementation. PRs #143, #137, and #126 are active attempts, all blocked/red. Next step is to consolidate one SOP-staleness branch, rebase it, and make the matrix green.