docs(plan): clear the last stale facts and disposition the whole tracker

[mmcky]

Rebased on #137, which corrected the consumers table and added release gating as P0. This clears what #137 did not touch — found while triaging all 20 open issues against the code.

Line	Was	Now
70	backlog item 5 (#14) listed as open	struck, with a note that the capture is still fatal under pipefail and belongs to #105
98	dependency policy pinned to anaconda=2025.12	anaconda=2026.06, migrated in #95
112	"#14 Cloudflare alias URL — Still valid"	closed, shipped in #131
113	"#29 — Still valid"	docs half valid, env-harness half overtaken by the live canary
125	rollout Phase 1 put lecture-dp on @v0.8.0	@v0, matching the consumers table above it

The disposition table listed 8 issues while 23 are open, so it had stopped working as a status view. This adds a second table covering everything opened after the July review — #92, #96–#100, #102, #105–#110, #115 and #129.

Item 3's =2025.12 is deliberately untouched: it narrates the misconception that produced #86/#87, not the current baseline.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates PLAN.md to reflect the repo’s current state at v0.11.1 and restores the open-issues disposition section as a complete, up-to-date status view.

Changes:

• Refreshes status lines to v0.11.1 and updates rollout references from @v0.8.0 to floating @v0.
• Marks backlog item 5 (#14) as completed via #131, while noting remaining related work tracked in #105.
• Expands the “Open issues disposition” section with a second table covering issues opened after the July review.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[mmcky]

Rebased onto main to clear the conflict with #137, which landed underneath this branch and touched the same file. Force-pushed with --force-with-lease; still one commit.

Three hunks conflicted, and all three were resolved by keeping both intents rather than picking a side:

Hunk	Resolution
Header	Merged. This PR's framing (August triage, every open issue dispositioned) now leads, followed by #137's additions. Kept #137's correction of "the move of every consumer to @v0" → "the move of lecture-dp and lecture-python.myst" — the original phrasing was the false claim this file was corrected for
Current state / v0.11.1	Same change on both sides. Kept #137's version, which also records that v0 and v0.11.1 both resolve to a388639
Rollout table rows 1–4	Took this PR's cleaner row 1 (✅ preview-netlify@v0 live) — #137's "(was @v0.8.0)" was only meaningful as a correction note at the time and is now git history. Kept #137's rows 2–4 annotations and its lecture-python-programming name fix (the .myst suffix was wrong; Copilot caught it on #137)

Everything unique to this PR survived: item 5 closed against #131, the anaconda 2026.06 baseline, the #14/#29/#2 disposition updates, the whole August triage table, and lecture-dp at @v0. Everything unique to #137 survived too: the corrected consumers table, P0 items 0a–0d, and the precise canary-trigger wording.

One update while resolving — the triage table's gating rows predated #136 and #138, so they now read:

• Release gating: require a green canary before v0 moves (adds a v0-next staging tag) #135 reworded to only ever exercises a published release and cannot test a candidate at all (the earlier "can only test the previous release" is inaccurate once the tag moves);
• The release gate needs its own fixture repo — the canary cannot be trusted as one #136 added — the gate needs its own fixture repo;
• Tracking: release gating — get to a candidate that is verified before v0 moves #138 added — the tracking issue.

The diff against main is now exactly this PR's own contribution. MERGEABLE; the required harness check is still running.