submit io.pilot.wallet v0.4.0

[TeoSlayer]

Wallet 0.4.0, the four bundles from pilot-protocol/wallet v0.4.0: darwin and linux, amd64 and arm64. 0.3.3 shipped one Apple-silicon binary for every platform.

What changes for users

• The wallet keeps its keys. It keeps a copy of both identity files outside the install dir. A missing one, after an uninstall or an old pilotctl's upgrade, is restored instead of a new key being created. It refuses to create a key while any copy exists. (wallet#47)
• Exits when the daemon that started it dies; wallet.help lists every method; spend-cap and Base Sepolia fixes. The full list is in metadata.json's changelog.

Publisher key

The bundles are signed with the wallet's rotated publisher key ed25519:xAD0ai5G…, now pinned in the live catalogue (pilotprotocol#528, signed with the catalogue key). verify-update checks against that pin.

Checked before opening

• pilot-app verify passes on all four bundles: sha256, manifest schema, binary pin, signature, wallet.help.
• verify-update passes against the rotated catalogue: 0.4.0 ≥ 0.3.3, same key.
• The tarballs are byte-identical to the GitHub release assets (checksums.txt).
• Each binary's format matches its platform (Mach-O x86_64 / arm64, static ELF x86-64 / aarch64).
• The EVM key survives install 0.3.3 → upgrade 0.4.0 → uninstall → reinstall on this Mac with the released darwin-arm64 binary. Tested with pilotctl v1.13.10, v1.17.0 and main, including with 0.3.3 and 0.4.0 signed by different publisher keys, as in this rotation.

After merge

publish-on-merge releases the bundles on pilot-protocol/catalog and opens the catalogue PR, signed with CATALOG_SIGN_KEY. The wallet is a stateful app, so that PR needs the catalogue:stateful-bump-approved label.

🤖 Generated with Claude Code