Repository navigation
Paseobility 2.12.13
This patch fixes an existing installation's update failure: Paseo rejects plugin add when the same ID is already registered. The old updater and its rollback both attempted that operation.
- Preserve and verify a managed Git checkout before unregistering it; keep directory development checkouts untouched.
- Remove only the selected plugin registration, install the pinned replacement, and confirm it is running.
- Restore the prior plugin and skills after a failed activation, including failures that leave a candidate registered.
- Preserve concurrent changes. Lost add/remove/rollback responses retain the lock and require inspection instead of automatically replaying uncertain actions.
This includes all v2.12.12 changes: Ego recovery rules, Paseo 0.12–0.15 compatibility, Cua Driver 0.39.0 installer pin, Windows MCP UTF-8 diagnostics and optional browser dependency updates.
Validation: plugin typecheck and 41 regression cases; actual directory and managed Git replacement on an isolated Paseo 0.15.2 daemon; five-job macOS/Windows/compiler CI. The temporary daemon was stopped. The release ZIP and SHA-256 checksum were verified.
Upgrading an older installation: its update button reads the worker from the old installed source. Update that worker from this tag first, or update a Git-installed plugin through Paseo's native plugin management. The selected four-host rollout includes the backed-up worker bootstrap before the pinned package update.
No production Paseo daemon or agent is restarted. Actual fresh-agent browser choice and full native GUI actions remain user validation. Evidence and limits.