Repository navigation
residue: purge active docs planning and status fossils #630
Description
Activity
🔗 Related PRs
#391 - chore: consolidate roadmaps into single ROADMAP.md [merged]
#475 - Merge-worthy unmerged branches into omnibus reconciliation branch [merged]
#476 - Release/v0.1.0 [merged]
#503 - Revise README.md for clarity and additional information [merged]
#529 - Retire leaf legacy packages [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Starting #630 for v0.1.1. Rationale before state/file changes:
- The repository still carries filesystem planning surfaces (
docs/drafts/,docs/plans/,docs/milestones/) that compete with GitHub Issues/Milestones/Projects as the live planning system. - README still exposes generated Alpha/package progress markers, and
scripts/compute-progress.mjsplus.github/workflows/progress.ymlcan recreate that stale repo-owned progress state. - The correct current flow is already documented: GitHub owns live backlog/progress/release scheduling; repo docs keep stable doctrine, references, and historical evidence only.
I will delete or archive active planning fossils, remove the README progress matrix and its automation path, update CI/docs/tests so the old surfaces cannot return, run preflight, then close this issue as completed only if the guards pass.
- The repository still carries filesystem planning surfaces (
Completion rationale for v0.1.1 residue purge:
- Deleted active filesystem planning surfaces:
docs/drafts/,docs/plans/, anddocs/milestones/. - Moved the remaining MVP technical architecture evidence under
docs/archive/MVP/so it is historical, not an active milestone lane. - Removed README generated progress/status markers and the package matrix.
- Retired the repo-owned progress automation path:
.github/workflows/progress.yml,scripts/compute-progress.mjs, progress metadata/badge files, and the old progress Bats tests. - Updated CI, repo Bats smoke, script docs, host docs, and CI docs to use explicit docs-planning boundary checks instead of progress checks.
- Added
test/docs-planning-boundary.batsto prevent filesystem planning directories, README progress markers, and progress automation from returning.
Commit: aeab9f5
chore(residue): retire repo planning surfacesValidation:
pnpm run preflightpnpm run testpnpm run legacy-preflightpnpm run lintcargo xtask docs-checkBATS_LIB_PATH=test TERM=xterm BATS_NO_COLOR=1 bats -t test/docs-planning-boundary.batsBATS_LIB_PATH=test TERM=xterm BATS_NO_COLOR=1 bats -t test/domain-empty-boundary.batsBATS_LIB_PATH=test TERM=xterm BATS_NO_COLOR=1 bats -t test/ci-workflows.batsbash scripts/smoke/repo-bats-prepush.shgit diff --check
Closing as completed because active repo docs no longer carry live backlog/progress/milestone state; GitHub Issues, Milestones, Projects, and labels remain the scheduling authority.
- Deleted active filesystem planning surfaces:
Why
Wesley should not keep active repo docs that track backlog, progress, or old release status. GitHub Issues, Milestones, Projects, and labels are the source of truth for planning. Repo docs should describe current architecture, doctrine, and durable references only.
Scope
Audit and remove, graveyard, or rewrite planning/status fossils that still read like current project truth, especially:
docs/milestones/MVP/docs/milestones/README.mddocs/drafts/Keep historical evidence only when it is clearly marked as historical and does not compete with GitHub Issues/Milestones as the active planning system.
Acceptance
pnpm run preflightpasses.