Release v1.5.2

fix: bump algokit-utils to 9.2.2, fixes PQ txn confirmations

Release v1.5.1

Moving pool state to a single accountInformation read on the registry left two
gaps where a pool the bulk request missed stayed missed.

`processPoolData` fell back on the presence of the entry, not on what it held. A
pool whose state came back partial decodes to `{}`, which is truthy, so it kept
the empty entry and returned no lastPayout - which the Status column renders as
"Payouts stopped".

`algodVer` lost its fallback entirely. It came off LocalPoolInfo, and
StakingPoolInfo now reads it only from the bulk map; the per-pool read inside the
metrics query keeps lastPayout and discards the algodVer it fetched. Any pool the
map lacks reported its node version as "--" for the rest of the session.

Both now gate on `isPoolGlobalStateComplete`. It tests lastPayout rather than the
field being displayed, because lastPayout is written when the pool is created -
stakingPool.algo.ts sets it to the creation round as the first epoch's baseline -
so every pool has one and its absence can only mean an incomplete read. Gating on
algodVer instead would have been wrong: it is only written once the node daemon
reports in, and 88 of MainNet's 283 pools legitimately have none, so keying on it
would re-read a third of all pools on every visit and still show "--".

The 1020 fixture claimed a missing lastPayout stood for "a pool that has never
paid out", which the contract does not do. It now models the case that does
occur - a pool whose daemon has never reported, so no algodVer - and the tests
around it cover the fallback firing on an incomplete entry and staying put on a
complete one.

Every validator's Status column rendered a red gauge tooltipped "Not active".

Nodely serializes the uint64 columns of poolvotingperformance/24hr as bare JSON
numbers, but the lookup compared `validatorid` strictly against a string:

    (q) => q.validatorid === baseValidator.id.toString()   // 147 === "147"

so `validator.perf` was undefined for all 56 validators the feed covers. The
interface declared those columns as `string`, which is what hid it from tsc.

The miss then presented as a measurement rather than as missing data, because
the branch that renders "Not active" was only reachable via NaN:

    const perfScore = Number(validator.perf)   // Number(undefined) -> NaN
    if (perfScore >= 0.7) { Normal }           // NaN >= 0.7 -> false
    else if (perfScore < 0.7) { Watch }        // NaN <  0.7 -> false
    else { Error; 'Not active' }               // NaN only

The lookup moves to `findValidatorPerf`, which coerces both sides - the feed has
flipped these columns between quoted strings and raw numbers once already, and a
strict compare turns that into a silent blank for every row. ValidatorStatus now
tests for absence directly, so "Nodely has no row for this validator" and "this
validator is performing badly" stop sharing a branch, and formats the tooltip
through formatAmount (it was rendering 99.87096774193549%).

Two defects in the sibling payout indicator go with it: `!roundsSinceLastPayout`
treated a fresh 0 as "Payouts stopped, behind 0 seconds", and a Number was
compared against bigint literals. Threshold bands and colors are unchanged.

v1.5.0

perf(ui): load validator and pool state in bulk, persist the query cache

The dashboard opened with roughly 900 algod requests: four simulate calls per
validator (config/state/pools/nodePoolAssignments), one global state read per
pool, then enrichment lookups on top. All four validator reads come out of the
same `v` + validatorId box, and every pool is created by the registry's app
account, so both collapse into a single request each.

Bulk reads:

- `fetchAppBoxes` reads box names and values together using algosdk 3.6's
  `include('values')` with cursor pagination, pinning every page after the
  first to the round the first returned so a multi-page read is one snapshot.
  It throws if a node returns names without values rather than rendering an
  app's state as empty.
- `fetchAllValidatorData` decodes those boxes through the generated ARC-56
  struct and seeds the per-validator query caches inside the queryFn, so
  components and route loaders reading the individual keys resolve from cache.
  The validator detail route seeds the same four keys from one box read when
  arriving cold.
- `fetchPoolGlobalStates` reads every pool's `lastPayout`/`algodVer` from one
  `accountInformation` call on the registry address, and warns when algod
  truncates the created-app list. `processPoolData` takes that state as an
  argument, falling back to a per-pool read only for what the bulk read missed.
- xGov request boxes move off the typed client's `requestBox.getMap()`, which
  issued a request per box across the whole registry.
- `validatorMetricsQueryOptions` takes its per-validator inputs explicitly
  instead of re-deriving them through `ensureQueryData`, which would refetch
  once those entries are garbage collected. The per-row Rewards and Status
  queries observe rather than fetch, keeping metrics traffic inside the
  metered queue.

Caching and pacing:

- `queryPersister` persists an allowlist of query key roots to IndexedDB,
  chosen over localStorage because protocol data is full of bigints and
  structured clone handles them natively. Busted on `__APP_VERSION__`.
  main.tsx hydrates before the router runs, so the table paints from disk and
  refreshes underneath; index.html holds a static spinner and applies the
  stored theme before first paint.
- `useQueuedQueries` meters only work that will actually hit the network,
  returns results positionally aligned with its input, and learns a per-host
  batch size by AIMD (`utils/rateLimit`) - additive increase on clean ticks,
  halving on 429/503, persisted so the next load starts near a known-good rate.
- `axiosNfdApi` gains a localStorage-backed HTTP cache and exponential backoff.
  The retry has to register after `setupCache`: registered first it swallows
  the rejection before the cache settles the entry it opened, and the retry
  then blocks forever on that entry. Covered by a test.

algosdk 3.6 types `asset.params` as optional, hence the `?.` on every params
access. axios and axios-cache-interceptor are bumped alongside.

Specs added for the box reads, pool global state decoding, the batching queue,
the persister, the rate limit controller, and the NFD interceptor ordering.

AGENTS.md documents the three deliverables, the localnet-dependent dev loop, the per-package commands CI enforces, and which paths are generated build output. CLAUDE.md points at it.

.gitignore only had `.env.*`, which doesn't match a bare `.env` - and bootstrap writes mnemonics into nodemgr env files.