docs: finish de-dangling driver-manager citations; sync Cat 0 lockfile

Remaining hunks from the doc pass: local/AGENTS.md and the
legacy-superseded SUPERSEDED.md still cited the driver-manager
ASSESSMENT-2026-07-22 / D5-AUDIT evidence files and the archived
migration plan as if they were openable. Cargo.lock picks up the
0.3.1 -> 0.3.2 Cat 0 and installer versions.

Cargo.lock

@@ -979,7 +979,7 @@ dependencies = [
 
 [[package]]
 name = "redbear_cookbook"
-version = "0.3.1"
+version = "0.3.2"
 dependencies = [
  "ansi-to-tui",
  "anyhow",
@@ -1017,7 +1017,7 @@ dependencies = [
 
 [[package]]
 name = "redox_installer"
-version = "0.2.42+rb0.3.1"
+version = "0.2.42+rb0.3.2"
 dependencies = [
  "anyhow",
  "arg_parser",

local/AGENTS.md

@@ -1512,7 +1512,7 @@ When mainline updates affect our work:
 - `local/docs/DRIVER-MANAGER.md` (consolidated 2026-07-27, post-v5.9 systematic assessment) is the canonical
   current-state document for `driver-manager` (`local/recipes/system/driver-manager/`). The
   historical round-by-round v1.0 → v5.9 migration plan is archived at
-  `local/docs/archived/DRIVER-MANAGER-MIGRATION-PLAN.md`. **CUTOVER COMPLETE (2026-07-23,
+  the v1.0-v5.9 migration history (removed in the 2026-07-27 consolidation; see `local/docs/SUPERSEDED-DOC-LOG.md`). **CUTOVER COMPLETE (2026-07-23,
   operator-ratified):** driver-manager owns the boot-time PCI match/claim/spawn path in every
   `redbear-*` config, unconditionally; pcid-spawner is fully retired from configs, services,
   build wiring, and the tree. init supports
@@ -1530,8 +1530,8 @@ When mainline updates affect our work:
   P2-1 pcid AER/pciehp producers, P3 policy/hygiene.
   Services integration (assessment § 11): driver-params bridge live; udev-shim driver-binding
   view is a P3 gap; D-Bus correctly absent (bridge-on-demand). See
-  `local/docs/evidence/driver-manager/ASSESSMENT-2026-07-22.md` (B1–G10, § 12 gate) and
-  `local/docs/evidence/driver-manager/D5-AUDIT.md` for capability status.
+  the Round-22 driver-manager assessment (removed in the 2026-07-27 consolidation; see `local/docs/SUPERSEDED-DOC-LOG.md`) (B1–G10, § 12 gate) and
+  the D5 capability audit (removed in the 2026-07-27 consolidation; see `local/docs/SUPERSEDED-DOC-LOG.md`) for capability status.
 - `local/docs/QUIRKS-SYSTEM.md` documents the hardware quirks infrastructure: compiled-in tables,
   TOML runtime files, DMI matching, driver integration, and the linux-kpi C FFI bridge.
 - `local/docs/QUIRKS-IMPROVEMENT-PLAN.md` is the current follow-up plan for removing quirks drift,

local/patches/legacy-superseded-2026-07-22/SUPERSEDED.md

@@ -4,7 +4,7 @@
 **Source:** `local/patches/base/`
 **Destination:** `local/patches/legacy-superseded-2026-07-22/base/`
 **Trigger:** driver-manager v3.0 major assessment
-(`local/docs/evidence/driver-manager/ASSESSMENT-2026-07-22.md`, finding B1/G1)
+(the Round-22 driver-manager assessment (removed in the 2026-07-27 consolidation; see `local/docs/SUPERSEDED-DOC-LOG.md`), finding B1/G1)
 
 Per AGENTS.md § "Orphan-Patch Supersession Decision Tree": both patches
 were orphans — their content exists nowhere in the `local/sources/base`