docs: fix remaining stale ft-leg claims in change-file body

The Summary and Testing sections still said "two extras" blocked and "just
test" on the ft leg; align them with the shipped per-version smoke-script leg
and full blocked-extras list.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: lesnik512

planning/changes/2026-07-18.01-free-threaded-python-support.md

@@ -15,8 +15,9 @@ locally on 3.14t). Because `orjson` is in `[project] dependencies`, **nothing**
 installs on ft today — not even the pure extras. This change makes `orjson`
 opt-in (its own extra) with a stdlib-`json` fallback in the one place it is used
 (the logging serializer), so core and every pure extra install and pass tests on
-ft. A CI leg proves it; a capability page documents the support matrix and the
-two extras that remain ecosystem-blocked.
+ft. A per-version CI leg proves it; a capability page documents the support
+matrix and the extras that remain ecosystem-blocked (`otl`, `pyroscope`,
+`fastmcp`; `litestar` on 3.13t only).
 
 ## Motivation
 
@@ -124,7 +125,8 @@ calls on one bootstrapper, by design. ft parallelizes *request handling*, where
 - Unit (normal CI): `_dumps_orjson` and `_dumps_stdlib` each called directly; a
   parity test asserts identical output for a representative event dict (incl.
   non-ASCII); `parse()` round-trips under both. 100% coverage without ft.
-- ft CI leg: `import lite_bootstrap` + full `just test` green on 3.13t/3.14t.
+- ft CI leg: `scripts/ft_smoke.py` (import + serializer fallback + FastAPI
+  bootstrap/teardown) green on 3.13t and 3.14t (per-version extras).
 - `just lint-ci` clean (`ty`, planning validator).
 
 ## Risk