Bloom v0.3.2

Bloom v0.3.2

• Explicit HD account selection for wallet and compatible Petal operations. Account 0 retains the original wallet identity; use an explicit account index in wallet paths, for example wallets/main/0/address.
• Feedback joins Enso, NEAR, Polymarket, and Hyperliquid as a default Petal.
• Optional MCP VFS proxy for connecting an MCP client to Bloom; enable it through the configuration flag described in https://github.com/bloom-directory/bloom/blob/v0.3.2/docs/guides/mcp.md.
• Fix macOS login startup after reboot by securely recreating volatile authority runtime directories from the validated enrollment. Wallet custody and authentication remain unchanged.

Upgrade notes and known issues

Old/custom Petals need the explicit-account interface. Legacy Petal settings and sessions do not migrate automatically. Reconcile pending funded operations before replacing legacy packages, and retain your recovery records. See https://github.com/bloom-directory/bloom/blob/v0.3.2/docs/specs/2026-09-25-minimal-hd-account-petals.md.

Linux reinstall following uninstall --retain-custody can fail with Unit bloom-broker@1000.service not loaded (the UID varies). Normal live reinstallation and v0.3.1 upgrades were tested separately and passed; this retained-restore path remains unresolved. Do not use retained uninstall as an upgrade procedure for this release.

Signed packages

Supported bundles: Linux x86_64, Linux aarch64, and macOS aarch64. Each archive has .sha256, .sig, and .pub sidecars. Obtain the trusted key independently from packaging/triad/release/bloom-release-v1.pub at this release tag. Verify the outer checksum signature in the bloom-release-archive-v1 SSHSIG namespace and the internal payload manifest in bloom-release-payload-v1. The accompanying .pub alone does not establish trust.