diff --git a/local/AGENTS.md b/local/AGENTS.md
index 3b60074b2d..6602fa30e2 100644
--- a/local/AGENTS.md
+++ b/local/AGENTS.md
@@ -1422,32 +1422,28 @@ When mainline updates affect our work:
   also be treated as first-class subsystem plans, not as side notes.
 - `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` is the current umbrella plan for
   IRQ delivery, MSI/MSI-X quality, IOMMU validation, and other low-level controller completeness work.
-- `local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md` (v3.0, 2026-07-22) is the canonical planning
+- `local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md` (v3.1, 2026-07-23) is the canonical planning
   authority for the migration from `pcid-spawner` (`local/sources/base/drivers/pcid-spawner/`) to
-  `driver-manager` (`local/recipes/system/driver-manager/`). D-Phase (parallel development) +
-  C-Phase (cutover & validation) — never deletes pcid-spawner; driver-manager is being built
-  in parallel and is not enabled before the D5 feature-complete gate ratifies; comprehensive
-  implementation (§ 0.5) is a binding constraint; cross-references Linux 7.1 PCI driver model
-  and CachyOS. v3.0 records the 2026-07-22 major assessment
-  (`local/docs/evidence/driver-manager/ASSESSMENT-2026-07-22.md`, findings B1–G10): the
-  `<addr>/bind` claim endpoint never existed in pcid (claim collapses into channel `ENOLCK`
-  exclusivity per P0-1 — the pcid-spawner model); the pciehp/AER listeners poll files no
-  producer creates (restated; producers are P2-1); linux-kpi and driver-manager were two
-  competing claim systems with zero mutual awareness (the LDR track unifies them under
-  driver-manager ownership with a spawned-mode `pci_register_driver`); `modern_tech` was
-  advisory theater (P0-3 strips it); and runtime validation becomes a hard gate (P0-4).
-  The v3.0 work program: P0 correctness blockers (claim collapse, orphan-patch resolution,
-  modern_tech/exec cleanup, QEMU runtime gate) → LDR Linux-Driver-Reuse (unified claim,
-  spawned-mode registration, iwlwifi/amdgpu onboarding, linux-kpi API completion) →
-  P2 operator/event surface (pcid producers, scheme write endpoints, trigger-based retry) →
-  P3 policy/hygiene (quirk phases, AER recovery actions, firmware packaging).
-  94 tests across 4 crates pass; the § 0.5 audit gate reports 0 violations;
-  `driver-manager` compiles warning-free on host and on the redox target.
-  C-phase (C0–C4) cutover is dormant and requires
-  operator ratification. See `local/docs/evidence/driver-manager/D5-AUDIT.md` for
-  capability-level status.
-  The inline deferred comments in `config/redbear-mini.toml:31` and
-  `config/redbear-device-services.toml:9-13` remain accurate until C4 ratifies.
+  `driver-manager` (`local/recipes/system/driver-manager/`). **CUTOVER COMPLETE (2026-07-23,
+  operator-ratified):** driver-manager owns the boot-time PCI match/claim/spawn path in every
+  `redbear-*` config; pcid-spawner is retired from configs and gated behind
+  `/etc/driver-manager.d/disabled` as the operator fallback (never deleted). init supports
+  systemd-style `ConditionPathExists` (with `!` negation) for the gate. v3.1 records the
+  completed P0/LDR/P2 program: claim-via-channel collapse (`ENOLCK` exclusivity — the
+  pcid-spawner model); spawned-mode `pci_register_driver` in linux-kpi (honors
+  `PCID_CLIENT_CHANNEL`; driver-manager is the single owner of match-claim-spawn for native
+  and Linux-port daemons); linux-kpi real MSI/MSI-X + `pci_request_regions` +
+  `pcie_capability_*` + PM state; redbear-iwlwifi `--daemon` onboarding + `70-wifi.toml`;
+  `--import-linux-ids` Linux id_table→TOML pipeline; scheme operator surface
+  (`bind`/`unbind`/`new_id`/`remove_id`/`driver_override`/`rescan`); Tier-1 driver_override;
+  success-triggered deferred retry; modern_tech/exec advisory theater removed. Open: P0-4
+  QEMU runtime gate (in progress), 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) and
+  `local/docs/evidence/driver-manager/D5-AUDIT.md` for capability status.
+  The inline deferred comments in `config/redbear-device-services.toml` were resolved by
+  the cutover.
 - `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,