Normalize user-facing naming to superfile

[yorukot]

There was a previous issue (can't seem to find it now :/) where we discussed whether the project name should be Superfile or superfile. The agreed convention back then was to use superfile (lowercase).

This PR updates user-facing texts to consistently use superfile. Go naming conventions (e.g., exported identifiers) are left unchanged for now, since they don’t affect what users see.

Summary by CodeRabbit

• Style
  • Updated capitalization of "Superfile" to "superfile" across user-facing text, headers, prompts, documentation, and error messages for consistency.

[coderabbitai]

Walkthrough

This update standardizes the capitalization of the term "superfile" across documentation, user interface strings, test assertions, and error messages by changing it from "Superfile" to "superfile." No logic, control flow, or functionality was altered—only string literals and documentation text were updated.

Changes

File(s)	Change Summary
README.md, website/src/content/docs/contribute/file-struct.md	Section headers and directory descriptions updated to use "superfile" (lowercase)
src/internal/ui/prompt/consts.go	Constant string promptHeadlineText changed to "superfile Prompt"
src/internal/ui/prompt/model_test.go	Test assertions updated to expect "superfile Prompt" in rendered output
testsuite/core/base_test.py, testsuite/tests/chooser_file_test.py	Assertion error messages updated to "superfile is not running"/"superfile is still running"

Suggested labels

documentation

Poem

A bunny hopped and changed a name,
From "Superfile" to "superfile"—all the same!
Lowercase letters now dance in delight,
Across docs and prompts, they look just right.
With every test and every line,
The humble "superfile" begins to shine!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 14f551e and 1791074.

📒 Files selected for processing (6)

• README.md (1 hunks)
• src/internal/ui/prompt/consts.go (1 hunks)
• src/internal/ui/prompt/model_test.go (4 hunks)
• testsuite/core/base_test.py (2 hunks)
• testsuite/tests/chooser_file_test.py (1 hunks)
• website/src/content/docs/contribute/file-struct.md (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (3)

testsuite/tests/chooser_file_test.py (1)

testsuite/core/spf_manager.py (1)

• is_spf_running (29-34)

testsuite/core/base_test.py (1)

testsuite/core/spf_manager.py (1)

• is_spf_running (29-34)

src/internal/ui/prompt/model_test.go (1)

src/config/icon/icon.go (1)

• Terminal (42-42)

🪛 LanguageTool

website/src/content/docs/contribute/file-struct.md

[uncategorized] ~73-~73: Possible missing comma found.
Context: ...nctions ### testsuite/ - superfile's testsuite written in Python - Automatically test...

(AI_HYDRA_LEO_MISSING_COMMA)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (go)

🔇 Additional comments (11)

website/src/content/docs/contribute/file-struct.md (1)

73-73: Consistent lowercase naming
The term “superfile” is correctly styled in lowercase here.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~73-~73: Possible missing comma found.
Context: ...nctions ### testsuite/ - superfile's testsuite written in Python - Automatically test...

(AI_HYDRA_LEO_MISSING_COMMA)

README.md (1)

136-136: Consistent lowercase naming in header
The “Start superfile” section header correctly uses lowercase.

testsuite/tests/chooser_file_test.py (1)

34-34: Assertion message updated to lowercase
The error message now consistently uses “superfile” in lowercase.

src/internal/ui/prompt/consts.go (1)

8-8: UI prompt constant adjusted for lowercase
The prompt headline text is updated to “superfile Prompt” to match naming conventions.

testsuite/core/base_test.py (3)

80-80: Assertion message updated to lowercase
Updated to use “superfile” in lowercase for the running status assertion.

---

115-115: Assertion message updated to lowercase
Updated to use “superfile” in lowercase for the closed status assertion.

---

117-117: Assertion message updated to lowercase
Updated to use “superfile” in lowercase for the running status assertion.

src/internal/ui/prompt/model_test.go (4)

242-242: Basic Render (Shell Mode) header uses lowercase "superfile".

Updated the expected header to reflect the new lowercase naming convention, in line with the change to promptHeadlineText.

---

253-253: Basic Render (SPF Mode) header uses lowercase "superfile".

Consistently updated the SPF mode header to lowercase "superfile" to match the standard.

---

295-295: Result Message (Success) header uses lowercase "superfile".

Aligned the success-case prompt header with the lowercase naming.

---

308-308: Result Message (Error) header uses lowercase "superfile".

Updated the error-case prompt header to lowercase "superfile" for consistency.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.