ci: use upstream rainix-rs-static reusable

[thedavidmeister]

Summary

• Drops the rainix-rs-static matrix entry from rainix.yaml.
• Adds top-level rainix-rs-static.yaml calling rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@main (introduced in ci: reusable rainix-rs-static workflow rainix#146), which runs through rainix's rust-shell — no chromium/sol/node toolchains pulled in for fmt + clippy.

Test plan

• CI green: new rainix-rs-static workflow passes.
• Existing Rainix CI matrix still runs rainix-rs-test on both OSes and test-wasm-build on ubuntu.

🤖 Generated with Claude Code

Summary by CodeRabbit

Chores

• Implemented automated artifact management system with consistency checks to ensure generated artifacts remain synchronized with committed versions
• Enhanced CI/CD pipeline workflows with improved task organization and separation
• Updated build configuration filesystem permissions and refactored development environment setup

Tests

• Added test coverage for artifact consistency and integrity validation

[coderabbitai]

Warning

Rate limit exceeded

@thedavidmeister has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 35 minutes and 55 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0994525b-6f2c-4ea0-9113-782de0296d4e

📥 Commits

Reviewing files that changed from the base of the PR and between 7d6e641 and 4f43e13.

📒 Files selected for processing (9)

• .github/workflows/copy-artifacts.yaml
• .github/workflows/rainix.yaml
• REUSE.toml
• crates/float/abi/DecimalFloat.json
• crates/float/abi/TestDecimalFloat.json
• foundry.toml
• script/CopyArtifacts.sol
• script/lib/LibCopyArtifacts.sol
• test/script/CopyArtifacts.t.sol

Walkthrough

This PR establishes a system for managing Solidity contract ABI artifacts in source control. It creates a committed TestDecimalFloat.json ABI file, updates Rust bindings to load from that file instead of environment variables, adds a Forge script and test contract to synchronize and verify artifact consistency, implements a new CI workflow to enforce sync on every push, and refactors supporting Nix and Foundry configurations.

Changes

Committed Solidity ABI Artifact Management

Layer / File(s)	Summary
ABI Artifact Definition crates/float/abi/TestDecimalFloat.json	New committed ABI artifact defining packLossless, unpack, and error signatures with compiled metadata.
Rust Bindings Configuration crates/float/src/lib.rs	alloy::sol! macro updated to load DecimalFloat and TestDecimalFloat ABIs from CARGO_MANIFEST_DIR/abi/ instead of environment variables.
Build Configuration foundry.toml	fs_permissions array expanded to grant read access to ./out and read-write access to ./crates/float/abi/.
Artifact Synchronization & Verification script/CopyArtifacts.sol, test/script/CopyArtifacts.t.sol	New Forge script copies compiled artifacts from ./out to committed ./crates/float/abi/ location; test contract verifies committed artifacts match generated outputs via keccak256 hash comparison.
CI Workflows & Enforcement .github/workflows/copy-artifacts.yaml, .github/workflows/rainix-rs-static.yaml, .github/workflows/rainix.yaml	New copy-artifacts workflow builds artifacts, runs sync script, and enforces consistency via git diff --exit-code on every push; separate rainix-rs-static workflow created; rust static analysis removed from rainix matrix.
Development Environment Configuration flake.nix, .prettierignore	Nix flake refactored to use eachDefaultSystem, shell hooks inherited from rainix, and Prettier configured to ignore crates/float/abi/ directory.
Documentation Updates crates/float/src/fuzz_ops.rs	Comment for fuzz test helper updated; no logic changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related issues

• Switch from Nix-derivation ABI to committed JSON artifacts for rust crate #199 — PR directly implements the feature of switching to committed ABI artifacts with synchronization script and CI enforcement.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the primary change: moving Rust static analysis from a matrix entry to an upstream reusable workflow to avoid unnecessary toolchain pulls.
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-05-10-use-rs-static-reusable

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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: 6

🤖 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 @.github/workflows/copy-artifacts.yaml:
- Around line 12-14: Remove the unnecessary Nix configuration entries from the
workflow: delete the keep-env-derivations and keep-outputs keys under the
nix_conf block so the CI run uses default Nix behavior and avoids preserving
build outputs/environments; update the nix_conf section (the block containing
keep-env-derivations and keep-outputs) to only include required options or be
omitted entirely.
- Around line 7-9: The workflow is fetching the full git history by setting
fetch-depth: 0 on the actions/checkout step; change this to a shallow clone by
removing or replacing fetch-depth: 0 (e.g., set fetch-depth: 1 or delete the
fetch-depth key) in the checkout step that uses actions/checkout@v4 so the job
only fetches the current commit and avoids unnecessary overhead.
- Around line 28-29: The CI step named "Assert committed artifacts match freshly
built" currently runs only "git diff --exit-code"; change it so the diff is
printed before the assertion to aid debugging: run a command that first displays
the diff (e.g., "git --no-pager diff" or "git diff --name-only") and then runs
"git diff --exit-code" (or combine into one run block that prints the diff and
then asserts), so the workflow will show what changed when the assertion fails.

In @.github/workflows/rainix-rs-static.yaml:
- Line 5: Replace the mutable branch reference in the workflow invocation "uses:
rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@main" with an
immutable full commit SHA; locate the line containing that exact "uses:
rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@main" string and
update the tail after '@' to the repository commit SHA (e.g.,
@<full-commit-sha>) to pin the reusable workflow to a specific commit for
reproducible CI.

In `@crates/float/abi/TestDecimalFloat.json`:
- Line 1: The JSON artifact file TestDecimalFloat.json is missing a trailing
newline which breaks diffs; open the committed file
(crates/float/abi/TestDecimalFloat.json) and add a single newline character at
the end of the file, save and recommit so the artifact (containing the ABI
entries like packLossless and unpack) ends with a newline.

In `@script/CopyArtifacts.sol`:
- Around line 8-11: Add a short prerequisite note to the run() function stating
that the script expects compiled artifacts in out/ (i.e., that "forge build" has
been executed) so maintainers know to run compilation first; add this as either
a NatSpec comment above run() or an inline comment referencing run() and the
helper _copyArtifact to clarify the dependency on the out/ directory.

🪄 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: 75f7ad0a-8b57-4008-b672-1e6416d8007f

📥 Commits

Reviewing files that changed from the base of the PR and between fe3bcd7 and 7d6e641.

📒 Files selected for processing (12)

• .github/workflows/copy-artifacts.yaml
• .github/workflows/rainix-rs-static.yaml
• .github/workflows/rainix.yaml
• .prettierignore
• crates/float/abi/DecimalFloat.json
• crates/float/abi/TestDecimalFloat.json
• crates/float/src/fuzz_ops.rs
• crates/float/src/lib.rs
• flake.nix
• foundry.toml
• script/CopyArtifacts.sol
• test/script/CopyArtifacts.t.sol

💤 Files with no reviewable changes (1)

• .github/workflows/rainix.yaml

[coderabbitai]

🧹 Nitpick | 🔵 Trivial | 💤 Low value

Consider removing unnecessary Nix configuration.

The keep-env-derivations and keep-outputs settings preserve build outputs and environments, which are typically useful for debugging or inspecting build artifacts. For this CI workflow that only needs to build and verify, these settings may add overhead without benefit.

🤖 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 @.github/workflows/copy-artifacts.yaml around lines 12 - 14, Remove the
unnecessary Nix configuration entries from the workflow: delete the
keep-env-derivations and keep-outputs keys under the nix_conf block so the CI
run uses default Nix behavior and avoids preserving build outputs/environments;
update the nix_conf section (the block containing keep-env-derivations and
keep-outputs) to only include required options or be omitted entirely.

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
rg -nP '^\s*uses:\s*[^#\n]+@(?:main|master|[A-Za-z0-9._/-]+)$' .github/workflows

Repository: rainlanguage/rain.math.float

Length of output: 1019

---

🏁 Script executed:

# Check for any comments or documentation about workflow pinning strategy
find .github -name "*.md" -o -name "*.txt" -o -name "*.yaml" -o -name "*.yml" | head -20

Repository: rainlanguage/rain.math.float

Length of output: 371

---

🏁 Script executed:

# Look for README or documentation files that might explain the workflow strategy
find . -maxdepth 2 -name "README*" -o -name "CONTRIBUTING*" | head -10

Repository: rainlanguage/rain.math.float

Length of output: 84

---

🏁 Script executed:

# Check if there are any comments in workflow files about the pinning strategy
rg -A 2 "uses:.*@main" .github/workflows/ -t yaml

Repository: rainlanguage/rain.math.float

Length of output: 1097

---

🏁 Script executed:

# Check the README for any guidance on workflow versions
cat README.md | head -100

Repository: rainlanguage/rain.math.float

Length of output: 4414

---

🏁 Script executed:

# Check the actual content of the rainix-rs-static.yaml file to confirm context
cat -n .github/workflows/rainix-rs-static.yaml

Repository: rainlanguage/rain.math.float

Length of output: 235

---

Pin the reusable workflow to an immutable commit SHA.

Using @main makes CI behavior mutable and weakens supply-chain guarantees. Pin this reusable workflow to a full commit SHA for reproducibility and tamper resistance.

Suggested change

 jobs:
   rs-static:
-    uses: rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@main
+    uses: rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@<full_commit_sha>

🤖 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 @.github/workflows/rainix-rs-static.yaml at line 5, Replace the mutable
branch reference in the workflow invocation "uses:
rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@main" with an
immutable full commit SHA; locate the line containing that exact "uses:
rainlanguage/rainix/.github/workflows/rainix-rs-static.yaml@main" string and
update the tail after '@' to the repository commit SHA (e.g.,
@<full-commit-sha>) to pin the reusable workflow to a specific commit for
reproducible CI.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify committed artifact matches build output

set -euo pipefail

# Rebuild artifacts
forge build --force

# Run the copy script
forge script script/CopyArtifacts.sol

# Check for uncommitted changes
git diff --exit-code crates/float/abi/TestDecimalFloat.json || {
  echo "ERROR: Committed artifact differs from build output"
  echo "Run: forge script script/CopyArtifacts.sol"
  echo "Then commit the updated artifact"
  exit 1
}

echo "SUCCESS: Artifact is in sync"

Repository: rainlanguage/rain.math.float

Length of output: 118

---

🏁 Script executed:

#!/bin/bash
# Check if the build output file exists
echo "=== Checking for build output file ==="
if [ -f "out/TestDecimalFloat.sol/TestDecimalFloat.json" ]; then
  echo "Build output found at: out/TestDecimalFloat.sol/TestDecimalFloat.json"
  echo "File size: $(wc -c < out/TestDecimalFloat.sol/TestDecimalFloat.json) bytes"
else
  echo "Build output NOT found at: out/TestDecimalFloat.sol/TestDecimalFloat.json"
fi

# Check the committed file
echo ""
echo "=== Checking committed ABI file ==="
COMMITTED_FILE="crates/float/abi/TestDecimalFloat.json"
if [ -f "$COMMITTED_FILE" ]; then
  echo "Committed file found at: $COMMITTED_FILE"
  echo "File size: $(wc -c < $COMMITTED_FILE) bytes"
  
  # Check for trailing newline
  if [ -s "$COMMITTED_FILE" ]; then
    last_char=$(tail -c 1 "$COMMITTED_FILE" | od -An -tx1)
    echo "Last byte (hex): $last_char"
    if [ "$(tail -c 1 "$COMMITTED_FILE" | wc -l)" -eq 1 ]; then
      echo "Has trailing newline: YES"
    else
      echo "Has trailing newline: NO"
    fi
  fi
else
  echo "Committed file NOT found at: $COMMITTED_FILE"
fi

# If both files exist, compare them
echo ""
echo "=== Comparing files (first 500 chars) ==="
if [ -f "out/TestDecimalFloat.sol/TestDecimalFloat.json" ] && [ -f "$COMMITTED_FILE" ]; then
  echo "Build output (first 100 chars):"
  head -c 100 "out/TestDecimalFloat.sol/TestDecimalFloat.json"
  echo ""
  echo ""
  echo "Committed (first 100 chars):"
  head -c 100 "$COMMITTED_FILE"
  echo ""
fi

Repository: rainlanguage/rain.math.float

Length of output: 455

---

🏁 Script executed:

#!/bin/bash
# Check if out/ directory exists
echo "=== Checking out/ directory structure ==="
if [ -d "out" ]; then
  echo "out/ directory exists"
  echo "Contents:"
  find out -type f -name "*.json" 2>/dev/null | head -20
else
  echo "out/ directory does NOT exist"
fi

# List all directories at the root level
echo ""
echo "=== Root level directories ==="
ls -la | grep "^d"

# Check the script that's mentioned in the review
echo ""
echo "=== Checking for CopyArtifacts script ==="
if [ -f "script/CopyArtifacts.sol" ]; then
  echo "Found: script/CopyArtifacts.sol"
  head -30 "script/CopyArtifacts.sol"
else
  echo "NOT found: script/CopyArtifacts.sol"
fi

Repository: rainlanguage/rain.math.float

Length of output: 1964

---

Add trailing newline to committed artifact.

The file crates/float/abi/TestDecimalFloat.json is missing a trailing newline, which will cause diff checks to fail. Add a newline at the end of the file to fix this.

🧰 Tools

🪛 GitHub Actions: copy-artifacts / 0_copy-artifacts.txt

[warning] 1-1: File has 'No newline at end of file' (diff output indicates missing trailing newline).

---

[error] 1-1: CI step failed (exit code 1) after detecting an unexpected change/diff in this ABI JSON file (packLossless/unpack ABI and bytecode/sourceMap content differed).

🤖 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 `@crates/float/abi/TestDecimalFloat.json` at line 1, The JSON artifact file
TestDecimalFloat.json is missing a trailing newline which breaks diffs; open the
committed file (crates/float/abi/TestDecimalFloat.json) and add a single newline
character at the end of the file, save and recommit so the artifact (containing
the ABI entries like packLossless and unpack) ends with a newline.

[coderabbitai]

🧹 Nitpick | 🔵 Trivial | 💤 Low value

Consider documenting the prerequisite.

The script assumes forge build has already been run to populate out/. Adding a comment or NatSpec to run() would make this clearer for future maintainers.

📝 Optional documentation addition

+    /// `@notice` Copy ABI artifacts from out/ to crates/float/abi/.
+    /// `@dev` Requires `forge build` to have been run first.
     function run() external {

📝 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

	function run() external {
	_copyArtifact("DecimalFloat");
	_copyArtifact("TestDecimalFloat");
	}
	/// `@notice` Copy ABI artifacts from out/ to crates/float/abi/.
	/// `@dev` Requires `forge build` to have been run first.
	function run() external {
	_copyArtifact("DecimalFloat");
	_copyArtifact("TestDecimalFloat");
	}

🤖 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 `@script/CopyArtifacts.sol` around lines 8 - 11, Add a short prerequisite note
to the run() function stating that the script expects compiled artifacts in out/
(i.e., that "forge build" has been executed) so maintainers know to run
compilation first; add this as either a NatSpec comment above run() or an inline
comment referencing run() and the helper _copyArtifact to clarify the dependency
on the out/ directory.

[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