[Backend] Implement Durable Task Snapshotting for Fast Cold Starts

[ayomideadeniran]

Contributor Focus: [Startup Performance] Reduce keeper cold-start time without serving dangerously stale task state
ETA: 2 days

Context

A fresh keeper start may need to rebuild task awareness from expensive reads, which slows operational recovery.

Problem

Cold starts can delay due-task detection if no durable local snapshot exists.

Task Breakdown

1. Define what task state is safe and useful to snapshot.
2. Add snapshot persistence and versioning.
3. Reconcile snapshots against live chain state on startup.
4. Prevent stale snapshots from being trusted blindly.
5. Measure startup improvement and document tradeoffs.

Acceptance Criteria

• Keeper startup becomes faster with durable snapshots.
• Snapshot reconciliation protects correctness.
• Snapshot versioning and invalidation are documented.
• The feature is operationally transparent.

[sweetesty]

@sweetesty has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi please can I work on this issue I’ll be done in 20mins

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sweetesty to this issue.

[drips-wave]

Congratulations, @sweetesty! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @sweetesty: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊