AlgoScan

Co-authored-by: Algorand Generation Bot <codegen@algorand.com>

# Conflicts:
#	daemon/algod/api/server/v2/generated/data/routes.go
#	daemon/algod/api/server/v2/generated/experimental/routes.go
#	daemon/algod/api/server/v2/generated/nonparticipating/private/routes.go
#	daemon/algod/api/server/v2/generated/nonparticipating/public/routes.go
#	daemon/algod/api/server/v2/generated/participating/private/routes.go
#	daemon/algod/api/server/v2/generated/participating/public/routes.go

Collapse the two-package / two-branch setup into one package published
from main, with releases triggered by git tags instead of branch pushes:

- package.json: rename @perawallet/connect-beta -> @perawallet/connect,
  set version 1.6.0-beta.0, update description
- replace the two branch-push workflows with one tag-triggered release.yml;
  a prerelease tag (vX.Y.Z-beta.N) publishes under the `beta` dist-tag,
  a clean tag (vX.Y.Z) under `latest`; a guard fails on tag/version drift
- CONTRIBUTING: document the single-main branch model and release procedure

Per docs/superpowers/specs/2026-06-29-release-consolidation-design.md.
GitHub Release step left commented pending action SHA pinning.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The WalletConnect client lib swap (#191) dropped a transitive ambient
Window.Buffer type, breaking the release build (TS2339). Match the
existing (window as any) polyfill pattern used for global.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Design for collapsing the two-branch / two-package setup into a single
@perawallet/connect package on a single main branch, with tag-triggered
releases (beta prereleases -> beta dist-tag, stable -> latest).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

FallbackResolver resolved the configured FallbackDNSResolverAddress but only
logged failures at Debug and carried on with a nil *net.IPAddr: the non-secure
path then dereferenced it and panicked, while the secure path built a bogus
'<nil>:53' resolver. A node with a misconfigured fallback address could crash
during SRV bootstrap.

When the fallback address cannot be resolved, log a warning and fall back to
the default resolver, matching the system -> fallback -> default chain that
readFromSRV already relies on.

Replace the bare 1232 literal in query() - and its duplicate assertion in
the test - with a documented package constant. 1232 is the DNS Flag Day 2020
value; naming it keeps the single source of truth and explains the choice at
the point of use.