docs: remove internal planning and draft documents - #63
Merged
Conversation
These files were internal development planning notes, superseded implementation drafts, and status-tracking matrices created during development. They are not user- or contributor-facing documentation and do not belong in the public repository. Removed: - plans/ (implementation plans, engine spec, linting-strategy notes) - docs/codex-vendoring-plan.md, docs/upstream-codex-sync.md (superseded; the vendored tree they described was already removed) - docs/current-tui-therock-correction-plan.md (completed correction pass) - docs/dash-parity-map.md, docs/dash-parity-checklist.md, docs/implementation-completion-audit.md, docs/tui-retirement-checklist.md (internal status trackers) - ROADMAP.md (internal work-tracking, not a public roadmap) Also scrub the first-person "Current Host Finding" section from docs/wsl.md, and drop now-dangling references to the removed files in .gitattributes, AGENTS.md, MANIFEST.md, and a few source-comment pointers. Genuine outstanding work described by these docs is tracked separately in the issue tracker. Signed-off-by: Roman Inflianskas <Roman.Inflianskas@amd.com>
michaelroy-amd
added a commit
that referenced
this pull request
Jun 30, 2026
Resolve conflicts after main advanced (PR #63 cleanup + reroute): - apps/rocm/src/main.rs: keep PR #62's minimal launcher front door for bare `rocm` (dash::run_launcher); drop the dangling docs/tui-retirement-checklist.md reference (deleted on main). - docs/dash-parity-checklist.md, docs/dash-parity-map.md: accept main's deletion (PR #63 removed these tracker docs); the Phase 4 test-name updates to them are moot. Full gate green post-merge: fmt, build, clippy -D warnings, single-thread tests. Signed-off-by: Michael Roy <michael.roy@amd.com>
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
2 participants
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.
What
Removes a set of internal development planning notes, superseded implementation drafts, and status-tracking documents that are not user- or contributor-facing and don't belong in the public repository.
Deleted:
plans/— implementation plans, the PyTorch engine spec, and linting-strategy notesdocs/codex-vendoring-plan.md,docs/upstream-codex-sync.md— superseded; the vendored tree they described was already removeddocs/current-tui-therock-correction-plan.md— a completed correction pass kept only as historydocs/dash-parity-map.md,docs/dash-parity-checklist.md,docs/implementation-completion-audit.md,docs/tui-retirement-checklist.md— internal status/tracking matricesROADMAP.md— internal work-tracking, not a public roadmapScrubbed:
docs/wsl.md— removed the first-person "Current Host Finding" section describing one developer's machine; the rest of the WSL guide is unchanged.Reference cleanup (so nothing dangles): dropped the
/plans/**rule from.gitattributes, theplans/section fromMANIFEST.md, an example-file pointer inAGENTS.md, and a few stale source-comment references inapps/rocm/src/main.rsandcrates/rocm-core/src/{diagnose,examine,fix}.rs.Why
These documents reflect the internal development process rather than the product. They add noise for external readers and risk going stale. Genuine outstanding work they described is tracked separately in the issue tracker.
Notes