Risk & Rollback
Risk Assessment
| Risk | Likelihood | Mitigation |
|---|---|---|
Broken xrefs to old paths |
High |
Grep all |
Content duplication |
Medium |
When splitting a partial into per-concern files, verify no content is duplicated. Each concern appears exactly once. |
Nav bloat |
Low |
Per-concern pages add nav entries, but each is focused. The current single-page-per-tool nav is actually harder to navigate because you can’t jump to a specific concern. |
Conflict with CR-2026-04-10 |
Medium |
The formatting refactor touches the same partials. Complete CR-2026-04-10 first. Don’t run both in parallel. |
Partial naming collision |
Low |
Convention: |
Rollback Plan
Per-Tool Rollback
# Each tool is refactored in its own commit
# To rollback a single tool:
git log --oneline -- "docs/modules/ROOT/pages/codex/grep/" | head -1
git revert <hash>
# Verify build
rm -f /tmp/build.txt && make > /tmp/build.txt 2>&1 && cat /tmp/build.txt
Full Rollback
# Find the commit before the first tool was refactored
git log --oneline --before="2026-04-12" | head -1
# Revert range
git revert --no-commit <first-cr-commit>..HEAD
git commit -m "revert: rollback codex granular page refactor"
Communication
-
No external impact — internal documentation only
-
Don Quijote structure is the reference model (already uses per-concern pages)
-
Codex STD-016 format is preserved — this changes page organization, not content format