Title: Indexer stopped ingesting events from canonical rollup 0x91fF… since ~Sep 7–8, 2026 (withdrawals shown as staked, new stakes stuck PENDING) #118

Summary
api.stake.aztec.network appears to have stopped recording events from the canonical rollup 0x91fF8bbD8Ebb07893010D50A48A1609e5EBd8E34 somewhere between blocks 25,921,445 and 25,935,689 (Sep 7–8, 2026 UTC). /status keeps advancing to the chain head, and events from the older rollup 0xAe2001f7e21d5EcABf6234E9FDd1E76F50F74962 are still recognized. Because of this:

• WithdrawFinalized on 0x91fF… after that point doesn't mark stakes UNSTAKED, so users who have fully withdrawn still see the amount under "Staked" in the dashboard.
• Deposit events on 0x91fF… after that point aren't recorded, so new stakes stay PENDING even though the validators are active on-chain.

Evidence

• Last correctly handled withdrawal on 0x91fF…: block 25,921,445 (Sep 6 22:58 UTC). It shows UNSTAKED.
• 0x5f9ff7fcb260e2bf57c1813d5bf884ad8636000d: its withdrawals at blocks 25,905,008 and 25,905,010 show UNSTAKED. The ones at 25,976,593 and 26,077,259–26,077,566 show SUCCESS even though WithdrawFinalized was emitted for them.
• 0x7b61dd775422f465d6b9f28c8efee39263ef2579: withdrew attester 0x90af737a948360e8221090384dce9f898e1dff24 at block 26,077,353, but totalErc20Delegated still shows 200000e18.
• Validator 0x5c802FB7F1928A459521d42BDB853EC000bF0661 (staked at block 25,935,689): getStatus on 0x91fF… returns 1 (VALIDATING), but the API reports PENDING. The same holds for every ERC20 stake after that block that I checked (18 of 18).
• Counter-example: a withdrawal on the old rollup 0xAe20… at block 25,947,503 (Sep 10) is correctly marked UNSTAKED.

Expected
Stakes are marked UNSTAKED after WithdrawFinalized and SUCCESS after Deposit on the canonical rollup.

Notes
The indexer code hasn't changed since July 13, so this looks like a deployment or runtime issue, for example the Ponder factory child for 0x91fF… no longer being synced. A re-sync of the Rollup contract from about block 25,920,000 would probably fix it.