docs(solid-query): correct devtools development-mode explanation

[grzdev]

🎯 Changes

The devtools documentation incorrectly describes isServer === true as the condition for including devtools.

Update it to reflect the implementation: isDev enables the devtools in development, the components render nothing in production, and loading happens only on the client.

Documentation only. Verified against the entry point and client-only wrapper; git diff --check passes.

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested code changes locally with pnpm run test:pr, or these tests do not apply to this pull request.
• I fully understand the code in this pull request, including any code generated with AI assistance.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Documentation
  • Updated Solid Query Devtools behavior across environments.
  • Clarified that devtools are enabled only in development, load on the client, and render nothing in production or during server-side rendering.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: c97218a6-0d3e-412f-bf44-602fbe77e643

📥 Commits

Reviewing files that changed from the base of the PR and between 1893a96 and 8c9e043.

📒 Files selected for processing (1)

• docs/framework/solid/devtools.md

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The Solid Query Devtools documentation now states that devtools use isDev, render nothing in production, and load only on the client during development.

Changes

Solid Devtools Documentation

Layer / File(s)	Summary
Environment behavior documentation docs/framework/solid/devtools.md	The documentation now describes development-only enablement, production rendering behavior, and client-only loading during development.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 8c9e0

The Solid Query Devtools documentation now accurately describes its development-only, client-only behavior without changing runtime code or published artifacts. The change is ready to merge.

Suggested reviewers: dborysov

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description explains the documentation change, its motivation, verification, checklist status, and release impact. One checklist item about understanding AI-assisted code remains unchecked, but th…
Title check	✅ Passed	The title is concise, specific, and accurately identifies the correction to the Solid Query devtools development-mode documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

_{Comment @coderabbitai help to get the list of available commands.}