`docker build` without `--platform` produces a binary for the Docker daemon's
default platform, which only coincidentally matched the Vault container on a
dev machine: both followed the host architecture. On CI the two are chosen
independently, and a plugin binary built for a different architecture than the
Vault container dies before the go-plugin handshake, leaving only Vault's
opaque "Failed to read any lines from plugin's stdout" behind a 400 on mount.

Resolve the build platform from the Vault image itself so the binary and the
container that execs it always agree.

This reverts commit 3f08b29.

The mount failure this was added to diagnose was an architecture mismatch
between the plugin binary and the Vault container, now fixed at the source in
scripts/build_vault_plugin.sh. The extra CI log dump and error formatting are
no longer needed.

Bumps [conventional-changelog-conventionalcommits](https://github.com/conventional-changelog/conventional-changelog/tree/HEAD/packages/conventional-changelog-conventionalcommits) from 8.0.0 to 10.4.0.
- [Release notes](https://github.com/conventional-changelog/conventional-changelog/releases)
- [Changelog](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-conventionalcommits/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/conventional-changelog/commits/conventional-changelog-conventionalcommits-v10.4.0/packages/conventional-changelog-conventionalcommits)

---
updated-dependencies:
- dependency-name: conventional-changelog-conventionalcommits
  dependency-version: 10.4.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [cpy-cli](https://github.com/sindresorhus/cpy-cli) from 5.0.0 to 7.0.0.
- [Release notes](https://github.com/sindresorhus/cpy-cli/releases)
- [Commits](https://github.com/sindresorhus/cpy-cli/compare/v5.0.0...v7.0.0)

---
updated-dependencies:
- dependency-name: cpy-cli
  dependency-version: 7.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

chore: bump conventional-changelog-conventionalcommits to 8.0.0 to fix release notes formatting

feat: support algosdk 3.7 pq signatures and v42 heartbeat discount

Bumps [joi](https://github.com/hapijs/joi) from 17.13.3 to 17.13.7.
- [Commits](https://github.com/hapijs/joi/compare/v17.13.3...v17.13.7)

---
updated-dependencies:
- dependency-name: joi
  dependency-version: 17.13.7
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Adds a memoized `transactionSigner` getter so Pera drops straight into
AtomicTransactionComposer and any API that accepts an algosdk signer:

  atc.addTransaction({txn, signer: peraWallet.transactionSigner});

The whole group is sent to the wallet in one signTransaction call; slots
not in indexesToSign are marked `signers: []` (ARC-0001) so the wallet
shows but does not sign them. Results are returned in indexesToSign
order, and a count mismatch from the wallet is rejected with a clear
SIGN_TRANSACTIONS error instead of reaching the composer as a corrupted
group.

The getter returns the same function on every access on purpose:
AtomicTransactionComposer batches transactions by signer identity, so a
fresh closure per access would mean one wallet prompt per transaction.

algosdk stays a peer dependency; TransactionSigner is imported as a type
only and the runtime bundle gains no algosdk symbols.

Closes #44

When wc.perawallet.app/config.json is unreachable or lists no servers,
getPeraConnectConfig() yields an empty bridgeURL and connect() fell back
to https://bridge.walletconnect.org. WalletConnect retired that host in
2023; it no longer resolves, and the fork rewrites any walletconnect.org
host to a random X.bridge.walletconnect.org subdomain, all of which are
gone too. Every user reaching the fallback got a QR against a dead bridge
and an indefinite hang.

Fall back to a shuffled Pera-hosted bridge instead. Precedence is
unchanged: dApp `bridge` option, then config.json, then the fallback.

Refs #104

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>