chore: latest rainix + soldeer re-lock

[thedavidmeister]

Bumps rainix to latest and re-locks soldeer deps.

• rainix.url -> github:rainlanguage/rainix, nix flake update rainix
• soldeer deps bumped to latest registry versions where behind, then re-locked
• verified via nix develop (latest rainix dev shell)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Updated continuous integration workflow configuration for pull request assessment
  • Refactored development environment setup

• Documentation

  • Improved README formatting and readability

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 53 minutes and 18 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a35b6b63-8c81-4dd3-ba20-ae927f5d21da

📥 Commits

Reviewing files that changed from the base of the PR and between 2af8668 and ebe113c.

📒 Files selected for processing (1)

• flake.nix

Walkthrough

The pull request updates the repository's development and CI infrastructure. The flake.nix configuration is refactored to remove an unused self parameter while preserving build tasks and environment setup. A new CI workflow job is added to assess PR size automatically, and the README text is reformatted without content changes.

Changes

Repository configuration and CI workflow updates

Layer / File(s)	Summary
Flake configuration refactoring flake.nix	The flake outputs signature removes the self argument and restructures to accept { flake-utils, rainix, ... }. Per-system cargo-expand build, packages tasks, and devShells.default are preserved. Dev shell inputs now use inherit from rainix.devShells.${system}.default for buildInputs and nativeBuildInputs.
Workflow PR assessment integration .github/workflows/pr-assessment.yaml	A jobs section is introduced that invokes the reusable PR assessment workflow from rainlanguage/github-chore, forwarding pr_number, repo, owner, and merged status as inputs to assess PR size on closure.
README documentation formatting README.md	The introductory text and "Example:" label are reflowed across multiple lines for readability without changing content, semantics, or code examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related issues

• chore: bump pinned rainix to latest raindex#2575: The flake.nix refactoring to accept rainix as a flake input and remove the unused self argument aligns with updating the pinned rainix flake input.

🚥 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 accurately summarizes the main changes: updating rainix to the latest version and re-locking soldeer dependencies, which are the primary objectives of this pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-06-01-latest-rainix

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 4: Fix the typo in the README intro by changing the word "doumentation"
to "documentation" in the sentence that references `wasm_bindgen` bindings (the
snippet containing "`wasm_bindgen` bindings. For more details please read the
doumentation of the"); update that exact word so the README reads
"documentation".

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ae1f4654-6deb-49f2-8616-85af60c78700

📥 Commits

Reviewing files that changed from the base of the PR and between 7863101 and 2af8668.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• .github/workflows/pr-assessment.yaml
• README.md
• flake.nix

💤 Files with no reviewable changes (1)

• .github/workflows/pr-assessment.yaml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix typo in README intro text.

doumentation should be documentation (Line 4).

Suggested patch

-`wasm_bindgen` bindings. For more details please read the doumentation of the
+`wasm_bindgen` bindings. For more details please read the documentation of the

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	`wasm_bindgen` bindings. For more details please read the doumentation of the
	`wasm_bindgen` bindings. For more details please read the documentation of the

🧰 Tools

🪛 LanguageTool

[grammar] ~4-~4: Ensure spelling is correct
Context: ...dings. For more details please read the doumentation of the items of this lib. Example: ``...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 4, Fix the typo in the README intro by changing the word
"doumentation" to "documentation" in the sentence that references `wasm_bindgen`
bindings (the snippet containing "`wasm_bindgen` bindings. For more details
please read the doumentation of the"); update that exact word so the README
reads "documentation".

[thedavidmeister]

Reviewed ebe113c: chore — latest rainix + soldeer re-lock. LGTM.

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

SIZE=M