[PIR][WP11] Integrate autogenous's constitutional gate for capability-expanding mutations

Epic: #837 · Cross-repo counterpart: ruvnet/autogenous#11 · Plan: docs/research/perpetual-intelligence-runtime/03-program-plan.md

Goal

Integrate ruvnet/autogenous's constitutional admission gate into this repo's promotion pipeline, so that every mutation expanding an agent's capability set requires explicit constitutional approval — distinct from, and at a higher bar than, the ordinary behavioral-mutation promotion handled by WP2's research-gate.

Capability expansion means new tool access, new physical action class, or new communication peer.

Acceptance criteria

• The promotion pipeline calls autogenous's constitutional gate for any mutation classified as capability-expanding, in addition to — never instead of — ruvector-proof-gate/rvm-proof and the WP2 research-gate verdict. A test asserts a constitutionally-approved mutation still fails promotion when the proof gate rejects it.
• Classification of capability-expanding vs. behavioral happens automatically on this side too, so a mutation cannot skip the gate by not being submitted to it.
• Approval records are anchored into the witness chain per the WP8 shared record schema, logged distinctly enough that WP12 can query "zero unapproved capability expansion" directly.
• A day-0 vs. day-30 capability/tool/action-table diff is producible on demand from this side.
• Negative test: an unapproved capability-expanding mutation is blocked, and the block is visible in the acceptance-test query — proving discriminating power rather than a query that returns zero because nothing was ever classified.
• The integration is resilient to autogenous API churn: it self-labels "research prototype", so pin deliberately, isolate the call behind an adapter, and budget for breaking changes rather than assuming stability.
• Failure mode is defined explicitly: if the gate is unreachable, capability-expanding promotions fail closed, not open.

Dependencies

WP8 (ruvnet/rvm#35 + ruvnet/autogenous#10) for the shared witness record schema, and ruvnet/autogenous#11 for the API being consumed. Blocks WP12 (#843).

Start with docs/research/perpetual-intelligence-runtime/03-program-plan.md, then trace the promotion pipeline around WP2's research-gate and the ruvector-proof-gate/rvm-proof checks. Read the WP8 shared witness record schema and autogenous#11 API before defining the integration boundary. Done means capability-expansion classification, constitutional approval records, day-0/day-30 diffs, negative coverage, and fail-closed behavior are all demonstrated.