feat(claims): index setactlimit/seedmbrclm and mirror mbrclaim into member_action_claims

[lucca65]

Summary

Claim limits, rollout step 4 (plan Task 7). event-source indexes the two new cambiatus.cm actions and keeps the backend's member_action_claims table in step with the contract's mbrclaim table.

• src/claim_mirror.js applies the contract's own arithmetic and decides nothing:
  • claimaction adds 1 to pending.
  • The first verifyclaim that moves a claim from pending to final closes it. pending goes down by 1 (never below 0); then approved goes up by 1, or last_rejected_at becomes the block's whole second. A replay finds the claim already final and skips it.
  • reward adds 1 to approved.
  • seedmbrclm overwrites the row.
  • Every write runs on the block transaction, after the existing replay guards and after any ResolveError path.
• setactlimit writes actions.max_claims_per_account and reclaim_cooldown_seconds; max 0 clears both. An action that isn't indexed raises ResolveError (skip and page).
• src/config/lane.js points at the lane chain (:8899) and cambiatus_lane_cpa. It refuses :8888 and the shared DBs.
• scripts/compare-claim-mirror.sh <chain> <db> <account>... compares chain mbrclaim with Postgres for each account.

The S3 contract (live since 2026-10-17) and the backend table (#546, on backend main) are already in place. Rows written on chain before this deploy are filled by the S4 backfill (seedmbrclm), which this PR indexes.

Merge after #79. Without #79 the indexer can drop the second part of a split block, and the mirror would drift with it (a lane run without #79 lost 7 claims).

Test plan

• Lane, this PR plus fix(indexer): apply the rest of a block delivered in two parts #79 (fresh chain :8899 on the committed prod wasm 5f661569, fresh DB):
  • test_community 97/97 and test_claim_limits 81/81 generate the activity;
  • compare-claim-mirror.sh prints OK for alice, bob, carol, dave and eve (exit 0);
  • 7 actions have a limit;
  • 0 error lines in the event-source log;
  • claims (325) and checks (16) match chain exactly.
• yarn format is clean.
• Task review (spec + quality): approved, no Critical or Important findings. The Minor lane-guard item is fixed (it also refuses cambiatus_mirror and cambiatus_review).
• code-simplifier: no changes.

Known and pre-existing, not changed here: resolveCreatedActionId reads the current chain, so an action created and deleted before it is indexed shifts later create ids. The lane test does this in one block; in prod it would need both inside one 500 ms poll.

Deploy (needs a go)

On the box: git status (clean?), git pull --ff-only origin master, pm2 restart event-source. Then watch that restart_time stays stable. No yarn install is needed.

🤖 Generated with Claude Code