Cut release 0.1.0: freeze src/generated/0_1_0/ in lockstep with the version

[thedavidmeister]

Cuts release 0.1.0 on the two-field contract rainix-static release-guard holds a sol-v* tag to: the tagged commit must carry [external.package].version == the tag version AND the frozen src/generated/<tag>/ snapshot it names. The version field was already 0.1.0 (this repo was created naming the version its first tag would cut), so the only field that moves here is the snapshot, cut in one cutRelease() + forge fmt run with the released-suites lib regenerated alongside.

MetaBoard was deployed before this PR — run 32523737176 (Manual sol artifacts, workflow_dispatch on main) — so the attestation this freeze arms has its subject already on chain. No further broadcast is a prerequisite here.

What changed

• src/generated/0_1_0/MetaBoard.sol — the frozen snapshot, byte-identical to the rolling src/generated/candidate/MetaBoard.sol (both sha256 a9ec5fc57f8f548e9427f3b8ab23763cc923c5bfdefb93f679455ccaa7c168db): same CREATION_CODE, same BYTECODE_HASH 0xb7b74d879e97f272145d32ce18bd060f1e9f387696911376191ca10ecf24bed6, same DEPLOYED_ADDRESS 0x8fD50fF9Db9835ba1B61394752A26F53D721D2a1, same empty DEPENDENCIES.
• src/lib/LibMetaBoardReleased.sol — regenerated in the same cutRelease() run, so releasedSuites() goes from length 0 to the one metaboard@0_1_0 entry aliased from that frozen file. This is the commit that gives RainDeployVerifyChain its first subject; it is regenerated here rather than in a follow-up because testEveryFrozenSnapshotIsReleased fails on either half landing without the other.
• foundry.toml — drops the paragraph saying nothing is frozen yet. This commit is the one that freezes it.

Release-path gates, run locally against this commit

Not restated from the workflow — each was executed against beb1eea:

• Determinism check — forge script ./script/Build.sol && forge fmt (the non-freezing run(), which is what the release re-runs) leaves git status --porcelain empty on this commit. Also verified empty on the base commit beforehand, so the freeze is the only thing this diff moves.
• Publish guard — rainix-static release-guard --version 0.1.0, at the release's pinned RAINIX_SHA c4cf22d, reports: clean — foundry.toml version, src/generated/0_1_0/ present and newest, tree regenerates unchanged, frozen release matches src/generated/candidate/.
• Verify gate — the full suite passes, 14/14, including MetaBoardDeployChainTest::testSuitesLiveOnEverySupportedNetwork against public archive endpoints for all seven supported networks.

Per-network eth_getCode at latest for 0x8fD50fF9Db9835ba1B61394752A26F53D721D2a1, read directly rather than through anything this repo asserts, then keccak256'd and compared to the frozen BYTECODE_HASH:

network	chainid	keccak256(runtime code)
arbitrum	42161	0xb7b74d87…bed6 OK
base	8453	0xb7b74d87…bed6 OK
base_sepolia	84532	0xb7b74d87…bed6 OK
ethereum	1	0xb7b74d87…bed6 OK
flare	14	0xb7b74d87…bed6 OK
hyperevm	999	0xb7b74d87…bed6 OK
polygon	137	0xb7b74d87…bed6 OK

All seven match, so nothing blocks the tag on the chain side.

QA

• Discriminating tests: MetaBoardDeployChainTest::testSuitesLiveOnEverySupportedNetwork — passed VACUOUSLY on base main, where releasedSuites() was empty so checkDeployedOnSupportedNetworks took its derived.length == 0 early return without touching a single RPC; this diff is what gives it a subject, and it now forks all seven networks and passes against the live chain (verified by running the suite on this branch with all seven *_RPC_URL bound to public archive endpoints). MetaBoardDeploySnapshotTest::testEveryFrozenSnapshotIsReleased fails on base if a freeze lands without its releasedSuites() entry or the reverse — verified by construction, which is why the generated lib is regenerated in this same commit rather than after. testSnapshotMatchesSource fails on any drift between the frozen/candidate bytes and what source compiles to.
• Mutations applied: n/a — a generated freeze plus a comment deletion, so there is no hand-written logic in this diff to mutate, and the two generated files are byte-for-byte what script/Build.sol emits (a hand mutation of either is exactly what the gates below catch). The standing gates discriminate instead: a hand edit inside src/generated/0_1_0/ fails the frozen-snapshots-append-only gate at PR time, a hand edit to LibMetaBoardReleased.sol fails the release's own determinism re-run (git status non-empty), and drift between the freeze and source fails MetaBoardDeploySnapshotTest.
• Oracle: the live chains, read directly and independently of this repo — eth_getCode at latest for 0x8fD50fF9… on all seven supported networks from public endpoints, keccak256'd and compared to the frozen BYTECODE_HASH (table above). The frozen bytes have a second independent oracle: sha256 equality with src/generated/candidate/, which script/Build.sol derives from compiled source, not from this diff.
• Category check: the ruled work is "cut release 0.1.0"; covered — version field (already 0.1.0, re-verified by the guard), frozen src/generated/0_1_0/ snapshot, regenerated released-suites lib, and the tag sol-v0.1.0 to follow on the merge commit. NOT covered and deliberately out of scope: the subgraph deployment record (Take the subgraph's deployment record and wire it to the deploy records #4, which stays open by ruling — the subgraph is not being stood up yet), and the on-chain broadcast, which already happened in run 32523737176 and is not part of the release workflow by design.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added published deployment metadata for MetaBoard version 0.1.0, including its release address, verified code information, and dependency details.
  • Release tooling can now retrieve a complete deployment record instead of an empty result.

• Chores

  • Removed outdated comments from the Foundry configuration without changing package metadata or configuration behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2e253823-8e47-40c3-8542-932d76cd8f0b

📥 Commits

Reviewing files that changed from the base of the PR and between f8a4efa and beb1eea.

⛔ Files ignored due to path filters (1)

• src/generated/0_1_0/MetaBoard.sol is excluded by !**/generated/**

📒 Files selected for processing (2)

• foundry.toml
• src/lib/LibMetaBoardReleased.sol

💤 Files with no reviewable changes (1)

• foundry.toml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

LibMetaBoardReleased now returns the frozen MetaBoard@0_1_0 deployment metadata in one DeploySuite. Obsolete release-status comments were removed from foundry.toml.

Changes

MetaBoard release metadata

Layer / File(s)	Summary
Populate released deployment suite src/lib/LibMetaBoardReleased.sol, foundry.toml	The library imports frozen deployment artifacts and returns one populated DeploySuite. Obsolete configuration comments were removed without changing configuration values.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to beb1e

This PR freezes the 0.1.0 generated snapshot and updates the released-suite index without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review.

Suggested reviewers: claude

🚥 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 clearly summarizes the release cut and freezing of the 0.1.0 generated snapshot, which are the primary changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cut-release-0.1.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[thedavidmeister]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.