Stellar Index v0.32.1

[v0.32.1] — 2026-08-13

Fixed

• /v1/accounts/{g}/transactions 6.7× faster (sub-second audit
  2026-08-13, r1-measured): both union arms carried the WIDE tx column
  set (memo, result_code, source_account, …) through their own scan and
  sort of stellar.transactions, and the outer DISTINCT then
  materialised both. The query now resolves the KEYSET in the union and
  hydrates the wide columns once over the surviving ≤limit keys —
  1.479s → 0.219s for the same 50 rows, with the cross-arm dedupe now
  provided by the hydration pass's LIMIT 1 BY.

• /v1/accounts/{g}/operations 2.7× faster — same two-phase shape,
  and it matters more here: opCols carries body_xdr, the column the
  code itself measures at ~600ms over the 24B-row table, and both arms
  were paying it. 0.407s → 0.153s (r1, 50 rows).

• CI integration gate stopped failing on the clock: the suite's
  go-test deadline is raised 20m→35m. It hit the ceiling on three
  consecutive pushes with the running test 1s in, while the same suite
  completes in ~13m locally (CI runners are ~1.5× slower) — a gate that
  reports "the clock ran out" as a failure stops being a signal. The
  next raise should split the suite by package instead.

• POST /v1/register returned keys that could not authenticate
  (found in the v0.32.0 post-deploy battery): the mint wrote only the
  Postgres MANAGEMENT row, but r1's auth middleware validates against
  the REDIS store (backend=redis), so a freshly registered key 401'd
  on first use — a 200 response carrying a dead credential, worse than
  an honest failure. The mint now mirrors the same plaintext into the
  validator's own store (RedisAPIKeyStore.CreateWithSecret) whenever
  that store is wired, and a mirror failure fails the request instead
  of handing back a key that cannot work. The agent-onboarding flow is
  functional again.