fix(config): correct signer flag

[julienrbrt]

Closes: #2603

Flags need to match the file structure for binding to work.

[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	Sep 9, 2025, 4:28 PM

[gemini-code-assist]

Summary of Changes

Hello @julienrbrt, 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 addresses naming inconsistencies within the project's configuration system. It standardizes the primary configuration file name and refines internal flag definitions, leading to a more consistent and user-friendly experience when interacting with the application's settings.

Highlights

• Configuration File Renaming: The primary configuration file name has been updated from "evolve.yaml" to "evnode.yml" across various application initialization commands, error messages, and documentation files to ensure consistency.
• Signer Flag Correction: The internal constant names for signer configuration flags, FlagSignerType and FlagSignerPath, have been corrected to signer.signer_type and signer.signer_path respectively, improving clarity and adherence to naming conventions.
• Documentation Updates: All relevant documentation files have been updated to reflect the new configuration file name and include minor formatting adjustments for improved readability.

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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

[gemini-code-assist]

Code Review

This pull request primarily focuses on renaming the configuration file from evolve.yaml to evnode.yml across the codebase and documentation. It also corrects the command-line flags for the signer configuration to be consistent with the struct field names. My review has identified a couple of areas in the documentation that were missed during these updates and require correction for consistency and accuracy. Overall, the changes are good but need these documentation fixes to be complete.

[github-actions]

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-09-10 07:36 UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.15%. Comparing base (0584153) to head (592ac07).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2637      +/-   ##
==========================================
- Coverage   69.17%   69.15%   -0.03%     
==========================================
  Files          74       74              
  Lines        7803     7803              
==========================================
- Hits         5398     5396       -2     
- Misses       1955     1957       +2     
  Partials      450      450              

Flag	Coverage Δ
combined	69.15% <ø> (-0.03%)	⬇️

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.

[tac0turtle]

can you update docs as well

[julienrbrt]

E2E tests are currently failing because of celestiaorg/tastora#112