Rampage 0.3.1 Recovery 4 — Pair Again, For Real

Pair again means pair again

Recovery.4 closes the lifecycle race exposed by a real owner-and-laptop re-pair. A retiring worker could previously recreate its controller pin after reset, causing the next encrypted invitation to fail with “this machine is already enrolled.”

This candidate makes that recovery path deterministic:

• Bounded sidecar exit barrier — Rampage waits for its managed process tree to stop before rotating enrollment state.
• Setup-only self-healing — while the authoritative setup marker is present, Rampage may remove only a fixed allowlist of stale worker credentials before accepting a new invitation.
• Active identities stay protected — owner and worker credentials are never self-deleted outside setup mode.
• Install-path-aware firewall repair — the private-network marker records the actual installation directory and regenerates the three scoped Windows rules after an install-path change.
• Same four-digit flow — install, choose Join my fabric, choose Find my fabric, compare the four digits, and approve on the owner PC.

Windows download

Download Rampage_0.3.1_x64-setup.exe

SHA-256: f7863556c21828048f34725800db6cc3b9abac3aea449f35220f38086e6245c8

The candidate packages are intentionally unsigned/not notarized. Every package is source-bound to merged commit 1e230bcd2a2480007f335333fda8c099f202a008 through the included distribution manifests and GitHub Sigstore/SLSA build provenance.

Qualification

• 24 native desktop recovery/pairing tests passed
• full Rust workspace, clippy, UI, TypeScript/Python SDK, intelligence, encrypted storage, authenticated mesh, model gateway, restart/fencing, and E2E gates passed
• independent Windows, Linux, and Apple Silicon native packaging passed
• Windows installer smoke passed: six payloads, desktop and shell shortcuts, controller/intelligence ready, signed node and offer, clean uninstall, and no leaked sidecars

Full changelog: v0.3.1-recovery.3...v0.3.1-recovery.4