chore: update known blocks

[LesnyRumcajs]

Summary of changes

Changes introduced in this pull request:

Reference issue to close (if applicable)

Closes #6378

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Summary by CodeRabbit

• Chores
  • Updated network mappings with new calibnet configuration (epoch 3283200) and mainnet configuration (epoch 5616000).

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR updates Forest's checkpoint mappings in build/known_blocks.yaml by adding new epoch-to-CID entries for both calibnet (epoch 3283200) and mainnet (epoch 5616000) networks. These checkpoints improve snapshot loading performance by reducing boot time during node initialization.

Changes

Cohort / File(s)	Summary
Checkpoint Data Update build/known_blocks.yaml	Added calibnet mapping for epoch 3283200 and mainnet mapping for epoch 5616000 with corresponding CIDs. No structural changes to file format or existing mappings.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• cron: update known_blocks.yaml #6378: This PR directly addresses the monthly checkpoint update procedure described in this issue, following the documented workflow for updating build/known_blocks.yaml.
• cron: update known_blocks.yaml #6016, #6270, #5884, #6127: Historical checkpoint update issues modifying the same file with similar epoch/CID mapping additions.

Possibly related PRs

• chore: update known blocks #6163: Prior checkpoint update PR adding calibnet and mainnet epoch-to-CID mappings to build/known_blocks.yaml.
• chore: update known blocks #6228: Earlier checkpoint update PR modifying the same file with different epoch/CID entries for network checkpoints.
• chore: update know blocks #6272: Related checkpoint update PR adding epoch-to-CID mappings for calibnet and mainnet networks.

Suggested reviewers

• hanabi1224
• akaladarshi
• sudo-shashank

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update known blocks' accurately describes the main change—updating the known_blocks.yaml configuration file with new checkpoint entries.
Linked Issues check	✅ Passed	The PR fulfills issue #6378 by updating build/known_blocks.yaml with new checkpoints for both mainnet and calibnet epochs as required.
Out of Scope Changes check	✅ Passed	The changes are limited to updating build/known_blocks.yaml with checkpoint mappings, which is exactly within the scope of issue #6378.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d561d3 and 9706a45.

📒 Files selected for processing (1)

• build/known_blocks.yaml

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: hanabi1224
Repo: ChainSafe/forest PR: 5944
File: src/chain/store/index.rs:0-0
Timestamp: 2025-08-18T03:09:47.932Z
Learning: In Forest's tipset_by_height caching implementation, hanabi1224 prefers performance-conscious solutions that leverage finality guarantees rather than expensive chain walking for fork detection. The approach of constraining cache lookups to finalized epochs (using CHECKPOINT_INTERVAL >= CHAIN_FINALITY) provides fork safety without the performance cost of ancestry verification.

Learnt from: hanabi1224
Repo: ChainSafe/forest PR: 6079
File: src/chain_sync/metrics.rs:6-7
Timestamp: 2025-09-16T12:55:26.955Z
Learning: HEAD_EPOCH references in shell scripts (like scripts/tests/calibnet_eth_mapping_check.sh) that extract data from `forest-cli info show` are unrelated to Rust metrics constants with the same name and should not be flagged when metrics cleanup is performed.

Learnt from: LesnyRumcajs
Repo: ChainSafe/forest PR: 5907
File: src/rpc/methods/state.rs:523-570
Timestamp: 2025-08-06T15:44:33.467Z
Learning: LesnyRumcajs prefers to rely on BufWriter's Drop implementation for automatic flushing rather than explicit flush() calls in Forest codebase.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: All lint checks
• GitHub Check: Coverage
• GitHub Check: Build Ubuntu
• GitHub Check: Build MacOS
• GitHub Check: cargo-publish-dry-run
• GitHub Check: Build forest binaries on Linux AMD64
• GitHub Check: tests-release

🔇 Additional comments (2)

build/known_blocks.yaml (2)

10-10: LGTM! Calibnet checkpoint correctly added.

The new calibnet checkpoint for epoch 3283200 follows the correct pattern with an 86400 epoch increment from the previous entry, and the CID format is consistent with existing entries.

---

49-49: LGTM! Mainnet checkpoint correctly added.

The new mainnet checkpoint for epoch 5616000 follows the correct pattern with an 86400 epoch increment from the previous entry, and the CID format is consistent with existing entries.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}