Fix docs for WireframeServer::new

[leynos]

Summary

• remove outdated panic section from server constructor docs

Testing

• cargo clippy -- -D warnings
• RUSTFLAGS="-D warnings" cargo test
• markdownlint '**/*.md' (fails: many pre-existing errors)
• nixie docs/*.md

---

https://chatgpt.com/codex/tasks/task_e_684e51103e6483228f03f2098a0e9d5c

Summary by Sourcery

Documentation:

• Remove the ‘# Panics’ section from the server constructor docs as the CPU-count fallback no longer panics

Summary by CodeRabbit

• Documentation
  • Removed documentation about a specific panic condition in the server constructor. No changes to functionality or behaviour.

[sourcery-ai]

Reviewer's Guide

This PR cleans up the WireframeServer::new documentation by removing an outdated # Panics section that no longer applies to the constructor’s behavior.

File-Level Changes

Change	Details	Files
Remove obsolete panic documentation from server constructor comments	Deleted # Panics header from doc comment Removed description of potential panic when CPU count cannot be determined Trimmed extra blank lines to maintain formatting	src/server.rs

Possibly linked issues

• #0: The PR removes the misleading # Panics section from the WireframeServer::new documentation as requested in the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

The documentation for the WireframeServer::new constructor in src/server.rs has been updated by removing a section that described a possible panic condition related to CPU count detection. No functional or code logic changes were made; only documentation comments were altered.

Changes

File(s)	Change Summary
src/server.rs	Removed documentation about a panic condition in WireframeServer::new

Sequence Diagram(s)

Possibly related issues

• Docs: Remove misleading # Panics section from WireframeServer::new #20: This issue discusses removing outdated panic documentation from WireframeServer::new, which matches the change in this PR.
• Docs: Consolidate duplicated text in WireframeServer::new docs #22: This issue addresses deduplication and consolidation of documentation for WireframeServer::new, which relates to the documentation cleanup performed here.

Possibly related PRs

• Fix worker count default #16: This PR refines documentation and API methods related to worker count fallback in WireframeServer::new, directly connecting to the documentation change here.
• Fix compile errors and clippy #11: This PR also modifies and clarifies the documentation for WireframeServer::new, overlapping in focus on the constructor's documentation.
• Add WireframeServer skeleton #6: This PR introduces the initial implementation and public API for WireframeServer, including its constructor, which is the subject of this documentation update.

Poem

In the warren of code, a comment did dwell,
About a panic that no longer befell.
With a hop and a sweep, the docs are now neat,
No more warnings of CPUs in retreat.
🐇✨
The server stands tall, with clarity sweet!

---

📜 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 11644cb and 15ea4d5.

📒 Files selected for processing (1)

• src/server.rs (0 hunks)

💤 Files with no reviewable changes (1)

• src/server.rs

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

• GitHub Check: build-test

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

[codescene-delta-analysis]

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Absence of Expected Change Pattern

• wireframe/src/server.rs is usually changed with: wireframe/src/extractor.rs, wireframe/src/middleware.rs

Quality Gate Profile: Pay Down Tech Debt
Want more control? Customize Code Health rules or catch issues early with our IDE extension and CLI tool.

[sourcery-ai]

Hey @leynos - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}