A third-party Pi MCP adapter drops its interpreter for Pi's native codemode

What this changes for operators

• Adapter users on current Pi 1.4.0: port script settings and hook matchers before installing adapter 6.0.0, then compare the native composition path with the interpreter or bridge you maintain. A second interpreter is now a concrete maintenance cost that can be removed.
• Test allowed and forbidden calls through proxy, deferred and scripted paths, plus an Executor pause with and without a person present. Recorded tool identities and refusal results would settle the deployed permission boundary; a visible --tools list does not settle it.
• Review project script contents as well as their configuration entries, and reverse the adapter’s native-MCP takeover when removing it. Count migration and review time against accepted work before claiming a net attention saving; the author’s context benchmark is configuration-specific.