chore(deps): bump rain-solmem 0.1.3 -> 0.1.26

[thedavidmeister]

Puts this repo on the latest published solmem, per the org-wide ruling to move everything to latest.

Changes

• foundry.toml: rain-solmem soldeer pin 0.1.3 -> 0.1.26.
• soldeer.lock: regenerated via forge soldeer install; only the rain-solmem entry moved.
• remappings.txt: rain-solmem-0.1.3/ remapping replaced by rain-solmem-0.1.26/. Soldeer appended the new line and left the stale 0.1.3 one; the stale line is pruned by hand in this PR.

Notes

• No file in src/ imports solmem directly, and the transitive graph through rainlang-interface-0.2.3 (LibEvaluable, IExpressionDeployerV2/V3) does not reach solmem either: the whole project compiles clean with only rain-solmem-0.1.26 installed and no 0.1.3 remapping. The pin is carried for the dependency set, not for any current import.
• LibStackPointer was deleted upstream in solmem; nothing here imported it.
• No generated pointers/bytecode artifacts in this repo.

QA

• Discriminating tests: n/a — this repo contains no tests at all (forge test: "No tests found in project"); the gate for a pin bump here is a clean compile of all 37 files against solmem 0.1.26, which passes locally.
• Mutations applied: n/a — the diff is a version pin, a regenerated lockfile, and one remapping line; no semantic line exists to mutate (a wrong path fails to compile).
• Oracle: the Solidity compiler over the full import graph — with the 0.1.3 remapping pruned and only 0.1.26 on disk, any surviving 0.1.3 reference would be a hard compile error.
• Category check: task asks to move the solmem pin to 0.1.26, regenerate soldeer.lock, and prune the stale remapping by hand; all three done, nothing else touched.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the rain-solmem package to version 0.1.26.
  • Applied the update consistently across project configuration.

[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: 5744b4f1-7f3e-4b3d-8898-883a98530965

📥 Commits

Reviewing files that changed from the base of the PR and between 45348d3 and fabd640.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• foundry.toml
• remappings.txt

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

---

Walkthrough

The PR updates the rain-solmem dependency and remapping from version 0.1.3 to 0.1.26.

Changes

Dependency update

Layer / File(s)	Summary
Align dependency references foundry.toml, remappings.txt	Both dependency references now use rain-solmem version 0.1.26.

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

Merge Risk: ⚪ Minimal · up to fabd6

This is a localized dependency pin and remapping update with no reported source-level behavior change or compile impact; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: dcatki

🚥 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 dependency update from rain-solmem 0.1.3 to 0.1.26.
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. (2 skipped: 2 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 2026-08-22-solmem-0-1-26

---

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

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

base="$(gh pr view 73 --repo rainlanguage/raindex.interface --json baseRefOid --jq '.baseRefOid')"
git diff --stat "$base"...HEAD
git diff --numstat "$base"...HEAD
git diff --name-status "$base"...HEAD

Length of output: 596

---

SIZE=S

_{You are interacting with an AI system.}