test(indexer): add user.processor spec and reconcile-users CLI

[Mossad-esc]

Summary

Closes #1593

user.processor.ts (235 lines) had no spec while the raffle and ticket
processors both did. User aggregates underpin the leaderboard and creator
profiles — double-counting from a replayed event or an uncompensated reorg
corrupts them permanently.

Changes

indexer/src/processors/user.processor.spec.ts (new, 25 tests)

Scenario	Handler(s)
First event for a new address — row upserted, counters incremented	all
Subsequent events — totalRafflesEntered only bumped on first ticket per raffle	handleTicketPurchased
Replayed duplicate (same txHash) → no-op, no double-count	handleTicketPurchased, handleRaffleFinalized
Compensating rollback (lastTxHash cleared) → event re-applied	handleTicketPurchased
Event that survived the reorg → skipped	handleTicketPurchased
null winner → early return	handleRaffleFinalized
Empty prize string coerced to '0'	handleRaffleFinalized
Own-transaction lifecycle: connect / commit / release / rollback on error	all
Address stored byte-for-byte as supplied; cache invalidated with exact address	normalisation

indexer/src/cli/reconcile-users.command.ts (new)

Recomputes all five aggregate columns from tickets + raffles and diffs
against stored users rows.

pnpm run users:reconcile              # report drift, exit 2 if any
pnpm run users:reconcile -- --dry-run # same, no writes
pnpm run users:reconcile -- --address GABC...
pnpm run users:reconcile -- --fix     # rewrite drifted rows (nulls lastTxHash)

indexer/package.json

Added users:reconcile script.

Test results

25/25 passing. The 12 lint errors in CI are pre-existing parserOptions.project
failures on integration files excluded from tsconfig — zero issues in the two
new files.