docs(project): add the cleanup audit of November 2026 #756
No reviewers
Labels
No labels
loop
queue/failed
queue/queued
ready
status/parked
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
torbscript/language!756
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/742-cleanup-audit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The cleanup audit of 2026-11-13 as a plain document of the project section: 14 findings (1 blocker, 6 major, 7 minor) with file and line evidence, the gap table from every design record, ROADMAP section and CONCEPT open question to its issue, the ordered cleanup plan, and the decisions that are the owner's with a recommendation each.
The plan items are filed as #743 to #755; the tracking epic #742 lists them in order.
Notes for the review
docs/project/2026-11-cleanup-audit.md, notdocs/audits/...as the epic first said: a new top-level folder underdocs/needs its ownindex.mdand a regenerated root index and would appear in the sidebar of the reference. A plain document named indocuments:ofdocs/project/index.mdis the form ROADMAP already uses there.docs/project/index.mdis written by hand in the formtorb docs indexemits (compiler/src/documentation/index.trb:186); CI'sdocs index --checkis the proof. Notorbbinary was run locally.seed/.Refs #742
Approved on
07aff45.pdiscandgates. The hand-written index line is covered by thedocs index --checkgate.docs/project/index.md; no source, no ROADMAP edit, nothing underseed/. The file placement deviation from the epic is explained in the body.Merging by rebase.
Post-merge check (orion): docs/project/2026-11-cleanup-audit.md and its index line are on main (checked via API, main at
61e36267). Merge commitdd6b1b60: pdisc and images edge show "Has been cancelled" (runs 2743, 2742), superseded by later pushes to main, which are pending now; no code failure. No release cut: documentation-only change, no version-bump track in use yet (no x.y.z release tags found), so nothing ships on a tag. Next step, if wanted: the CI results of main HEAD once they finish.