2.5 KiB
DGR-004 — Reproducible pinned llama.cpp patch stack
Status: done. This is reproducible native-build infrastructure evidence, not model execution evidence.
Delivered boundary
- Pin:
ggml-org/llama.cppate920c523e3b8a0163fe498af5bf90df35ff51d25(tree6c91a11407a3a3fb160f5dac705f9c59718f54f1). - Ordered patch:
0001-cmake-reserve-meshnet-patch-stack-abi-marker.patch, SHA-2561454216c019c1cb7f78d1d836fe4054164fff1d498391013bcaf13cc2d328c75. - The sole patch adds an interface-library CMake marker. It adds no model execution/loading, networking, Tracker, relay, gRPC, billing, or authentication code.
scripts/llama_cpp_dependency.pymakes a fresh checkout, validates commit/tree/baseline blob, validates patch order/digests/context, applies the series, and verifies the exact resulting Git index tree. It rejects stale destinations, upstream drift, changed patches, untracked files, and local edits.
Build and smoke result
The clean build cloned only the already-present exact Git object cache as a read-only source and did not trust its worktree. CMake 4.4.0 and GCC 15.2.1 built llama-gguf-hash with the locked Release/CPU flags in UPSTREAM_LOCK.json; llama-gguf-hash --help passed with no model download or load.
llama.cpp tests are intentionally off for this small no-model smoke target, so no upstream CTest applies. Meshnet's focused native protocol suite passed independently. Exact results are in commands.txt and results.json.
License, compatibility, and handoff
llama.cpp is MIT licensed. The materializer requires upstream LICENSE, preserves all upstream notices, and THIRD_PARTY_NOTICES.md requires including them in redistribution. No Mesh-LLM code or patch was adopted.
The lock records the patched upstream blob and resulting patched tree. Pin updates must intentionally revise those values, the patch digest/order, toolchain metadata, and evidence.
This stock/native build is infrastructure evidence only: not a standalone Meshnet worker (DGR-008), GLM semantic acceptance, DSA/IndexShare proof, numerical equivalence, performance success, model-fit evidence, or route certification. The stock dense-MLA fallback remains explicitly uncertified. DGR-001 CPU v1 remains stop; DGR-017 is a separate target contract. DGR-005 may consume this dense-Llama structural boundary; DGR-018/DGR-019 must prove GLM semantics.
Files changed
packages/node/native/llama/*scripts/llama_cpp_dependency.pytests/test_llama_cpp_dependency.py- this evidence directory, the DGR-004 issue, and
prd.json