1. .nsprc — restored expiry-based suppressions

  Converted all entries back to the object form with
active/expiry/notes, expiring 2027-03-01, and re-added the elliptic
advisory (1112030) that had been dropped. The audit
  still passes with no "unused exception" warning, so carrying elliptic
is free and means the file stays complete if the gate is ever tightened
from moderate to low.

  2. block-result.ts:38 — restored proposer?.toString()

  One line, closing the gap between the string type and the Address
instance algosdk actually decodes.

  3. state-delta-mappers.ts:157,173 — corrected "global" → "local" in
asLocalStateDeltaItem

Co-authored-by: mrcointreau <45950216+mrcointreau@users.noreply.github.com>

Co-authored-by: mrcointreau <45950216+mrcointreau@users.noreply.github.com>

Co-authored-by: mrcointreau <45950216+mrcointreau@users.noreply.github.com>

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Sections 1-6 are the original brief (problem, verified facts, design,
milestones, acceptance). Section 7 records how the 2.1 implementation
departed from the brief (planner hook instead of a support function) and
section 8 the first production deployment with measurements and the
plan-cache finding fixed in 4faf1f5. Host names, paths and other
environment specifics are left out.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BAkGJyPG5VRajhBwFRPiQ2

chore(deps): bump softprops/action-gh-release from 3.0.2 to 3.0.3 in the minor-and-patch group

With server-side prepared statements the plan cache builds a generic plan
after five executions. For substring(x,1,N) = $1 with N smaller than the
index prefix K, no value is available at plan time, so nothing can be
derived and the plan falls back to an unindexed scan. Under LIMIT with
default selectivity that scan is estimated cheap (cost ~12k on mainnet vs
the real crawl over billions of rows), so plancache adopts it and the
prefix index is never used again for that statement.

The hook now adds a large penalty to the total cost of any plan built with
an unbound external Param on a N < K prefix clause, which is exactly the
generic-plan case. plancache compares that against the average custom plan
cost and keeps replanning with the actual value, where the range on the
prefix index is derived as before. N >= K statements are unaffected.

Observed on the ush mainnet indexer: EXPLAIN EXECUTE x7 for N=3 switched
from the index range scan to a txn_pkey filter on the sixth execution.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BAkGJyPG5VRajhBwFRPiQ2

Signers (e.g. wallets) can mutate the transactions they are given, so
the built transactions aren't necessarily the ones that reach the network. The
mutated group was sent successfully, but `send()` then waited for confirmation of
the pre-mutation transaction ID, which is never found. The reported `txIds`,
`transactions` and `groupId` were stale for the same reason, in both `send()` and
`simulate()`.

Read the transactions back out of the signed transactions instead. The built
transaction is kept when its ID is unchanged.

Signers (e.g. wallets) can  mutate the transactions they are given, so
the built transactions aren't necessarily the ones that reach the network. The
mutated group was sent successfully, but `send()` then waited for confirmation of
the pre-mutation transaction ID, which is never found. The reported `txIds`,
`transactions` and `groupId` were stale for the same reason, in both `send()` and
`simulate()`.

Read the transactions back out of the signed transactions instead. The built
transaction is kept when its ID is unchanged, as decoding is lossy for zero
valued fields (a built `fee` of `0n` decodes back as `undefined`).

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