vasilito/RedBear-OS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: repair stale references to legacy-obsolete-2026-07-25/*

Browse Source 
Several docs still referenced files in local/docs/legacy-obsolete-
2026-07-25/ after that directory's 2026-07-27 cleanup deleted most of
its contents. The directory now only contains SUPERSEDED.md; all
other legacy-obsolete entries were fully removed. The doc cleanup
phase of the round-2 D-Bus audit identified each broken reference and
fixed it by pointing at the current canonical location.

Repairs:
- ACPI-IMPROVEMENT-PLAN.md, BUILD-SYSTEM-INVARIANTS.md,
  INIT-NAMESPACE-MANAGER-SCALABILITY-PLAN.md,
  NETWORKING-IMPROVEMENT-PLAN.md, USB-IMPLEMENTATION-PLAN.md:
  legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md
  -> IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md
  (restored to top-level local/docs/).
- CONSOLE-TO-KDE-DESKTOP-PLAN.md:
  legacy-obsolete/BUILD-SYSTEM-HARDENING-PLAN.md
  -> COLLISION-DETECTION-STATUS.md
- TOOLS.md, RELEASE-BUMP-WORKFLOW.md:
  legacy-obsolete/HOOKS.md
  -> RELEASE-BUMP-WORKFLOW.md § 'Git Hooks' (content merged).
- patches/README.md, RATATUI-APP-PATTERNS.md:
  removed dangling refs to legacy-obsolete/PATCH-PRESERVATION-AUDIT
  and redbear-power-improvement-plan (both deleted with no successor
  doc; the related guidance lives in the canonical plans).

Each replacement preserves the link's intent: every old reference was
pointing to a doc whose content has either been restored to top-level,
absorbed into a different canonical doc, or replaced by a plan
reference that covers the same surface.
This commit is contained in:
vasilito
2026-07-27 22:37:07 +09:00
parent 7ca41f4d60
commit 5970dd226f
10 changed files with 14 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
local/docs/ACPI-IMPROVEMENT-PLAN.md
+1 -1
View File
@@ -70,7 +70,7 @@ kernel-ownership decisions are shared.
Read these alongside this plan:
- `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md`
- `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md`
- `local/docs/QUIRKS-SYSTEM.md`
- `docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md`
local/docs/BUILD-SYSTEM-INVARIANTS.md
+1 -1
View File
@@ -457,4 +457,4 @@ miss. The `/etc/init.d/` path convention is self-enforcing via `config_for_dirs(
- `scripts/lint-config-paths.sh` — detects `/usr/lib/init.d/` paths in config files
- `make lint-config` — runs the lint as a build step
- Full plan: `local/docs/legacy-obsolete-2026-07-25/BUILD-SYSTEM-HARDENING-PLAN.md`
- Full plan: `local/docs/COLLISION-DETECTION-STATUS.md`
local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md
+3 -4
View File
@@ -99,7 +99,7 @@ consolidation are **DONE** and reflected in this plan's status tables
|--------|--------|
| **SDDM v0.21.0 marked COMPLETED (build-side)** | Was "In-tree, unwired". Now `sddm` + `pam-redbear` are in `config/redbear-full.toml` `[packages]`, init service `21_sddm.service` is wired via `/etc/init.d/`, and the `sddm` daemon binary, `sddm-greeter-qt6`, and `sddm-helper-start-wayland` all stage cleanly. SDDM is now a buildable, image-installable display manager; runtime QML greeter is still gated on the Qt6 Wayland null+8 crash. |
| **Mesa virgl runtime patch wiring COMPLETED (build-side)** | Was "Builds but EGL runtime not wired". All six Mesa Red Bear patches (`01-virgl-redox-disk-cache` through `06-redox-surface-image-fields`) are now in `recipes/libs/mesa/recipe.toml` `patches=[...]`. The `06-redox-surface-image-fields.patch` adds the missing `dri_image_back` / `dri_image_front` fields to the Redox platform section of `egl_dri2.h` so the EGL platform probe can attach GBM-backed images. `virtio_gpu_dri.so` is staged. Runtime EGL probe selection is the remaining gap. |
| **uutils nix-0.30.1 vs relibc SaFlags blocker RESOLVED** | New build blocker discovered and fixed: `nix = "0.30.1"` pinned by uutils' `Cargo.lock` was incompatible with relibc's `sa_flags: c_int` (i32) at `nix-0.30.1/src/sys/signal.rs:809,819`. Fixed by bumping workspace `libc` from `0.2.182` to `0.2.186` in `recipes/core/uutils/redox.patch`. `repo cook uutils` now succeeds. See `local/docs/legacy-obsolete-2026-07-25/BUILD-SYSTEM-HARDENING-PLAN.md` Phase 7. |
| **uutils nix-0.30.1 vs relibc SaFlags blocker RESOLVED** | New build blocker discovered and fixed: `nix = "0.30.1"` pinned by uutils' `Cargo.lock` was incompatible with relibc's `sa_flags: c_int` (i32) at `nix-0.30.1/src/sys/signal.rs:809,819`. Fixed by bumping workspace `libc` from `0.2.182` to `0.2.186` in `recipes/core/uutils/redox.patch`. `repo cook uutils` now succeeds. See `local/docs/COLLISION-DETECTION-STATUS.md` Phase 7. |
### What Changed in v5.0 (2026-06-20)
@@ -663,7 +663,7 @@ the wider column. Other rows show ` 1 ...` (no symbol).
#### v1.0 Comprehensive Quality Release (2026-06-20)
Full multi-phase implementation per `local/docs/legacy-obsolete-2026-07-25/redbear-power-improvement-plan.md`
Full multi-phase implementation per the redbear-power improvement roadmap (historical; all phases A → D implemented)
(Phases A → D, all deferred items implemented). **+1248 lines** added
(1396 → 2644 LoC) across **9 modules**.
@@ -719,8 +719,7 @@ local/recipes/system/redbear-power/source/src/
```
**Cross-references**:
- `local/docs/legacy-obsolete-2026-07-25/redbear-power-improvement-plan.md` — original Phase A-D plan
- `local/docs/RATATUI-APP-PATTERNS.md` §13 — ratatui 0.30 best practices
- `local/docs/RATATUI-APP-PATTERNS.md` §13 — ratatui 0.30 best practices (historical redbear-power improvement roadmap now consolidated here)
**Build**: `cook redbear-power - successful`, 0 warnings, 0 errors.
Total source: 1396 lines across 6 modules.
local/docs/INIT-NAMESPACE-MANAGER-SCALABILITY-PLAN.md
+1 -1
View File
@@ -225,5 +225,5 @@ evaluation (bounded to seconds, not infinite), which is the tail this rewrite wo
## Related
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` — canonical desktop path; console/login is its floor.
- `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — acpid/ACPI robustness context.
- `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — acpid/ACPI robustness context.
- Memory: `mini-login-acpid-mutex-rootcause`, `fbcond-handoff-console-wedge`.
local/docs/NETWORKING-IMPROVEMENT-PLAN.md
+1 -1
View File
@@ -37,7 +37,7 @@ Companion plans that share authority over networking-adjacent surfaces:
- `local/docs/WIFI-IMPLEMENTATION-PLAN.md` — canonical for the Wi-Fi control plane, Intel
transport, `redbear-iwlwifi`, `linux-kpi` wireless layer, and `redbear-wifictl`.
- `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — canonical for the PCI
- `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — canonical for the PCI
interrupt plumbing, MSI/MSI-X delivery, and IOMMU work that NIC drivers depend on.
- `local/docs/BLUETOOTH-IMPLEMENTATION-PLAN.md` — canonical for the Bluetooth stack.
local/docs/RATATUI-APP-PATTERNS.md
-2
View File
@@ -8,7 +8,6 @@
**Cross-references:**
- `local/recipes/system/redbear-power/` (production ratatui 0.30 consumer, 13,091 LoC, 27 modules, 217 tests)
- `local/recipes/tui/tlc/` (46k+ LoC TUI file manager, ratatui 0.29)
- `local/docs/legacy-obsolete-2026-07-25/redbear-power-improvement-plan.md` (improvement roadmap)
- `local/docs/bottom-vs-redbear-power-assessment.md` (bottom comparison assessment)
---
@@ -1595,7 +1594,6 @@ my-tui-app/
- `local/recipes/system/redbear-power/source/src/` — reference implementation (v1.44+, 13,091 LoC, 27 modules, 217 tests)
- `local/recipes/tui/tlc/source/src/` — 46k+ LoC production TUI
- `local/recipes/tui/redbear-tui-theme/` — shared theme constants
- `local/docs/legacy-obsolete-2026-07-25/redbear-power-improvement-plan.md` — improvement roadmap
- `local/docs/bottom-vs-redbear-power-assessment.md` — bottom comparison and borrow analysis
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` — desktop stack planning
- https://ratatui.rs/ — official docs
local/docs/RELEASE-BUMP-WORKFLOW.md
+2 -2
View File
@@ -64,7 +64,7 @@ the *checkout*, not on the branch creation.
When the operator checks out the new release branch, two things can happen:
**A. If the post-checkout hook is installed** (opt-in; see
`local/docs/legacy-obsolete-2026-07-25/HOOKS.md`):
`local/docs/RELEASE-BUMP-WORKFLOW.md` § "Git Hooks"):
```bash
git checkout 0.3.2
@@ -320,7 +320,7 @@ it has no behaviour in sealed mode.
| Local fork dependency rule (path deps, no version strings) | `local/AGENTS.md` § "Local fork dependency rule" |
| Branch and submodule policy (operator-only branches) | `local/AGENTS.md` § "BRANCH AND SUBMODULE POLICY" |
| Tool inventory + modes | `local/scripts/TOOLS.md` |
| Hook install / bypass / inventory | `local/docs/legacy-obsolete-2026-07-25/HOOKS.md` |
| Hook install / bypass / inventory | `local/docs/RELEASE-BUMP-WORKFLOW.md` § "Git Hooks" |
| Fork → upstream tag/mode map | `local/fork-upstream-map.toml` |
| External desktop-stack version map | `local/external-upstream-map.toml` |
| Post-checkout hook source | `local/scripts/post-checkout-version-sync.sh` |
local/docs/USB-IMPLEMENTATION-PLAN.md
+1 -1
View File
@@ -892,7 +892,7 @@ For all of these: when implementation detail is unclear, **port line-by-line fro
- `v1` — initial draft (pre-fork era; now superseded by this live plan)
- `local/docs/USB-IMPLEMENTATION-PLAN.md` — v2 lineage and current live roadmap (archived copy restored here)
- `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — IRQ/MSI-X quality surface that P2-A depends on
- `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — IRQ/MSI-X quality surface that P2-A depends on
- `local/docs/WIFI-IMPLEMENTATION-PLAN.md` — Wi-Fi subsystem plan; sibling first-class-citizen effort
- `local/docs/BLUETOOTH-IMPLEMENTATION-PLAN.md` — Bluetooth plan; uses `redbear-btusb` (USB Bluetooth transport)
- `local/reference/linux-7.1/drivers/usb/` — Linux 7.1 reference (the implementation of excellence)
local/patches/README.md
+2 -2
View File
@@ -82,8 +82,8 @@ verify-patch-content, verify-collision-detection, and the collision
selftest. All must pass for the pre-push hook to allow a `git push`.
For a full operator-decision guide on what to do with new orphans,
see `local/docs/legacy-obsolete-2026-07-25/PATCH-PRESERVATION-AUDIT-2026-07-12.md` (the "Out-of-
scope" section tracks the current Round 5+6 forward work).
see root `AGENTS.md` § "Orphan-Patch Supersession Decision Tree" (the
decision flow for classifying and handling orphan patches).
## Round 7 snapshot
local/scripts/TOOLS.md
+2 -3
View File
@@ -166,7 +166,7 @@ REDBEAR_NO_AUTO_SYNC=1 Bypass for a single checkout.
Guards: `$3==1`, anchored semver branch, no rebase/cherry-pick/merge in
progress, `REDBEAR_NO_AUTO_SYNC` unset, clean tree. Never network, never
regen, never commit. See `local/docs/legacy-obsolete-2026-07-25/HOOKS.md`.
regen, never commit. See `local/docs/RELEASE-BUMP-WORKFLOW.md` § "Git Hooks".
### install-git-hooks.sh (hook installer)
@@ -217,9 +217,8 @@ install-git-hooks.sh (operator opt-in hook installer)
## See also
- `local/docs/legacy-obsolete-2026-07-25/HOOKS.md` — git hooks documentation
- `local/docs/RELEASE-BUMP-WORKFLOW.md` — release-bump operator runbook (includes git hooks documentation)
- `local/docs/RELEASE-BUMP-WORKFLOW.md` — release-bump operator runbook
- `local/docs/legacy-obsolete-2026-07-25/PATCH-PRESERVATION-AUDIT-2026-07-12.md` — cumulative rounds 0-12
- `local/fork-upstream-map.toml` — fork → upstream tag/mode map
- `local/external-upstream-map.toml` — external desktop-stack version map
- `local/patches/README.md` — patch archive structure