This note is for future maintainers who find references to the old local planning system in git history. After reading it, they should know what was removed from the working tree, what was preserved in docs/, and where current project context now lives.
Use README.md, AGENTS.md, and docs/ for current repository guidance. The old local planning trees were retired because this project is now being driven from the Codex app and ordinary tracked documentation.
The pre-cleanup commit was 5a2d72ad. If you need a removed planning artifact for archaeology, recover it from git history instead of reintroducing the planning tree.
The retired .planning tree contained 405 tracked files and about 8.4 MB of material:
| Area | Count | Disposition |
|---|---|---|
| Milestone phase plans and summaries | 158 | Retired as execution scaffolding. Current docs and code are authoritative. |
| Workstream plans, states, evidence, and screenshots | 115 | Retired except for the Android visual reference material preserved under docs/design/android-visual-refresh/. |
| Combined legacy roadmaps and per-surface plans | 63 | Retired as historical planning context. |
| April consolidation and Supabase planning archive | 48 | Retired as historical planning context. |
| Generated codebase research and maps | 12 | Retired because stable docs and live code now carry that context. |
| Supabase smoke checklist | 1 | Preserved under docs/ops/. |
The retired .gsd entry was an ignored symlink into a local home-directory GSD project store, not app source. It can be reinitialized later if needed.
The Supabase smoke checklist was moved into operations docs because release sign-off still needs a stable checklist.
The Android A4 visual refresh references were moved into design docs because the screenshots and manifests are still useful when comparing Android UI parity against the approved iOS reference set.
The rest of the old planning material stayed in git history rather than being duplicated into docs/. That avoids treating stale plans as active implementation guidance.
Do not recreate .planning or .gsd as required repository inputs unless the team intentionally returns to that workflow. New durable decisions, runbooks, design references, and release checklists should be added directly under docs/.