docs(phase-00/01): note Python 3.14 lacks PyTorch CUDA wheels (#192)

[Elimartain]

Adds a short note in the GPU setup step pointing out that PyTorch doesn't publish CUDA wheels for the newest Python right away, so on Python 3.14 the install falls back to CPU-only torch. Suggests using Python 3.11–3.13 for GPU until 3.14 wheels are available.

This matches the setup doc, which already recommends Python 3.11+.

Fixes #192.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: baf52025-b555-4725-8fe5-cdcfcf202779

📥 Commits

Reviewing files that changed from the base of the PR and between eaa1d17 and c91a8a0.

📒 Files selected for processing (1)

• phases/00-setup-and-tooling/01-dev-environment/docs/en.md

✅ Files skipped from review due to trivial changes (1)

• phases/00-setup-and-tooling/01-dev-environment/docs/en.md

---

📝 Walkthrough

Walkthrough

Adds a GPU setup note explaining that the cu124 PyTorch index may not provide CUDA wheels for Python 3.14, and recommends using cu128/cu126 for Python 3.14 or Python 3.11–3.13 when using cu124.

Changes

GPU Setup Documentation

Layer / File(s)	Summary
Python 3.14 CUDA wheel availability note phases/00-setup-and-tooling/01-dev-environment/docs/en.md	Inserted a note in the GPU setup step explaining that cu124 may lack Python 3.14 CUDA wheels (leading to CPU-only torch installs), recommending cu128/cu126 for 3.14 or Python 3.11–3.13 when using cu124.

---

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

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a note about Python 3.14 lacking PyTorch CUDA wheels, which matches the documentation update in the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining what note was added to GPU setup instructions and why, plus referencing the linked issue (#192).
Linked Issues check	✅ Passed	The PR successfully addresses issue #192 by adding documentation clarifying PyTorch CUDA wheel availability for Python 3.14 and suggesting alternatives (cu126/cu128 or Python downgrade).
Out of Scope Changes check	✅ Passed	The changes are limited to GPU setup documentation as requested in issue #192, with no unrelated modifications or out-of-scope additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@phases/00-setup-and-tooling/01-dev-environment/docs/en.md`:
- Around line 126-127: Update the note that currently reads "On Python 3.14?
PyTorch doesn't ship CUDA wheels for the newest Python release right away, so
the command above can't find a matching GPU build and you fall back to CPU-only
torch. Use Python 3.11–3.13 for GPU support until the CUDA wheels catch up to
3.14." to reflect that PyTorch currently supports CUDA-enabled wheels for Python
3.10–3.14; change the wording to say Python 3.10–3.14 are supported for CUDA
builds and add a short parenthetical pointing to the official guide
(https://pytorch.org/get-started/locally/) for up-to-date platform/version
compatibility, preserving the original "On Python 3.14?" header to locate the
paragraph.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7587f086-0656-4c42-8cab-36536f263512

📥 Commits

Reviewing files that changed from the base of the PR and between 86bbb61 and eaa1d17.

📒 Files selected for processing (1)

• phases/00-setup-and-tooling/01-dev-environment/docs/en.md

[Elimartain]

Thanks, good catch. I checked the wheel indexes directly:

• cu124 (the index used in the doc) only has cp310–cp313 wheels, no cp314 yet.
• cu126 and cu128 do ship cp314 wheels.

So 3.14 CUDA wheels exist, just not on the cu124 build the doc points at. I updated the note to send 3.14 users to cu128/cu126 instead of suggesting a Python downgrade.