CHANGELOG.md (1)

36-37: Link to PR instead of issue for 5956 (per changelog guidance).

The entry uses an issue link but there’s no linked issue; the guidelines say to use the PR number when no issue exists. Switch the URL to /pull/5956.

-- [#5956](https://github.com/ChainSafe/forest/issues/5956) Add `forest-tool archive f3-header` subcommand for inspecting the header of a standalone F3 snapshot(FRC-0108).
+- [#5956](https://github.com/ChainSafe/forest/pull/5956) Add `forest-tool archive f3-header` subcommand for inspecting the header of a standalone F3 snapshot(FRC-0108).

src/tool/subcommands/archive_cmd.rs (1)

238-243: Add contextual error messages for easier troubleshooting.

Wrap File::open and header decoding with context so users see which path failed and whether it was I/O vs decode.

-            Self::F3Header { snapshot } => {
-                let mut r = BufReader::new(File::open(&snapshot)?);
-                let f3_snap_header = F3SnapshotHeader::decode_from_snapshot(&mut r)?;
-                println!("{f3_snap_header}");
-                Ok(())
-            }
+            Self::F3Header { snapshot } => {
+                let mut r = BufReader::new(
+                    File::open(&snapshot)
+                        .with_context(|| format!("failed to open F3 snapshot '{}'", snapshot.display()))?,
+                );
+                let f3_snap_header = F3SnapshotHeader::decode_from_snapshot(&mut r)
+                    .with_context(|| {
+                        format!("failed to decode F3 snapshot header from '{}'", snapshot.display())
+                    })?;
+                println!("{f3_snap_header}");
+                Ok(())
+            }

scripts/tests/harness.sh (3)

33-35: Fail fast if inspection of v1 snapshot info fails.

Guard the command to align with the project’s preference for hard failures in pre-merge checks.

-  echo "Inspecting v1 snapshot"
-  $FOREST_TOOL_PATH archive info v1.forest.car.zst
+  echo "Inspecting v1 snapshot"
+  $FOREST_TOOL_PATH archive info v1.forest.car.zst || return 1

---

37-38: Fail fast on F3 header inspection to surface corrupt/malformed snapshots early.

If header decoding fails, the function should stop and report failure.

-  echo "Inspecting F3 snapshot"
-  $FOREST_TOOL_PATH archive f3-header f3.bin
+  echo "Inspecting F3 snapshot"
+  $FOREST_TOOL_PATH archive f3-header f3.bin || return 1

---

41-44: Also guard v2 post-merge inspections.

Continue the fail-fast pattern for info and metadata checks to catch issues immediately.

-  echo "Inspecting v2 snapshot info"
-  $FOREST_TOOL_PATH archive info v2.forest.car.zst
-  echo "Inspecting v2 snapshot metadata"
-  $FOREST_TOOL_PATH archive metadata v2.forest.car.zst
+  echo "Inspecting v2 snapshot info"
+  $FOREST_TOOL_PATH archive info v2.forest.car.zst || return 1
+  echo "Inspecting v2 snapshot metadata"
+  $FOREST_TOOL_PATH archive metadata v2.forest.car.zst || return 1

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

Learnt from: hanabi1224
PR: ChainSafe/forest#5930
File: build.rs:64-77
Timestamp: 2025-08-13T09:43:20.301Z
Learning: hanabi1224 prefers hard compile-time errors in build scripts rather than runtime safeguards or collision detection, believing it's better to fail fast and fix root causes of issues like malformed snapshot names.

Learnt from: hanabi1224
PR: ChainSafe/forest#5886
File: src/daemon/db_util.rs:236-259
Timestamp: 2025-08-11T14:00:47.060Z
Learning: In Forest's snapshot import (`src/daemon/db_util.rs`), when F3 CID is present in snapshot metadata but the actual F3 data is missing, this should cause a hard error as it indicates snapshot corruption. Only errors during the F3 import process itself (after data is successfully retrieved) should be non-fatal and logged.