fix(f3): reset F3 on calibnet

[hanabi1224]

Summary of changes

Changes introduced in this pull request:

• ports fix: update F3-calibnet name and bootstrap epoch Calibnet filecoin-project/lotus#13469

Reference issue to close (if applicable)

Closes

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 calibration network settings: new bootstrap epoch, network name change, and cleared initial power table.
  • Adjusted F3 consensus/bootstrap initialization parameters for the calibration network.

• Tests

  • Temporarily disabled active F3 readiness polling and related runtime checks in the calibration test script.

[coderabbitai]

Walkthrough

Updated calibnet F3 configuration: bootstrap epoch changed to 3451774, network name to "calibrationnet2", and initial power table set to null. A test script that performed F3 readiness checks was disabled by commenting out its polling and verification steps.

Changes

Cohort / File(s)	Summary
F3 Manifest & Config f3-sidecar/f3manifest_calibnet.json, src/networks/mod.rs	BootstrapEpoch updated to 3451774, NetworkName changed to "calibrationnet2", and InitialPowerTable removed/set to null / None. Comment timestamps/epoch references updated.
Test Script Disabled scripts/tests/calibnet_no_discovery_check.sh	F3 readiness poll loop and subsequent F3 subcommand invocations commented out, disabling runtime verification and output.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• fix(f3): skip importing F3 data when initial power table is not set in the F3 manifest #6397: Changes import behavior when initial_power_table is unset — directly related to setting the field to null.
• fix(f3): prepare for f3 network name change on calibnet #6362: Touches calibnet F3 manifest and network-name handling relevant to renaming to "calibrationnet2".
• fix: add F3 pending activation status to healthcheck API #6415: Adds healthcheck logic that reads bootstrap_epoch for F3 activation status, related to the updated epoch.

Suggested reviewers

• LesnyRumcajs
• sudo-shashank

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix(f3): reset F3 on calibnet' directly and clearly summarizes the main purpose of the changeset, which is to reset F3 configuration on the calibration network across configuration files and code.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hm/f3-calibnet-reset

---

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