Regenerate the ABI fixtures for the rainlang 0.2.6 candidates

[thedavidmeister]

What

The five ABI and bytecode JSON copies under crates/ regenerated by script/CopyArtifacts.sol for the candidates #6 produced. Ten lines of bytecode, nothing else.

Why

#6 moved four candidates but only re-ran script/Build.sol, not CopyArtifacts, so the committed copies lag the pointers and git-clean is red on main.

QA

• Discriminating tests: n/a, generated copies; git-clean is the check and it printed exactly this diff on Bump rain-sol-codegen 0.1.37 with rainlang 0.2.6, rainlang-interface 0.2.9, rain-deploy 0.1.10 and the transitive pins rainlang 0.2.6 imports #6.
• Mutations applied: n/a, no logic changed.
• Oracle: script/Build.sol, script/CopyArtifacts.sol and forge fmt run on main in a fresh clone; the diff is the five files git-clean named.
• Category check: git-clean red on main; covered.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN

Summary by CodeRabbit

• Chores
  • Updated contract deployment artifacts with regenerated bytecode and current embedded contract addresses.
  • Refreshed integrity-check metadata and opcode information used by the deployment artifacts.
  • Public ABI declarations and function interfaces remain unchanged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: fca530bd-9445-4b73-973b-efde16bff530

📥 Commits

Reviewing files that changed from the base of the PR and between 8420628 and 21fc2e3.

📒 Files selected for processing (5)

• crates/bindings/abi/Rainlang.json
• crates/test_fixtures/abi/Rainlang.json
• crates/test_fixtures/abi/RainlangExpressionDeployer.json
• crates/test_fixtures/abi/RainlangInterpreter.json
• crates/test_fixtures/abi/RainlangParser.json

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

---

📝 Walkthrough

Walkthrough

The pull request regenerates Rainlang deployment artifacts and test fixtures. The ABI declarations remain unchanged. The bytecode updates embedded addresses, selectors, opcode constants, runtime length, and control-flow offsets.

Changes

Bytecode regeneration

Layer / File(s)	Summary
Rainlang artifact bytecode crates/bindings/abi/Rainlang.json, crates/test_fixtures/abi/Rainlang.json	The creation and deployed bytecode now contains updated embedded addresses and control-flow offsets. The fixture runtime length changed from 0x1f6 to 0x1f7.
Expression deployer bytecode crates/test_fixtures/abi/RainlangExpressionDeployer.json	The creation and deployed bytecode now references a new integrity-check address and selector. The opcode constant table changed from 72 to 73 entries.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 21fc2

The change synchronizes generated deployment artifacts without changing ABI declarations, and no concrete production or deployment risk is established.

🚥 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 and concisely describes the main change: regenerating ABI fixtures for the Rainlang 0.2.6 candidates.
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…
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 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-09-14-regenerate-abi-fixtures

---

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.}

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment