26 lines
912 B
Markdown
26 lines
912 B
Markdown
# Repo Cleanup Workflow
|
|
|
|
## Purpose
|
|
Keep repository documentation and task metadata clean without changing functional behavior.
|
|
|
|
## Inputs
|
|
- Cleanup trigger (stale docs, duplicate guidance, archival need, naming drift).
|
|
- Current governance priorities from `docs/00-governance/active_work.md`.
|
|
|
|
## Steps
|
|
1. Confirm cleanup scope and impacted files.
|
|
2. Ensure no production code changes are included.
|
|
3. Remove stale or duplicate sections that are no longer authoritative.
|
|
4. Consolidate references so canonical docs remain in `docs/00-governance/`.
|
|
5. Log cleanup action and any remaining debt in `docs/00-governance/CLEANUP_LOG.md`.
|
|
6. Verify links/paths and runbook references after edits.
|
|
|
|
## Required Output
|
|
- List of files cleaned and reason for each.
|
|
- Cleanup debt notes for deferred follow-ups.
|
|
|
|
## Exit Criteria
|
|
- Cleanup scope is complete.
|
|
- `CLEANUP_LOG.md` is updated.
|
|
- No code files were modified.
|