docs(planning): codex review fixes for PR #4 phase specs

Three findings from a second codex:review pass on PR #27:

1. ROADMAP.md inline-summary v0.1.5 scope instead of linking to
   ../CHANGE-REQUEST-v0.1.5-launch.md. The CR document is intentionally
   untracked (it's a working planning artifact), so the link was dead from
   a fresh checkout's perspective. Replaced with a one-sentence summary
   of the five workstreams.

2. Phase 10 WNEW-01: define the kind filter and pagination params that
   the success criteria already exercise. Previous WNEW-01 listed only
   the version input, making the spec internally inconsistent with
   success criterion 3 (kind="deprecation") and WNEW-03 (pagination).

3. Phase 11 DETV2-01: parse the standard `version = X.Y[.Z]` key in
   pyvenv.cfg (written by python -m venv). version_info is the optional
   fallback, not the primary key as previously specified. Confirmed
   against the local .venv/pyvenv.cfg in the workspace.

Author: ayhammouda

.planning/ROADMAP.md

@@ -3,7 +3,7 @@
 ## Current
 
 - **v0.1.4** — shipped (pre-PyPI; installed via `uvx --from git+…`)
-- **v0.1.5** — in progress (PyPI debut, repo rename to `python-stdlib-mcp`, positioning lockdown, benchmark harness, launch post). See [`CHANGE-REQUEST-v0.1.5-launch.md`](../CHANGE-REQUEST-v0.1.5-launch.md) for the full scope.
+- **v0.1.5** — in progress. Five coordinated workstreams: positioning lockdown ("canonical Python stdlib oracle for AI coding agents — always free, always MIT, token-frugal"); first PyPI publish via Trusted Publishing; GitHub repo rename to `python-stdlib-mcp` (PyPI package name stays `python-docs-mcp-server`); benchmark harness against competing docs MCPs; coordinated launch post on a personal blog, dev.to, and Show HN.
 
 ## Backlog (post-v0.1.5)
 

.planning/phases/10-whatsnew/10-CONTEXT.md

@@ -14,9 +14,9 @@ Return the official "What's New in Python `<version>`" content as structured sec
 
 ## Requirements
 
-- WNEW-01: Tool accepts a Python version string. Returns `{ "sections": [{title, anchor, body, kind}] }`.
+- WNEW-01: Tool signature: `whatsnew_for_version(version: str, kind: str | None = None, start_index: int = 0, max_sections: int = 20)`. `kind` filters to a single `kind` value (see WNEW-02); `start_index` + `max_sections` paginate the response. Returns `{ "sections": [{title, anchor, body, kind}], "next_start_index": int | None }`.
 - WNEW-02: `kind` enum: `new_module | new_feature | deprecation | removal | performance | syntax | other`.
-- WNEW-03: Token cost capped at ~2k per section; pagination supported via section index.
+- WNEW-03: Each section's `body` is capped at ~2k tokens. If a single section exceeds the cap, truncate with a clear marker and a `get_docs` hint. Pagination via `start_index` / `next_start_index` round-trips.
 
 ## Success criteria
 

.planning/phases/11-detect-venv/11-CONTEXT.md

@@ -15,7 +15,7 @@ Make `detect_python_version` venv-aware: report the Python version of the *activ
 
 ## Requirements
 
-- DETV2-01: Detect active venv via the `VIRTUAL_ENV` env var; if present, read `$VIRTUAL_ENV/pyvenv.cfg` for `version_info`.
+- DETV2-01: Detect active venv via the `VIRTUAL_ENV` env var; if present, read `$VIRTUAL_ENV/pyvenv.cfg` and parse the `version = X.Y[.Z]` key (the standard key written by `python -m venv`). Fall back to `version_info` only if `version` is absent — some tools write that variant.
 - DETV2-02: Detect `.venv/` or `venv/` directories in cwd or its ancestors (up to project root).
 - DETV2-03: Detect `uv`'s `.venv` and `poetry`'s `.venv` patterns.
 - DETV2-04: Preserve v1 fallback chain unchanged below the new venv checks.