Bump rain-solmem 0.1.3 -> 0.1.26

[thedavidmeister]

Clears the roh dash's stale-dep flag on this repo (rain-solmem pinned 0.1.3, latest 0.1.26).

• foundry.toml: rain-solmem 0.1.3 -> 0.1.26
• remappings.txt and the three version-pinned import sites (LibPointer, LibMemCpy, LibBytes) updated to match
• soldeer.lock regenerated via forge soldeer update

Same shape as rain.extrospection PR #134 this morning. The consumed solmem APIs are unchanged between the versions (0.1.4–0.1.26 changes are NatSpec plus a new truncation error). Local run: 23 passed, 0 failed.

QA

• Discriminating tests: n/a - dependency version bump with no first-party logic change; the discriminator is the existing 23-test suite passing against the new dependency (verified locally, full suite, 1024-run fuzz)
• Mutations applied: n/a - no first-party source logic changed; the only source edits are version-pinned import path strings and the remapping, whose mutation is a compile error by construction
• Oracle: the existing test suite, whose expected values predate this change and are independent of the bumped dependency; solmem 0.1.3->0.1.26 diff reviewed for API stability of the consumed libs
• Category check: dash stale-dep flag asks for the solmem pin to reach latest; covered: dependency pin, remappings, import paths, lockfile - the full surface a soldeer bump touches in this org's version-pinned-import convention

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@thedavidmeister, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: fc18ccbe-052a-4d71-8e05-887c61572f17

📥 Commits

Reviewing files that changed from the base of the PR and between 01e329a and 3b44a31.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• foundry.toml
• remappings.txt
• src/lib/LibDataContract.sol
• test/lib/LibDataContract.t.sol

---

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