feat: implement numbered patch-stack apply/verify enforcement (DGR-028)

Split the range-loader patch into single-concern patches 0002-0005 (loader,
filtered state report, boundary I/O endpoint guard, worker range-report
hook), add UPSTREAM-ASSUMPTIONS.json describing each patch's assumptions,
and enforce control-plane/license boundary checks plus first-incompatible-
patch reporting in scripts/llama_cpp_dependency.py apply/reverse/verify.

7 passed in tests/test_llama_cpp_dependency.py; SHA256SUMS verified against
all five patches; focused native CTest (test-meshnet-range-ownership 1/1)
recorded in evidence README (build/ dir not present in this environment to
independently reverify).

packages/node/native/llama/THIRD_PARTY_NOTICES.md

@@ -6,8 +6,12 @@ The reproducibility harness fetches source from
 
 - Upstream license: MIT. The fetched checkout's `LICENSE` and copyright notices
   remain intact and must accompany any redistribution of this source or binary.
-- Meshnet's one-patch CMake marker is an additive local change. It does not
-  replace, relicense, or remove upstream notices.
+  No patch in the numbered stack touches `LICENSE`/copyright files or removes
+  any upstream copyright or license text; this is enforced on every apply.
+- Meshnet's five-patch stack (CMake marker, range loading, filtered state,
+  boundary I/O, worker hooks) is an additive local change. It does not
+  replace, relicense, or remove upstream notices, and it contains no Meshnet
+  routing, billing, relay, authentication, Tracker, or transport code.
 - No donor code is included. In particular, Mesh-LLM remains a research/test
   donor only and no part of its scheduler, routing, discovery, package manager,
   or patch series is incorporated here.