Build the 1.2 operator and access-control foundation

[terrizoaguimor]

Summary

• add the contract-first 1.2 operator roadmap and the gated relicensing plan
• add the interactive Ratatui console, Claude Code/Codex plugin bundle, and reproducible hyphae-sdk PyPI pipeline
• add durable principals, built-in/custom roles, scoped API keys, rotation/recovery, audit records, and managed session revalidation
• enforce managed API-key authentication across the local protocol, daemon, named pipes, Native HTTP v2, Rust client, and serve flag while preserving explicit legacy modes

Verification

• cargo test --workspace --all-features --locked
• cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
• protocol/product/daemon/server/client/CLI focused matrices
• Windows GNU cross-check for managed named-pipe coverage
• plugin contract checker and 4 negative tests
• Python package checker, reproducible wheel/sdist validation, 26 SDK tests, and 11 distribution-tool tests
• access-control contract checker and 15 negative tests
• cargo fmt --all -- --check and git diff --check

Honest boundary

This is the 1.2 foundation, not a declaration that every 1.2 exit gate is closed. The checked-in contract continues to mark transport-wide administration, full TUI surface parity, Native v2 MCP migration, registry publication receipts, and legal relicensing authority as pending until their roadmap gates are satisfied.