[indexer-alt-framework] remove skip_watermark and standardize first_checkpoint behavior

[wlmyng]

Description

This PR standardizes behavior around --first-checkpoint and its effects on
A. The checkpoint to start ingesting from
B. The checkpoint for a pipeline to resume processing from

• When an indexer starts, it will always start ingesting from the next checkpoint after the smallest committed checkpoint across all pipelines added to it.
• Pipelines without a watermark are by default to be backfilled from genesis.
• Providing --first-checkpoint overrides this behavior, and tells the indexer that these pipelines are to process checkpoints from --first-checkpoint instead.

Test plan

New tests

---

Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

• Protocol:
• Nodes (Validators and Full nodes):
• gRPC:
• JSON-RPC:
• GraphQL:
• CLI:
• Rust SDK:

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sui-docs	Ready	Preview	Comment	Nov 12, 2025 7:38pm

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
multisig-toolkit	Ignored	Preview		Nov 12, 2025 7:38pm
sui-kiosk	Ignored	Preview		Nov 12, 2025 7:38pm

[wlmyng]

@emmazzz @amnn this hopefully makes it easier to review the desired behavior involving --first-checkpoint.

For each pipeline, we calculate the next checkpoint to ingest as either the checkpoint after its watermark, or if that doesn't exist, then the provided first checkpoint, and if that doesn't exist, then 0 (genesis).
The checkpoint that ingestion starts as is the minimum across all the next checkpoints calculated this way (per-pipeline).

We can remove the consistency checks first_checkpoint <= committer_watermark because the ingestion piece will always be the minimum among the next checkpoint to process.