Resume F3 on Calibration

[BigLep]

Background

Per https://filecoinproject.slack.com/archives/C0556MSR945/p1761828202761209, F3 is not progressing on Calibration. This was discovered by a human; not by any automated notification.

Done Criteria

1. F3 on calibration is progressing again
2. F3 public calibration dashboard(s) are working
3. Monitoring/alerting is setup on F3 in Calibration
4. F3's activation date for calibration can be set via smart contract repeatedly like it was done for onetime in mainnet so that we can more easily reset in the future.

Why Important

1. This is affecting the F3-based bridge on IPC today that is in the final stages of implementation and need a place to test against.
2. It will affect everyone when we do a nv28 upgrade in 2026.

Approach

Attempt 1

What: find the small SPs who were in the power table when F3 got stuck and ask them to enable F3.

Challenges:

• Human intensive and no guarantee of success
• We are likely going to be hosed by exponential backoff since there is no upper bound on exponential backoff (issue to fix this), so we need to understand what the round time is at this point.

Attempt 2

What: include a new network name for f3 as a patch to nv27 on Calibration

Notes

1. Discussion about this topic in FDS-7 are here. Many of the notes were incorporated back into the issue description.

[BigLep]

This was discussed in Buenos Aires on 2025-11-15. I'll post the notes and next steps on this today.

[BigLep]

The issue description has been updated to account for FDS discussion.

@rjan90 is in progress on "approach 1" discussed above.