Rewrite PLAN.md as the repo's working plan (July 2026)#91
Open
mmcky wants to merge 1 commit into
Open
Conversation
The previous PLAN.md was a migration-plan snapshot frozen in February 2026: Phase 1 (lecture-dp) has since shipped and runs the full chain in production at v0.8.0, and a July 2026 deep technical review of all actions, containers, workflows, docs, and open issues/PRs produced a concrete backlog that had no home. This rewrite makes PLAN.md the single forward-looking plan: - Current state: v0.8.0, the June 2026 hardening pass, and a verified consumer table (lecture-dp full chain, lecture-python.myst previews) - Prioritized backlog P0-P3 from the review, e.g. the container-mode gh-CLI alerting gap (see #83), missing failure-report artifacts, Dependabot conda-group drift (see #28, PRs #86/#87), and the preview-cloudflare alias URL (see #14) - Dependency policy: the Anaconda-baseline "bump as a set" invariant and the hold on PRs #86/#87 - Open-issues disposition table from the triage - Updated rollout status, compressing the completed February gap analysis to its two remaining RunsOn verification items All factual claims were verified against the current tree and live consumer repos. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Reworks PLAN.md from a frozen Feb 2026 migration snapshot into the repo’s current, forward-looking working plan (current state, prioritized backlog, dependency policy, and rollout status), and updates README.md to point to the new purpose of the plan.
Changes:
- Rewrite
PLAN.mdto reflect the post-v0.8.0reality, including a prioritized backlog (P0–P3) and updated rollout status. - Add/clarify dependency policy guidance (notably “science stack bumps as a coordinated set”).
- Update the
README.mddocumentation index line describingPLAN.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| README.md | Updates the documentation index description for PLAN.md to match its new role. |
| PLAN.md | Replaces the old migration-plan snapshot with an updated working plan (state, backlog, dependency policy, rollout). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PLAN.md was a migration-plan snapshot frozen in February 2026. Since then Phase 1 shipped —
lecture-dpruns the full chain in production at@v0.8.0— and a deep technical review (July 2026) of all actions, containers, workflows, docs, and every open issue/PR produced a prioritized backlog that had no home. This PR rewrites PLAN.md as the repo's single forward-looking work plan and updates the README pointer line to match. Net −81 lines.What changed
Current state now reflects reality: v0.8.0, the June 2026 hardening pass (see #79, #36, #35, #78, #84), a verified consumer table (
lecture-dpfull chain at@v0.8.0,lecture-python.mystpreviews at@v0.8.0,test-lecture-python-introat@v0.6.0), and an honest note that container-mode failure alerting is currently broken (see #83).Backlog (P0–P3) from the review, headlined by:
ghCLI, socreate-failure-issue.shexits 127 in the documented default configuration — every cache-build failure goes un-alerted (see #83)pr-Nalias URL for preview-cloudflare (see #14)asset-urloutput, Netlify token viaenv:, standard-mode cache CI coverage, docs trim (see #29, #30, #40)Dependency policy section codifies the "bump the science stack as a set" invariant from #28 and records the hold on PRs #86/#87 — both drift the containers off the Anaconda 2025.12 baseline the lecture repos pin, and #87 additionally pulls in pandas 3.0 (major).
Open issues disposition table summarises the triage of all 7 open issues (#83, #14, #29, #30, #18, #27, #2) against current
main.Rollout status replaces the stale Phase 1/2 tables: Phase 1 is complete, previews-first migration is tracked in QuantEcon/meta#327, and the completed February gap analysis is compressed to its two remaining RunsOn verification blockers (the full feature matrix stays in git history).
Verification
Every factual claim in the new PLAN.md was adversarially checked against the current tree and live consumer repos (via
gh apionlecture-dp,lecture-python.myst, andtest-lecture-python-introworkflows): 12 of 13 checkable claims confirmed exactly; the two figures that failed verification (consumer version cell, docs line count) were corrected before commit.🤖 Generated with Claude Code