Bump rain-lib-memkv 0.1.0 -> 0.1.5

[thedavidmeister]

What

Moves the rain-lib-memkv pin from 0.1.0 to 0.1.5, the newest published
revision, and follows the versioned import path in the seventeen files that use
it.

Why

The org health dashboard draws this repo standing on a stale dependency: pinned
0.1.0 against 0.1.5 published. A stale pin means the closure this repo actually
resolves is not the one the graph draws.

QA

• Discriminating tests: none added, and none are owed. Across the five
  revisions, src/lib/LibMemoryKV.sol changed by +19/-0 and nothing else in
  src/ changed at all: the whole diff is a new has function. No line this
  repo calls was touched. The existing suite is the discriminator for the
  substitution being inert, and it is green at 1552 passed, 0 failed.
• Mutations applied: n/a. A mutation pass tests this repo's own behaviour, and
  this change adds none: no line of logic moves and no assertion changes. The
  behaviour reached through the bumped package is pinned by that package's own
  suite, which grew from 28 to 34 tests across these revisions.
• Oracle: the published package contents at each tag, compared directly, and the
  soldeer registry for what the newest revision is.
• Category check: the ask is a stale pin. Covered: the pin moves to the newest
  published revision, all seventeen import paths follow it so no stale copy can
  resolve, soldeer.lock records the new url, checksum and integrity, and the
  suite runs green against the installed 0.1.5 tree.

Note on the local run: this repo's nix shell will not build here, because its
rain flake input vendors Rust dependencies that crates.io now answers 403 for
(const-hex 1.11.3). The suite above was run with foundry from a sibling shell.
CI has the working cache and is the authority on this branch.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V8ViHcKLVk2YoS2joH4HdN

Summary by CodeRabbit

• Chores
  • Updated the memory key-value library from version 0.1.0 to 0.1.5.
  • Aligned application and test integrations with the newer library version.
• Tests
  • Updated test dependencies to use version 0.1.5 while preserving existing test coverage and behavior.

[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: 73d311e8-128b-42dc-8044-112d4771f3d0

📥 Commits

Reviewing files that changed from the base of the PR and between 8d2fc22 and 0a50279.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (19)

• foundry.toml
• remappings.txt
• src/abstract/BaseRainlangInterpreter.sol
• src/lib/eval/LibEval.sol
• src/lib/op/store/LibOpGet.sol
• src/lib/op/store/LibOpSet.sol
• src/lib/state/LibInterpreterState.sol
• src/lib/state/LibInterpreterStateDataContract.sol
• test/abstract/OpTest.sol
• test/src/concrete/RainlangStore.t.sol
• test/src/lib/eval/LibEval.fBounds.t.sol
• test/src/lib/eval/LibEval.inputsLengthMismatch.t.sol
• test/src/lib/eval/LibEval.maxOutputs.t.sol
• test/src/lib/eval/LibEval.remainderOnly.t.sol
• test/src/lib/op/logic/LibOpAny.t.sol
• test/src/lib/op/store/LibOpGet.t.sol
• test/src/lib/op/store/LibOpSet.t.sol
• test/src/lib/state/LibInterpreterState.fingerprint.t.sol
• test/src/lib/state/LibInterpreterStateDataContract.t.sol

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

---

📝 Walkthrough

Walkthrough

Changes

The PR upgrades rain-lib-memkv from 0.1.0 to 0.1.5 in project configuration, production imports, and test imports. Imported symbols and test logic remain unchanged.

rain-lib-memkv upgrade

Layer / File(s)	Summary
Dependency configuration foundry.toml, remappings.txt	The dependency version and remapping path change to 0.1.5.
Source and test import alignment src/..., test/...	All affected imports reference rain-lib-memkv-0.1.5. Imported symbols and test logic remain unchanged.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 0a502

This is an import-only dependency upgrade with no supported unresolved behavior or integration risk.

🚥 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 identifies the main change: updating rain-lib-memkv from version 0.1.0 to 0.1.5.
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 bump-memkv

---

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