docs: correct the install page — wrong failure mode, wrong cut release, wrong support range

[Jammy2211]

Phase 2 of PyAutoLabs/PyAutoHands#238. The tombstone releases are live on PyPI (PyAutoHands #240, #242); this makes the install page describe what actually happens.

Three false claims, not one

1. The failure mode. The page said pip install autogalaxy on 3.9/3.10/3.11 "will fail with a no matching distribution error". It did not. Verified on real venvs with pip 26.2.1, before the fix:

Python	actual result
3.9	silently installed the 2026.7.29.1 stack, exit 0
3.10	same
3.11	same
3.12	2026.8.17.1 (current)

No JAX, no warning, months out of date. Worse than the documented hard failure, because nothing told the user which version they were running.

2. The cut release. "We dropped support ... in release 2026.4.5.3" is the wrong release. That floor was reverted on 2026-04-30, and 2026.5.1.4 … 2026.7.29.1 all shipped >=3.9 again. The real cut is 2026.7.29.2.

3. The yank. "Pre-2026.4.5.3 releases on PyPI have been yanked, so they will not install" — they were not. 396 of 421 autolens releases are live; the 25 yanked ones are a scattering from the autoconf-rename period. The section's entire premise was a yank that never happened, which is why the resolver fallback it claimed was blocked was in fact wide open.

What it says now

The real cut release, why raising a floor does not retract a back catalogue, and the 2026.7.29.1.post1 tombstone that now refuses the install. It also states the one remaining gap rather than hiding it: --only-binary=:all: skips source distributions, steps past the tombstone, and installs the old wheel silently.

Pinned historical installs are unaffected and still resolve on old Pythons.

API Changes

None. Documentation only.

🤖 Generated with Claude Code

[Jammy2211]

Added a second, related correction to the same install docs: docs/installation/overview.md advertised "Python 3.12 - 3.13", but 3.14 was promoted on 2026-07-31 — it is in the classifiers and PyAutoHands python_matrix.yml runs it as a REQUIRED unit + smoke leg. Reworded to "Python 3.12 or later", which matches requires-python and won't need editing at the next promotion.

Checked and deliberately not changed: PyAutoCTI's "Python 3.12 or 3.13" is accurate (its classifiers stop at 3.13 — it genuinely was not promoted), and the workspace AGENTS.md files saying CI gates on "3.12 and 3.13" are accurate too (PyAutoHeart's reusable smoke-tests workflow defaults to ["3.12", "3.13"] and none override it).