chore: triage maintenance review and close completed stories

.scratch/distributed-gguf-runtime/PRD.md

@@ -44,6 +44,102 @@ Real-model/hardware stories must:
 
 Before a story is marked complete, run the full deterministic `pytest -q` suite or record the exact pre-existing unrelated failure with a clean-tree reproduction.
 
+## Dependency Graph and Status
+
+Status as of 2026-07-14 (MAINT-003). Authoritative per-story status is
+`passes` in [prd.json](prd.json); closed issues live in
+`docs/issues/distributed-gguf-runtime/`, open and blocked issues in
+[issues/](issues/).
+
+```mermaid
+graph TD
+    classDef done fill:#c8e6c9,stroke:#2e7d32;
+    classDef blocked fill:#ffcdd2,stroke:#c62828;
+
+    DGR001[DGR-001 perf contract]:::done
+    DGR002[DGR-002 gRPC Shard protocol]:::done
+    DGR003[DGR-003 artifact/recipe identity]:::done
+    DGR004[DGR-004 pinned llama.cpp patch stack]:::done
+    DGR005[DGR-005 dense-Llama range ownership]:::done
+    DGR006[DGR-006 boundary input/output]:::done
+    DGR017[DGR-017 GLM-5.2 target/alpha contract]:::done
+    DGR018[DGR-018 whole-model GLM oracle]:::blocked
+    DGR019[DGR-019 GLM range/DSA/IndexShare]:::blocked
+    DGR020[DGR-020 distributed GLM alpha]:::blocked
+    DGR007[DGR-007 Hot KV State]
+    DGR008[DGR-008 C++ gRPC worker]
+    DGR009[DGR-009 Meshnet integration]
+    DGR010[DGR-010 local two-process acceptance]
+    DGR011[DGR-011 two-machine route]
+    DGR012[DGR-012 continuous batching]
+    DGR013[DGR-013 failure/cancel/restart]
+    DGR014[DGR-014 release gate]
+    DGR015[DGR-015 Qwen3 adapter]
+    DGR016[DGR-016 upstream package]
+
+    DGR002 --> DGR003
+    DGR017 --> DGR003
+    DGR001 --> DGR004
+    DGR017 --> DGR004
+    DGR003 --> DGR005
+    DGR004 --> DGR005
+    DGR002 --> DGR006
+    DGR005 --> DGR006
+    DGR001 --> DGR017
+    DGR002 --> DGR017
+    DGR003 --> DGR018
+    DGR004 --> DGR018
+    DGR017 --> DGR018
+    DGR005 --> DGR019
+    DGR006 --> DGR019
+    DGR018 --> DGR019
+    DGR006 --> DGR007
+    DGR019 --> DGR007
+    DGR002 --> DGR008
+    DGR003 --> DGR008
+    DGR004 --> DGR008
+    DGR006 --> DGR008
+    DGR007 --> DGR008
+    DGR003 --> DGR009
+    DGR008 --> DGR009
+    DGR009 --> DGR010
+    DGR010 --> DGR011
+    DGR007 --> DGR012
+    DGR009 --> DGR012
+    DGR010 --> DGR012
+    DGR008 --> DGR013
+    DGR009 --> DGR013
+    DGR001 --> DGR014
+    DGR011 --> DGR014
+    DGR012 --> DGR014
+    DGR013 --> DGR014
+    DGR014 --> DGR015
+    DGR010 --> DGR016
+    DGR007 --> DGR020
+    DGR008 --> DGR020
+    DGR009 --> DGR020
+    DGR011 --> DGR020
+    DGR013 --> DGR020
+    DGR017 --> DGR020
+    DGR018 --> DGR020
+    DGR019 --> DGR020
+```
+
+- **Done (`passes: true`):** DGR-001, DGR-002, DGR-003, DGR-004, DGR-005,
+  DGR-006, DGR-017.
+- **Blocked on hardware:** DGR-018 requires a 256-GiB-class host with at least
+  224 GiB runtime-accessible memory and 250 GB free storage outside `/home`;
+  no such host is currently available (development host: 124.9 GiB MemTotal).
+  Exact preflight output: [evidence/DGR-018/BLOCKED.md](evidence/DGR-018/BLOCKED.md).
+  DGR-019 (needs the DGR-018 oracle) and DGR-020 (needs DGR-018/DGR-019 plus
+  multiple physical consumer nodes) are blocked transitively.
+- **Consequence of the graph as written:** DGR-007 depends on DGR-019, so every
+  remaining story (DGR-007 through DGR-016) is transitively blocked on the
+  256-GiB host. Unblocking the generic dense pipeline without that host would
+  require an explicit re-planning decision to relax the DGR-007 → DGR-019
+  dependency; that decision is out of scope for maintenance and has not been
+  made.
+
 ## User Stories
 
 ### DGR-001: Lock the safetensors-versus-GGUF performance contract