chore(cli): rename comment/description for start cli

[chuck-bear]

A node has multiple modes:

• archive
• fullnode
• validator

This PR will rename the beacond start description/comment to avoid any confusion because full node is onf of the modes mentioned previously.

Summary by CodeRabbit

• New Features
  • Updated command descriptions for improved clarity and brevity in the node startup process.

[coderabbitai]

Walkthrough

The changes involve updates to the command descriptions in the StartCmdWithOptions function within the start.go file. The Short and Long descriptions have been simplified for clarity, without altering the command's functionality or logic.

Changes

File	Change Summary
mod/cli/pkg/commands/server/start.go	Updated command descriptions in StartCmdWithOptions: shortened Short and Long descriptions.

Sequence Diagram(s)

(No sequence diagrams generated as the changes are purely semantic and do not affect control flow.)

Poem

In the meadow, I hop with glee,
A command so clear, it sings to me!
"Run the node," it cheerfully states,
Simplified words, oh, how it resonates!
With CometBFT, we dance and play,
A joyful start to a brand new day! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 21.83%. Comparing base (9735718) to head (8aa4171).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
mod/cli/pkg/commands/server/start.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1996   +/-   ##
=======================================
  Coverage   21.83%   21.83%           
=======================================
  Files         359      359           
  Lines       15976    15976           
  Branches       21       21           
=======================================
  Hits         3488     3488           
  Misses      12367    12367           
  Partials      121      121           

Files with missing lines	Coverage Δ
mod/cli/pkg/commands/server/start.go	0.00% <0.00%> (ø)

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 9735718 and 8aa4171.

Files selected for processing (1)

• mod/cli/pkg/commands/server/start.go (1 hunks)

Additional comments not posted (1)

mod/cli/pkg/commands/server/start.go (1)

92-93: Approve description changes but verify consistency.

The changes to the Short and Long descriptions of the start command make the descriptions more generic and applicable to all node modes, which aligns with the PR objectives. However, it's important to ensure that these changes are consistent with the rest of the documentation and user interface texts.

Run the following script to verify consistency in the documentation:

Verification successful

---

Verification successful: No inconsistencies found.

The changes to the Short and Long descriptions of the start command appear to be consistent with the documentation. The term "node" is used broadly across various contexts, and there is no specific mention of "full node" that would conflict with the updated descriptions.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify consistency of the term "node" in the documentation.

# Test: Search for the term "node" and "full node" in the documentation. Expect: Consistent usage of "node."
rg --type markdown -A 5 $'node'
rg --type markdown -A 5 $'full node'

Length of output: 3298