Rename prelude build command to rainlang-prelude

[thedavidmeister]

Summary

• Rename the old prelude nix task to rainlang-prelude in flake.nix
• Update all CI workflow references
• Update CLAUDE.md and BuildAuthoringMeta.sol comments

Closes #461

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflow definitions and development environment configuration to use updated build system tooling across deployment and testing pipelines.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 99de0a0b-25fa-42fb-b976-5137582cb9da

📥 Commits

Reviewing files that changed from the base of the PR and between c636657 and ac409df.

⛔ Files ignored due to path filters (1)

• CLAUDE.md is excluded by !CLAUDE.md

📒 Files selected for processing (5)

• .github/workflows/git-clean.yaml
• .github/workflows/manual-sol-artifacts.yaml
• .github/workflows/rainix.yaml
• flake.nix
• script/BuildAuthoringMeta.sol

---

📝 Walkthrough

Walkthrough

This pull request renames the prelude build command from i9r-prelude to rainlang-prelude across GitHub workflows, Nix configuration, and inline documentation. The change updates package exports, environment references, and documentation comments consistently throughout the repository.

Changes

Cohort / File(s)	Summary
GitHub Workflows .github/workflows/git-clean.yaml, .github/workflows/manual-sol-artifacts.yaml, .github/workflows/rainix.yaml	Replace nix develop command from i9r-prelude to rainlang-prelude in workflow steps; minor YAML formatting adjustments (blank line removal).
Nix Flake Configuration flake.nix	Rename package output from packages.i9r-prelude to packages.rainlang-prelude; update task name attribute and devShells.default package reference accordingly.
Script Documentation script/BuildAuthoringMeta.sol	Update inline documentation comments to reference rainlang-prelude instead of i9r-prelude.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Rename rain-i9r-cli to rainlang-cli #471: Coordinated branding migration from "i9r" to "rainlang" identifiers across build configuration and flake definitions.

Poem

🐰 From i9r's old name, we hop away,
Rainlang prelude leads the way!
Flakes and workflows now align,
Branding fresh, a new design. ✨

🚥 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 describes the primary change: renaming the prelude build command from i9r-prelude to rainlang-prelude across the codebase.
Linked Issues check	✅ Passed	All coding requirements from issue #461 are met: i9r-prelude is renamed to rainlang-prelude in flake.nix and all CI workflows reference the new command name.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to the rename objective: flake.nix package definition, CI workflows, and related documentation comments are all in scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 rename-prelude-command

---

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

[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=S