docs: note Windows OpenBLAS hang with stdio tool imports

[Amiirhosseini]

Summary

Documents the Windows stdio hang when a tool first-imports OpenBLAS-backed libraries (
umpy / scipy / orch, …): no error, no log line, tool call appears stuck.

• Tip under Running your server → stdio: import those libraries at module scope before mcp.run(); streamable-http is unaffected
• Pointer under Troubleshooting → Still stuck? for the search terms people actually use
• Links #2832 (closed as not-an-SDK-bug; maintainers agreed a docs sentence would help)

Test plan

• Rendered tip reads correctly on the docs site / GitHub preview
• Troubleshooting bullet links to the stdio section anchor

AI disclosure: drafted with Cursor assistance; I reviewed the wording against #2832 and the existing docs voice.

Made with Cursor

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

This PR has been closed automatically. This repo only keeps pull requests open when they come from a maintainer, or from a contributor a maintainer has assigned to the linked issue, and this PR doesn't link an open issue yet.

• If you're already assigned to an issue for this, add Fixes #<n> to the description and the PR will reopen on its own.
• If there's no issue yet, please open one instead: what you ran into, why it matters for your use case, and a minimal reproduction. That context is super important to us and is what we use to decide what to prioritise.
• If there's an issue but you're not assigned, add Fixes #<n> anyway so they're linked, then engage on the issue itself by confirming the repro or describing the approach you'd take. Assignment is a maintainer call based on capacity; comments that only ask to be assigned don't factor in. If you are assigned, this PR reopens automatically.

You're welcome to keep pushing commits here (just avoid force-pushing, since GitHub can't reopen a rewritten branch), but that on its own won't get the PR reviewed or the issue assigned, and realistically most auto-closed PRs stay closed. There's no need to open a new PR either way.

CONTRIBUTING.md has the full reasoning, but in short:

• We're a small team with very little capacity to review community PRs right now.
• Many recent PRs are AI-generated with little human review, and reviewing one carefully still costs a maintainer as much time as it ever did. A well-described issue is usually more useful to us than the code.

Maintainers: reopen, remove missing-issue-link, or add bypass-issue-check to override.