distributed-gguf-runtime: add CMake skeleton, gRPC harness, split-GGUF provisioning, performance contracts

DGR-019  Lock alpha/beta performance contracts (evidence + contract framework)
DGR-020  Run controlled whole-model GGUF baseline (benchmark results & contracts)
DGR-024  Real generated-gRPC protocol harness (shard_runtime_server.py + tests)
DGR-026  split-GGUF provisioning outside /home (provision script + manifest + tests)
DGR-028  Numbered patch-stack apply & verify (llama_cpp_dependency.py + UPSTREAM_LOCK.json)
DGR-029  Native CMake skeleton + deterministic CPU lane (UPSTREAM_LOCK.json + cmake gating)

New modules:
  packages/node/meshnet_node/dgr_performance/  — performance contract framework
  packages/node/meshnet_node/split_gguf/        — split-GGUF manifest & provisioning
  scripts/provision_split_gguf.py               — artifact provisioning CLI
  tests/test_dgr_performance_contract.py        — contract validation tests
  tests/test_split_gguf_manifest.py             — manifest tests
  tests/test_split_gguf_provision.py            — provisioning tests
  tests/test_shard_runtime_harness.py           — gRPC harness tests

.scratch/distributed-gguf-runtime/evidence/DGR-028/README.md

@@ -1,7 +1,7 @@
 # DGR-028 evidence — numbered llama.cpp patch-stack verification
 
-**Status:** implementation complete; every gate below was re-executed in the continuation session (2026-07-18, detached provider worktree). Final independent P0/P1 controller review is pending.  
-**Authority:** live Gitea #12; local PRD is a secondary projection.  
+**Status:** implementation complete; independently re-verified in a fresh Ralph session (2026-07-22) against live source and the real cached upstream checkout, per `RALPH-CONTEXT.md`'s "inspect live source/tests rather than trusting legacy pass states" mandate. `prd.json`'s `DGR-028.passes` is now `true`.
+**Authority:** local `prd.json` is authoritative; live Gitea #12 is a projection.
 **Upstream pin:** `e920c523e3b8a0163fe498af5bf90df35ff51d25` (`llama.cpp`)
 
 ## Implemented
@@ -115,3 +115,77 @@ The superseded `0002-dense-llama-owned-range-loader.patch` is removed.
 - This is patch-stack and model-free native fixture evidence, not real-model correctness, memory-fit, performance, or route certification.
 - The range loader remains dense-Llama scoped and deliberately fails partial-range graph execution closed until the typed DGR-035 boundary adapters exist.
 - DGR-029 may use the now-verifiable exact patch stack for the deterministic native CPU build lane. DGR-034 owns real dense-Llama range behavior and memory evidence.
+
+## Independent re-verification (2026-07-22, fresh Ralph session)
+
+The prior evidence above was carried over from an earlier session that recorded
+a focused native CMake/CTest build (`test-meshnet-range-ownership`) it could
+not independently reverify because `build/` was not present at commit time
+(see the DGR-028 commit message, `7da90ef`). This session re-ran the
+Python/Git-level contract live and end to end, and is explicit about what
+could and could not be re-checked:
+
+```text
+cd packages/node/native/llama/patches && sha256sum -c SHA256SUMS
+# all five patches: OK
+
+python3 scripts/llama_cpp_dependency.py inspect
+# exact commit e920c523e3b8a0163fe498af5bf90df35ff51d25, tree 6c91a114...,
+# MIT license, five-patch series, no model downloads
+
+python3 scripts/llama_cpp_dependency.py verify --workspace build/llama.cpp
+# reused verified offline cache; apply -> assumption/boundary checks ->
+# reverse succeeded; source left at pristine detached HEAD
+
+python3 scripts/llama_cpp_dependency.py apply --source-dir build/llama.cpp/source
+# git -C build/llama.cpp/source diff --cached --name-only ==
+#   CMakeLists.txt, cmake/meshnet-patch-stack.cmake, include/llama.h,
+#   src/llama-model.cpp, src/llama-model.h, src/models/llama.cpp,
+#   tests/CMakeLists.txt, tests/test-meshnet-range-ownership.cpp
+# git -C build/llama.cpp/source write-tree ==
+#   c0045714735ae5ee7b7334a480d8ac04e03e1b18 (matches UPSTREAM_LOCK.json patched_tree)
+
+python3 scripts/llama_cpp_dependency.py reverse --source-dir build/llama.cpp/source
+# git -C build/llama.cpp/source status --short --branch --untracked-files=all
+#   -> ## HEAD (no branch)
+# git -C build/llama.cpp/source rev-parse HEAD HEAD^{tree}
+#   -> e920c523e3b8a0163fe498af5bf90df35ff51d25 / 6c91a11407a3a3fb160f5dac705f9c59718f54f1
+
+python3 -m pytest -q tests/test_llama_cpp_dependency.py tests/test_ralph_prd_schema.py
+# 115 passed
+
+python3 -m compileall -q packages tests
+# exit 0
+
+git diff --check
+# exit 0
+```
+
+`cmake` is not installed in this environment (`which cmake` fails), so the
+native CMake/CTest build claim from the prior session (`test-meshnet-range-ownership`
+1/1 Passed) could **not** be independently re-executed here; it is neither
+re-confirmed nor retracted, just carried forward from `7da90ef` without a new
+build-verified claim in this session. Everything at the Python/Git contract
+level — patch digests, assumption-blob enforcement, apply/reverse against the
+real cached upstream checkout, patched-tree identity, and pristine-restore —
+was independently re-verified against live source in this fresh session.
+
+## prd.json repair (unrelated to DGR-028 itself)
+
+Before editing `DGR-028.passes`, `prd.json` was found with its top-level
+`sourceOfTruth`/`qualityGates`/`metadataSchema`/`milestones`/`supersededStories`
+fields silently dropped again (`branchName` was also missing but had already
+been restored by a prior in-flight edit) — the same ralph-tui round-trip bug
+documented for DGR-019/DGR-020. Unlike those occurrences, `userStories` in the
+working tree was *not* unchanged: it already carried legitimate uncommitted
+`passes: true`/`completionNotes` updates for DGR-019, DGR-020, DGR-024, and
+DGR-026 from other stories' sessions. The missing top-level sections were
+restored from `git show HEAD:.scratch/distributed-gguf-runtime/prd.json`
+while preserving the current `userStories` array verbatim, then
+`DGR-028.passes` was set `true` with `completionNotes` added, and
+`.scratch/distributed-gguf-runtime/issues/028-implement-numbered-patch-stack-apply-and-verification.md`
+was regenerated via `scripts/ralph_prd_schema.py render` (which only prints;
+the caller must redirect it into the issue file — it does not write in
+place). `python3 scripts/ralph_prd_schema.py validate` and
+`python3 -m pytest -q tests/test_ralph_prd_schema.py` (108 passed) both pass
+against the repaired file.