Reconciles two independent feature sets that both targeted version 0.4.3 for unrelated reasons. Carries forward the vendor-neutral PaymentProcessor interface (custodian.processors.base, custodian.authority.ledger, entry-point discovery for external packages) from 0.4.3 unchanged, and adds the harness-neutral action-evaluation engine and Paladin credential-broker bridge moved out of custodian.codex_guard into custodian.guard_core, part of Kernel -- it already served every guard harness (Codex, Claude, OpenCode) via a harness keyword, but living inside codex_guard's own package meant every other guard adapter had to depend on custodian-codex-guard just to reach it. custodian.codex_guard.mcp_server/.paladin_bridge re-export the same names for backward compatibility; behavior is unchanged, only the canonical location moved. A new permanent architecture-boundary test enforces this going forward. v0.4.3 shipped only the payment-processor half and is genuinely incompatible with custodian-codex-guard>=0.1.4 and custodian-claude-guard>=0.1.0, both of which require custodian.guard_core.evaluation directly -- rather than rewrite the already-public v0.4.3 tag, this ships as 0.4.4; v0.4.3 stays as-is, superseded but not altered. The exact attached wheel and source archive passed the full 3,000+ test suite, the complete custodian-release.py prepare battery (fresh install, upgrade from the real published 0.4.2, managed two-slot install/reinstall/uninstall with data preservation, PEP 668 compliance), and were verified directly against both real downstream packages this fixes: custodian-codex-guard 0.1.4 (a genuine MCP initialize handshake) and custodian-claude-guard 0.1.0 (real PreToolUse allow/deny hook decisions), both installed fresh from their own GitHub tags. Not yet published to the real PyPI index.