fix: complete the docs/→design/ and openapi→api/ rename references

The file moves (docs/ → design/, docs/api/openapi.json → api/openapi.json) landed
in d01a8fd, but the matching reference updates did not — so mgmt.rs's drift-test
`include_str!("../../../docs/api/openapi.json")` pointed at a path that no longer
exists and the host failed to build. This restores it and updates every reference:

  - mgmt.rs include_str! → ../../../api/openapi.json (fixes the build)
  - web/orval.config.ts codegen target, web/Dockerfile, .dockerignore
  - deb/rpm/Arch packaging install paths
  - CLAUDE.md, the .gitea CI workflows, code doc-comments, design-doc cross-links

docs-site route URLs (/docs/...) untouched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

packaging/windows/drivers/Cargo.toml

@@ -1,6 +1,6 @@
 # Unified in-tree workspace for punktfunk's all-Rust UMDF drivers, on microsoft/windows-drivers-rs
 # (crates.io wdk/wdk-sys/wdk-build — NOT the dev-box ../../crates/wdk* path-deps). Part of the
-# Windows-host rewrite (docs/windows-host-rewrite.md, M1). pf-vdisplay + the gamepad drivers move here.
+# Windows-host rewrite (design/windows-host-rewrite.md, M1). pf-vdisplay + the gamepad drivers move here.
 #
 # Separate from the main cargo workspace (own [workspace] root) because driver crates are cdylibs built
 # with the WDK toolchain (cargo-wdk / wdk-build) on Windows only. Path-deps the shared ABI crate

packaging/windows/drivers/pf-vdisplay/Cargo.toml

@@ -1,6 +1,6 @@
 # pf-vdisplay — the all-Rust UMDF IddCx virtual-display driver (M1 step-2 rewrite onto wdk-sys + the
 # owned pf-driver-proto ABI). Replaces the vendored-binding oracle at packaging/windows/vdisplay-driver/
-# (deleted once on-glass parity is reached, per docs/windows-host-rewrite.md §14 STEP 8).
+# (deleted once on-glass parity is reached, per design/windows-host-rewrite.md §14 STEP 8).
 [package]
 name = "pf-vdisplay"
 edition.workspace = true

packaging/windows/drivers/pf-vdisplay/src/adapter.rs

@@ -137,7 +137,7 @@ pub(crate) fn adapter() -> Option<iddcx::IDDCX_ADAPTER> {
 /// iGPU+dGPU box the OS may otherwise pick the iGPU to render the virtual monitor, so the host's shared
 /// ring textures (created on the NVENC dGPU) can't be opened → `DRV_STATUS_TEX_FAIL` → the host's 20 s
 /// black bail. Pinning the render adapter to the encode GPU fixes that. Unconditional — NOT the
-/// SudoVDA-parity default-off branch (`docs/windows-host-rewrite.md` §2.8). Returns
+/// SudoVDA-parity default-off branch (`design/windows-host-rewrite.md` §2.8). Returns
 /// `STATUS_NOT_FOUND` if called before the adapter exists.
 pub fn set_render_adapter(luid_low: u32, luid_high: i32) -> NTSTATUS {
     let Some(adapter) = adapter() else {

packaging/windows/drivers/pf-vdisplay/src/control.rs

@@ -27,7 +27,7 @@ static WATCHDOG_STARTED: AtomicBool = AtomicBool::new(false);
 /// without a cooperative REMOVE (crash / `TerminateProcess`) left its virtual monitor + swap-chain
 /// worker + pooled D3D device wedged in WUDFHost until the next host start's CLEAR_ALL, and a
 /// not-restarted host left the orphan monitor in the desktop topology indefinitely
-/// (`docs/windows-host-rewrite.md` §2.8). This thread closes that: if no IOCTL arrives for
+/// (`design/windows-host-rewrite.md` §2.8). This thread closes that: if no IOCTL arrives for
 /// `WATCHDOG_TIMEOUT_S` while monitors exist, it departs them all.
 ///
 /// (A WDF `EvtFileClose` on the control handle would be more immediate — the plan's preferred §3.4

packaging/windows/drivers/pf-vdisplay/src/lib.rs

@@ -1,5 +1,5 @@
 //! pf-vdisplay — the all-Rust UMDF IddCx virtual-display driver (M1 step-2 rewrite, on wdk-sys + the
-//! owned pf-driver-proto ABI). See docs/windows-host-rewrite.md §14 for the full port plan.
+//! owned pf-driver-proto ABI). See design/windows-host-rewrite.md §14 for the full port plan.
 //!
 //! STEP 2: the IddCx driver SKELETON — DriverEntry → driver_add builds the full `IDD_CX_CLIENT_CONFIG`
 //! (14 IddCx callbacks + the PnP `EvtDeviceD0Entry`, all stubs) sized via the versioned