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
2.8 KiB
2.8 KiB
DGR-028: Implement numbered patch-stack apply and verification
- Status / triage: completed;
passes: true - Execution mode:
AFK - Milestone:
M1 - Dependencies:
DGR-027 - Blocks (derived):
DGR-029,DGR-034,DGR-069 - Labels:
area:upstream,area:patches,type:tooling,priority:p0,ready-for-agent - Evidence class:
model-free - Hardware:
none - Model:
generic - Upstream:
yes
Objective / description
Fresh Ralph session: read .scratch/distributed-gguf-runtime/RALPH-CONTEXT.md, source issue .scratch/distributed-gguf-runtime/issues/028-implement-numbered-patch-stack-apply-and-verification.md, and evidence READMEs for dependencies (DGR-027) before changing code. Inspect live source/tests rather than trusting legacy pass states. Objective: Maintain a minimal auditable llama.cpp delta with one numbered patch per concern.
Acceptance criteria
- Add deterministic apply/check/reverse verification against the exact manifest pin.
- Separate range loading, boundary I/O, filtered state, and worker hooks into scoped patches.
- Record upstream file/API assumptions and fail with the first incompatible patch when the pin changes.
- Verify license/attribution and prove no Meshnet routing, billing, relay, or authentication code enters the patch stack.
- Applicable shared quality gates in
prd.jsonpass, and the evidence handoff records exact commands/results, changed files, limitations, and dependency handoff.
Shared quality gates
- Targeted deterministic tests pass; Python changes also pass
python -m compileall packages tests. git diff --checkpasses.- Default tests are model-download-free, API-credit-free, and GPU-free.
- Evidence README records exact changed files, commands/results, limitations, and dependency handoff; no fabricated evidence or inherited completion credit.
- Native changes pass focused out-of-tree CMake build and CTest; patch changes verify clean apply/check/reverse against the exact llama.cpp pin.
- Runs are opt-in and record exact artifact/split hashes, runtime/upstream pin, backend/driver, hardware, network, commands, and raw metrics. Model artifacts use configured mounted-drive storage and never
/home. - Preserve existing Transformers behavior and backend-agnostic Tracker routing/load balancing/billing/relay semantics unless an explicit versioned contract says otherwise. One scoped story commit is expected during execution, but this specification-materialization change is not committed.
Evidence handoff
Verified evidence: .scratch/distributed-gguf-runtime/evidence/DGR-028/README.md. Legacy evidence remains provenance only and grants no implementation completion credit.