🤖 [claude] Review follow-ups for v0.1.1-fh3.1-1: changelog accuracy, stale comment

.github/workflows/sf-release.yml

@@ -118,8 +118,9 @@ jobs:
           # buildx, so branch/PR (release) and tag (maxperf) caches stay separate.
           cache-from: type=gha
           cache-to: type=gha,mode=max
-          # Read access to the private pinax-network/reth fork for cargo's git
-          # fetch inside the build (mounted, never baked into a layer).
+          # Optional read token for git dependencies pinned to the private
+          # pinax-network org (see header and Dockerfile.sf); unused when none
+          # are. Mounted as a BuildKit secret, never baked into a layer.
           secrets: |
             github_token=${{ secrets.PAT_INTERNAL_REPOSITORIES }}
           build-args: |

CHANGELOG.md

@@ -11,11 +11,16 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
 ## v0.1.1-fh3.1-1
 
-First release built from the Pinax fork (`Johnaverse/reth-bsc` for testing, then
-`pinax-network/reth-bsc`). Sources are identical to StreamingFast's `v0.1.1-fh3.1`
-(`56c35604c`): same `Cargo.toml`, same `Cargo.lock`, so `--locked` resolves exactly the bytes
-StreamingFast shipped. Dependencies still come from `streamingfast/reth` (tag
-`bnb-v0.1.1-fh3.1`) and `streamingfast/evm` (`sf/v0.34.0`).
+First release built from `pinax-network/reth-bsc`. `Cargo.toml` and `Cargo.lock` are identical
+to StreamingFast's `v0.1.1-fh3.1` (`56c35604c`), so `--locked` resolves exactly the dependency
+bytes StreamingFast shipped: `streamingfast/reth` tag `bnb-v0.1.1-fh3.1` and `streamingfast/evm`
+`sf/v0.34.0`. One source file differs (see Fixed).
+
+### Fixed
+
+- `read_all_system_contracts` initialises `dir` at its declaration (clippy 1.98
+  `needless_late_init`, which `ci.yml` runs with `-D warnings` on unpinned stable). Same behaviour;
+  the identical failure shows on `streamingfast/reth-bsc` `release/0.1.x`.
 
 ### Changed