v0.9 hygiene: reconcile stale trackers and roadmap queue state

[AbdelStark]

Parent

#385

What to build

Bring the public tracker and roadmap surfaces back into sync with live GitHub state before implementation agents start v0.9 work. The current docs still mention some closed historical issues as open next work, and the old v0.7 tracker/issues remain open even though v0.8 superseded major parts of that queue.

This issue should not change model behavior. It should make the queue trustworthy.

Acceptance criteria

• audit open GitHub issues and identify stale v0.6/v0.7/v1.2 tracker state that conflicts with current main and [TRACKER] v0.9 data/eval repair for cross-benchmark correctness claims #385.
• update roadmap docs and next-goal prompts so the current queue points at [TRACKER] v0.9 data/eval repair for cross-benchmark correctness claims #385 and its children, not closed data: build public-safe 100-example downstream reranking set #210/eval: run scaled downstream reranking comparison and claim gate #211/[Tracking] v1.2 next positive-model research hypothesis #212 or superseded v0.7 WS-A: correctness-aware scoring (calibrator + label-aware retrieval prior + outcome head) #337-[TRACKER] v0.7 execution-substrate improvements (RFC-0015) #341 as active next steps.
• add GitHub comments or close/relabel stale tracker issues where appropriate, preserving historical evidence and avoiding destructive edits.
• docs tests cover the updated next-work wording where existing docs tests apply.
• validation includes uv run pytest tests/docs and git diff --check.

Blocked by

None - can start immediately.