Follow-up: proper fix for crash recovery / queued chains validation

[shrugs]

Follow-up on the crash recovery bug where the omnichain indexing status snapshot invariant (omnichainIndexingCursor < earliestQueuedStartBlock) fails after crash recovery, causing the indexer to crash-loop on every restart.

Context

• Original root-cause issue: Make omnichain indexing status builder to correctly recognize all queued chains #1821 — buildChainIndexingStatusSnapshots misclassifies chains as Queued when their Ponder per-chain checkpoint sits at startBlock but other chains have advanced past that startBlock.timestamp.
• Hotfix (merged): hotfix: promote Queued chains past omnichain cursor on crash recovery #2108 — promotes such chains from Queued to a degenerate Backfill snapshot in a second pass so the invariants hold.
• Proper fix (in progress, draft): Fix queued chains validation #2109 — Fix queued chains validation by @tk-o.
• Slack thread: https://namehash.slack.com/archives/C086Z6FNBHN/p1778701416030179

Ask

Land the proper fix (#2109) and remove the hotfix workaround from #2108 once the underlying classification logic correctly handles the crash-recovery case.

[coderabbitai]

🔗 Related PRs

#1612 - Apply specific variant types for ChainIndexingMetrics [merged]
#1734 - fix: mergeBlockNumberRange function logic [merged]
#1794 - fix: resolve indexing status snapshot validation errors [merged]
#2102 - Patches for 1.13.1 [merged]
#2108 - hotfix: promote Queued chains past omnichain cursor on crash recovery [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[tk-o]

The hotfix from PR #2108 has been working fine in production workloads, so there's no particular need to change that.