PostgreSQL derives equalities through equivalence classes but never
inequalities.  For the indexer's transaction pages

    FROM txn t JOIN block_header h ON t.round = h.round
    WHERE t.round >= $1 ORDER BY t.round, t.intra LIMIT n

nothing tells the planner that h.round >= $1, so a plan that drives the
join from block_header scans that index from its first key and probes txn
for every round below $1.  With an accurate n_distinct on round that plan
is the cheapest LIMIT plan on paper and the slowest one in practice
(6-12 s instead of 1-3 ms on a 3.7B-row table).

ineq_propagation.c adds, before planning, every  column OP value  condition
(OP one of <, <=, >=, >) to all columns joined to it with = of the same
type and operator family in the WHERE clause or an inner join.  Only
conditions that hold for every output row are used and produced (nothing
at or below the nullable side of an outer join), so results never change.
The value side must be safe to evaluate twice; uncorrelated sub-selects
become a second init plan.  GUC pg_algorand.propagate_inequalities.

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

An indexer search by group id, final once visible: five enriched rows,
the rest counted. The URL carries base64url (plain base64 accepted) —
a raw group id's slash can't ride in a path segment.

Claude-Session: https://claude.ai/code/session_01HSTYunMrd3nHfxWVNJGssA

0.8.7 shipped a stale dist: dist/ is gitignored and there was no
prepublish build step, so npm published whatever build happened to be in
the working directory (a Feb 11 build). The published 0.8.7 tarball is
byte-identical to 0.8.6 apart from the version string, so the cache
transaction sweeper from 393c571 never reached consumers.

Add prepublishOnly so the package is always rebuilt from source before
publishing, and bump to 0.8.8 (npm forbids republishing 0.8.7).

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

Bumps androidx.navigation:navigation-compose from 2.9.8 to 2.10.0.

---
updated-dependencies:
- dependency-name: androidx.navigation:navigation-compose
  dependency-version: 2.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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

fake-indexeddb's Database.transactions array is append-only: finished
transactions are never removed, so long-lived Node processes retain
~5-7KB per cache operation until restart and rescan the growing array on
every operation. This is the root cause of the daily memory sawtooth on
allo staging (diagnosed 2026-09-02; unfixed upstream as of 6.2.5).

Add a 10s sweeper interval, active only when the IndexedDB shim is in
use, that drops finished transactions from the array. Safe because every
upstream reader filters on transaction state. Verified: 500 saves leave
502 retained transactions before, 0 after the sweep, with all rows still
queryable.

Interim mitigation until the cache gets a proper Node backend (bounded
Map/LRU instead of the IndexedDB shim).

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

This commit syncs the stable release version back to main branch
to ensure the next beta cycle starts from the correct version base.

Release: 2.4.0
Tag: v2.4.0

## [2.4.0](https://github.com/algorandfoundation/algokit-lora/compare/v2.3.3...v2.4.0) (2026-09-02)

### 🚀 Features

* support arc-89 ([#582](https://github.com/algorandfoundation/algokit-lora/issues/582)) ([4c1f16f](https://github.com/algorandfoundation/algokit-lora/commit/4c1f16fb1f9c8ad002b4a68e6795363218c64c01))

This promotion merges tested changes from main branch to release for production release.

## [2.4.0-beta.3](https://github.com/algorandfoundation/algokit-lora/compare/v2.4.0-beta.2...v2.4.0-beta.3) (2026-09-02)