vasilito
1dd1fccbf3
The DRIVER-MANAGER-MIGRATION-PLAN was self-declared complete (the driver-manager cutover happened 2026-07-23 per local/AGENTS.md). It is now historical reference material rather than current planning authority. Move it from local/docs/ into the established legacy-obsolete-2026-07-25/ archive directory, updating every inbound reference. Also includes minor cross-doc alignment for the previous round's relocations: - local/AGENTS.md: update DRIVER-MANAGER-MIGRATION-PLAN to point to the legacy archive - local/docs/REDBEAR-FULL-SDDM-BRINGUP.md: alignment update - local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md: alignment update - local/docs/archived/README.md: refresh archive contents note - local/recipes/system/redbear-driver-policy/source/policy/README.md: policy doc drift alignment - local/scripts/guard-recipes.sh: fix symlink target computation (relative path was being glued onto an absolute path, producing malformed dangling links like '../..//mnt/.../recipe.toml') -- this is a real bug fix discovered during this audit round.
Archived Documentation
Last synced: 2026-07-27 — this archive inventory is dynamically maintained and tracks only files that currently exist in this directory.
These documents were written during earlier phases of Red Bear OS development. They contain historical context and analysis but are superseded by more current plans. They are kept for reference only.
Inventory
| Archived | Status |
|---|---|
ACPI-I2C-HID-IMPLEMENTATION-PLAN.md |
Deferred; USB HID remains the primary input path. |
BUILD-SYSTEM-IMPROVEMENTS.md |
Historical build-system improvement plan; absorbed into ../../AGENTS.md § BUILD SYSTEM POLICIES and ../legacy-obsolete-2026-07-25/BUILD-SYSTEM-HARDENING-PLAN.md. |
DRIVER-MANAGER-MIGRATION-PLAN.md |
v1.0 → v5.9 round-by-round migration plan (2861 lines, 182 KB). Historical record of pcid-spawner → driver-manager cutover and all v5.x work. Superseded by ../DRIVER-MANAGER.md (post-v5.9 systematic assessment). Read the current-state doc; read this archive for round-by-round history. |
IMPLEMENTATION-MASTER-PLAN.md |
Completion report of the 2026-07 audit sprint; superseded by ../CONSOLE-TO-KDE-DESKTOP-PLAN.md. |
IMPROVEMENT-PLAN.md |
RESOLVED quality-audit plan (38/38); historical reference only. |
INTEL-HDA-IMPLEMENTATION-PLAN.md |
Deferred; audio remains a later priority. |
KERNEL-SCHEDULER-MULTITHREAD-IMPROVEMENT-PLAN.md |
Historical scheduler analysis kept for reference. |
README.md |
Archive metadata only. |
RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md |
relibc IPC surface plan; credential work resolved in ../KERNEL-IPC-CREDENTIAL-PLAN.md. |
SLEEP-IMPLEMENTATION-PLAN.md |
Historical sleep/power-state plan; superseded by the ACPI power-surface work tracked in ../ACPI-IMPROVEMENT-PLAN.md. |
repo-governance.md |
Historical governance note kept for reference. |
SOURCE-ARCHIVAL-POLICY.md |
Absorbed into ../../AGENTS.md § RELEASE MODEL / SOURCE-OF-TRUTH RULE. |
STUBS-FIX-PROGRESS.md |
Final-state log of the completed stub→real-code campaign. |
SYSTEM-STABILITY-AND-UPSTREAM-SYNC-PLAN.md |
Moved here 2026-07-26 (round-5 stale-doc cleanup); active tracking role absorbed by ../CONSOLE-TO-KDE-DESKTOP-PLAN.md and the current subsystem plans. |
UPSTREAM-SYNC-PROCEDURE.md |
Moved here 2026-07-27 from ../legacy-obsolete-2026-07-25/. General per-fork upstream-sync procedure (Steps 1–12, decision matrix, rollback) still valid; the PCI-spawner sections were rewritten to reflect the completed driver-manager cutover (pcid-spawner retired 2026-07-24). Superseded for PCI-driver architecture by ../DRIVER-MANAGER.md. |
USB-BOOT-INPUT-PLAN.md |
Superseded by the current USB implementation planning. |
USB-VALIDATION-RUNBOOK-2026-07.md |
Historical validation runbook for the earlier USB phase. |
XHCID-DEVICE-IMPROVEMENT-PLAN.md |
Superseded by the current USB implementation planning. |
Supersession notes
USB-BOOT-INPUT-PLAN.mdandXHCID-DEVICE-IMPROVEMENT-PLAN.mdwere absorbed into the newer USB implementation work.ACPI-I2C-HID-IMPLEMENTATION-PLAN.mdandINTEL-HDA-IMPLEMENTATION-PLAN.mdremain as deferred historical references.KERNEL-SCHEDULER-MULTITHREAD-IMPROVEMENT-PLAN.mdandrepo-governance.mdare retained as archive-only context.- 2026-07-18 archival (release-bump cleanup):
IMPROVEMENT-PLAN.md,IMPLEMENTATION-MASTER-PLAN.md,STUBS-FIX-PROGRESS.md,RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md,SOURCE-ARCHIVAL-POLICY.mdmoved here fromlocal/docs/. All inbound references were updated to thearchived/paths in the same pass. - 2026-07-26 archival (round-5 stale-doc cleanup):
SYSTEM-STABILITY-AND-UPSTREAM-SYNC-PLAN.mdmoved here because its active tracking role was absorbed by../CONSOLE-TO-KDE-DESKTOP-PLAN.mdand the current subsystem plans. - 2026-07-27 archival (PCI-spawner doc cleanup):
UPSTREAM-SYNC-PROCEDURE.mdmoved here from../legacy-obsolete-2026-07-25/. Its PCI-spawner sections previously contradicted the completeddriver-managercutover (v5.6); the contradictory sections were rewritten in-place and the doc relocated here as historical reference. Inbound references inDRIVER-MANAGER-MIGRATION-PLAN.md,NETWORKING-IMPROVEMENT-PLAN.md, andPACKAGE-BUILD-QUIRKS.mdwere repointed to thisarchived/path in the same pass. - 2026-07-27 archival (driver-manager doc consolidation):
DRIVER-MANAGER-MIGRATION-PLAN.mdmoved here. The 2861-line v1.0 → v5.9 round-by-round plan was replaced by../DRIVER-MANAGER.md(~685 lines, current-state focused). The new doc adds the post-v5.9 systematic correctness review (§ 4) and the actionable fix/improvement plan (§ 5), neither of which existed in the old plan. Historical round-by-round detail is preserved in this archive. Inbound references in../HARDWARE-VALIDATION-MATRIX.md,../CONSOLE-TO-KDE-DESKTOP-PLAN.md,../REDBEAR-FULL-SDDM-BRINGUP.md,../evidence/driver-manager/D5-AUDIT.md,../../AGENTS.md,../../../docs/README.md, and../../../local/recipes/system/redbear-driver-policy/source/policy/README.mdwere repointed to../DRIVER-MANAGER.mdin the same pass.