chore: replace rollkit in readme

[tac0turtle]

Overview

[github-actions]

The latest Buf updates on your PR. Results from workflow CI and Release / buf-check (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	✅ passed	✅ passed	Jul 25, 2025, 12:18 PM

[gemini-code-assist]

Summary of Changes

Hello @tac0turtle, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a documentation maintenance task, specifically updating the README.md file to align its content with current project and framework naming conventions. The changes ensure that the documentation accurately reflects the correct branding and terminology for the project.

Highlights

• Documentation Update: The README.md file has been updated to reflect a change in terminology or branding, replacing all instances of 'Rollkit' with 'Ev-node' or 'Evolve'.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[claude]

Claude finished @tac0turtle's task —— View job

---

Pull Request Review

Documentation rebranding review completed. Here are my findings and recommendations:

Todo List:

• Read the README.md changes to understand modifications
• Analyze changes for code quality and consistency
• Check for remaining "rollkit" references across codebase
• Evaluate completeness of the rebranding effort
• Provide comprehensive review feedback

Review Findings

✅ What's Working Well

• Clean Documentation Updates: The README.md changes correctly transition from "Rollkit" to "Evolve" terminology
• Consistent User-Facing Language: The changes maintain consistent messaging for end users
• Logical Progression: The two commits show thoughtful progression from "Rollkit" → "Ev-node" → "Evolve"

⚠️ Issues Identified

1. Inconsistent Casing (Minor)

• Line 11: "Using Evolve" vs line 15: "how to use Evolve"
• Consider standardizing the casing approach (I agree with Gemini's suggestion to use "Ev-node" consistently where referring to the technical implementation)

2. Incomplete Rebranding (Major)

Found 99 files still containing "rollkit" references, including:

High Priority Files:

• README.md:103 - Still links to https://rollkit.dev (has TODO comment)
• CONTRIBUTING.md - References "Rollkit" in documentation
• apps/testapp/cmd/root.go - Comments and variable names still use "Rollkit"

Code References:

• Import aliases still use rollkitconfig
• Comments throughout codebase reference "Rollkit"
• Documentation files in /docs/adr/ contain "Rollkit" references

3. Functional Issues (Medium)

• Dead Link: Line 103 still points to rollkit.dev which may not resolve correctly for "Evolve" documentation
• Variable Names: Code still uses rollkitconfig imports which creates confusion

🔒 Security Considerations

• No security concerns with this documentation change
• Links should be verified to ensure they don't redirect to unintended domains

⚡ Performance Considerations

• No performance impact from documentation changes

🧪 Test Coverage

• No test changes needed for documentation updates
• Consider updating any integration tests that might reference old terminology

Recommendations

Immediate Actions:

1. Fix the broken link on line 103 - replace https://rollkit.dev with correct Evolve documentation URL
2. Complete the rebranding across the codebase, especially in:
   • CONTRIBUTING.md
   • Code comments in apps/testapp/cmd/root.go
   • Import aliases (rollkitconfig → evnodeconfig or similar)

Long-term Considerations:

• Consider creating a follow-up issue to systematically update all 99 files containing "rollkit" references
• Update ADR (Architecture Decision Records) documents to reflect the new branding
• Update any remaining protobuf definitions and generated code

Verdict

This PR is a good start but represents an incomplete rebranding effort. While the user-facing README changes are appropriate and well-executed, the extensive remaining "rollkit" references throughout the codebase will create confusion for developers and contributors.

I recommend either:

1. Expanding this PR to address the critical references (especially CONTRIBUTING.md and the broken link), or
2. Creating a follow-up issue to track the complete rebranding effort across the remaining 99 files

The current changes are safe to merge but should be considered part of a larger rebranding initiative.

---

[gemini-code-assist]

Code Review

This pull request begins the process of rebranding from 'Rollkit' to 'Evolve' and 'Ev-node' by updating the main README.md. The changes in the README are a good start.

I've left one comment regarding inconsistent casing for 'Ev-node' to improve clarity and consistency within the document.

Additionally, it appears the rebranding is not yet complete across the repository. I found several other files that still reference 'Rollkit'. To make this change comprehensive, you might want to consider updating these as well. Some examples include:

• CONTRIBUTING.md
• apps/testapp/cmd/root.go (comments and variable aliases)
• node/full.go (comments and variable names)

Completing the renaming across the project in this PR would make the 'chore' more complete and avoid confusion for future contributors.

[gemini-code-assist]

For consistency with the heading on line 11 (## Using Ev-node), it would be best to use the same casing here. Using Ev-node consistently improves readability.

Suggested change

	The easiest way to understand how to use Evolve is by exploring our example implementation, TestApp.
	The easiest way to understand how to use Ev-node is by exploring our example implementation, TestApp.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.27%. Comparing base (d89b796) to head (97f5733).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2495      +/-   ##
==========================================
+ Coverage   73.18%   73.27%   +0.09%     
==========================================
  Files          69       69              
  Lines        6564     6564              
==========================================
+ Hits         4804     4810       +6     
+ Misses       1363     1358       -5     
+ Partials      397      396       -1     

Flag	Coverage Δ
combined	73.27% <ø> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.