v0.45.0: Proximo is the core, six tools over every address

Proximo is the core: six tools over every address.

0.44 was 924 hand-written wrappers. 0.45 is six MCP tools (proximo_find, proximo_plan, proximo_read, proximo_call, audit_entries, audit_verify) over every address PVE, PBS, PMG and PDM publish. Every call, through every door (stdio MCP, MCP over HTTP, REST, A2A and the proximo-core shell), passes the one seam where the six pillars run: PLAN, CONSENT (once its directory is set), PROVE, UNDO, DIAGNOSE and CONTAIN. tools/list is 5,544 bytes, the whole cost of connecting.

Coming from 0.44. A wrapper you called by name (pve_backup, pve_doctor) is now proximo_find for its address, then proximo_plan and proximo_call on it. SCOPE and LEASE live in the Proxmox token itself now, its ACL and its expire: proximo-core mint <plane> prints the vendor's commands to make that token. A set PROXIMO_SCOPE_PATH, or a PROXIMO_ARM_TTL above 0, stops every door at start and names what to set instead. The ledger is keyed, always. proximo-core doctor reads the gate back: the record, each plane, the chain, and which pillars stand.

What 0.44 had that 0.45 does not. The wrappers' names, the five runbook prompts, memory and wiki, the per-tool guidance text, the multi-step mutations as single tools (an ACME order, a PMG cluster join: each step is still an address, the caller does the sequence), the reach mirror, PROXIMO_SURFACES, and proximo doctor --receipt. The full list is the cut entry in CHANGELOG.md.

Said plainly. A stock 1.5B model drove this door in a 4,096-token window against a real PVE node, read-only. Its calls landed and every refusal named the fix; it did not finish its task. The window holds; a 1.5B does not. Browsing a PBS backup's contents needs the caller to build the vendor's base64 catalog path itself, which 0.44 did for you.

Full history for this release, commit by commit, is on the internal mirror; this
public branch carries one squashed commit per release by design.
Every change here is described in CHANGELOG.md.

Where to read more

• The trust model, and the honest scope notes saying what does not hold: SECURITY.md
• Wiring it into an MCP client and minting the token: docs/SETUP.md
• The six tools and their inputs: docs/TOOLS.md
• Every published address and its verdict: docs/arena.md
• Verifying the image signature, the SBOM and the provenance yourself: VERIFY.md
• Full change detail: CHANGELOG.md

Install: uvx proximo-proxmox · pip install proximo-proxmox · ghcr.io/john-broadway/proximo:0.45.0