a07cfabce8
Round 5 (Phase 4.x) additions to the cumulative audit:
- Phase 4.0 fork-branch push: 6 forks advanced to origin
(installer, kernel, syscall via --strict=0-behind; libredox,
userutils, relibc via force-push with --force-with-lease).
- Phase 4.3 patch-loss catch: P0-canary + P5-context-mod-sched
archived as operator-superseded (operator's recent cleanup
commits 66a5243f and dc51e67d made them obsolete).
- Phase 4.1 fork-branch deadlock: base fork could not be pushed
due to gitea receive.shallowUpdate=true. Documented in
local/docs/fork-push-status/2026-07-12-Round-5-phase-4.1.md.
Updated cumulative reduction table:
Round 0: 251 patches, 144 orphans (57%)
After Phase 1.0A: 96 orphans (38%)
After Phase 2.1: 27 orphans (15%)
After Phase 3.0-3.2: 0 orphans (0%) ← Round 3 closed
After Phase 4.3: 0 orphans (0%) ← Round 5 still 0
New 'Out-of-scope' entries:
- base fork push deadlock (operator-side gitea config fix)
- Collision detection extension (currently only checks
[[package]].installs, not [[package]].files; doesn't trace
dynamic file generation)
- Pre-receive server-side hook (defense in depth; gitea admin
permission required)
Also add brief mention of Phase 4.2 (collision detection) and
Phase 4.5 (pre-push hook) governance additions.