Re-pin rainlang 0.2.1 and drop the version alias remappings

[thedavidmeister]

Re-pins rainlang 0.2.0 -> 0.2.1 and drops the alias remappings the seed copied from rainlang. 0.2.1 spells the forge-std 1.16.2 and rain-sol-codegen 0.1.36 it pins (rainlang#577), so this repo's own files now spell the same versions and no import resolves through an alias. Every import names the version foundry.toml pins.

QA

• Discriminating tests: the full suite against the published 0.2.1, 39 passed, 0 failed; script/Build.sol at a fixed point, so no candidate record moved.
• Mutations applied: n/a, import paths and a pin.
• Oracle: foundry.toml [dependencies]; forge remappings shows only soldeer's one-to-one entries.
• Category check: the ruling "you can't remap versions", applied here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QyCCzi9WZPhuXcU1hwr2bq

Summary by CodeRabbit

• Chores

  • Updated Rainlang, forge-std, and code-generation dependencies to newer versions.
  • Removed legacy compatibility remappings for older dependency prefixes.
  • Updated build, deployment, and contract integrations to use the refreshed dependencies.

• Tests

  • Updated test configurations and imports to remain compatible with the refreshed dependency versions.
  • No test logic or assertions were changed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: e3eefb19-b9d9-4912-aa76-a7fdf9b858a2

📥 Commits

Reviewing files that changed from the base of the PR and between 2187d88 and 8654bde.

⛔ Files ignored due to path filters (1)

• soldeer.lock is excluded by !**/*.lock

📒 Files selected for processing (24)

• foundry.toml
• script/Build.sol
• script/BuildAuthoringMeta.sol
• script/CopyArtifacts.sol
• script/lib/LibCopyArtifacts.sol
• src/concrete/Rainlang.sol
• src/concrete/RainlangExpressionDeployer.sol
• src/concrete/RainlangInterpreter.sol
• src/concrete/RainlangParser.sol
• src/concrete/RainlangStore.sol
• src/lib/deploy/LibInterpreterDeploy.sol
• test/abstract/OpTest.sol
• test/abstract/RainlangExpressionDeployerDeploymentTest.sol
• test/src/abstract/RainlangDeploySuites.t.sol
• test/src/concrete/Rainlang.t.sol
• test/src/concrete/RainlangExpressionDeployer.deployCheck.t.sol
• test/src/concrete/RainlangExpressionDeployer.describedByMetaV1.t.sol
• test/src/concrete/RainlangExpressionDeployer.meta.t.sol
• test/src/concrete/RainlangExpressionDeployer.pointers.t.sol
• test/src/concrete/RainlangInterpreter.extrospect.t.sol
• test/src/concrete/RainlangInterpreter.pointers.t.sol
• test/src/concrete/RainlangParser.pointers.t.sol
• test/src/lib/deploy/LibInterpreterDeploy.t.sol
• test/src/script/Build.t.sol

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

---

📝 Walkthrough

Walkthrough

The change updates Rainlang, forge-std, and rain-sol-codegen package references. It removes obsolete Foundry remappings and updates production scripts, contracts, deployment libraries, and tests without changing runtime logic or test behavior.

Changes

Dependency Alignment

Layer / File(s)	Summary
Dependency configuration and build imports foundry.toml, script/...	The default profile removes legacy remappings. Build scripts update Rainlang, rain-sol-codegen, and forge-std import paths.
Production import alignment src/concrete/..., src/lib/deploy/...	Production contracts and deployment libraries use Rainlang 0.2.1 and forge-std 1.16.2 imports.
Test import alignment test/abstract/..., test/src/...	Tests update Rainlang and forge-std import paths. Test logic and assertions remain unchanged.

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

Merge Risk: ⚪ Minimal · up to 8654b

This updates Rainlang and supporting development dependencies while aligning imports and removing obsolete remappings. No current merge-blocking risk remains.

🚥 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 primary changes: updating the rainlang dependency to 0.2.1 and removing version alias remappings.
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

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-09-07-spell-pinned-versions

---

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