3.1 KiB
3.1 KiB
16 — Produce the upstream llama.cpp collaboration package
Status: ready-for-agent
Mandatory fresh-session context
- Read RALPH-CONTEXT.md completely before changing code.
- This issue is
DGR-016in prd.json. - Read the evidence README for every dependency listed below.
- Inspect current code and
git status; historical text and previous agent claims are not evidence.
Description
As a maintainer, I need narrow upstreamable proposals so that our patch burden can shrink without asking llama.cpp to own Meshnet networking.
Expected durable outputs
- Narrow upstream patches/tests
- Generic API design note
- Human-ready llama.cpp outreach package
- evidence/DGR-016/README.md
Acceptance criteria
- Separate generic llama.cpp hooks from Meshnet protocol/control-plane code.
- Prepare minimal reproducible examples and tests for range-aware loading, boundary input/output, and layer-filtered KV.
- Compare the proposal with Nakshatra and prima.cpp evidence and explain why the API is generally useful.
- Preserve one scoped commit/patch per concern against the exact upstream pin.
- Produce an outreach document suitable for Georgi/llama.cpp maintainers; actual sending remains a human action.
- Targeted pytest tests pass
- python -m compileall packages tests passes for Python changes
- git diff --check passes
- Default tests remain deterministic, model-download-free, API-credit-free, and GPU-free
- Full deterministic pytest -q passes, or the exact pre-existing unrelated failure is recorded with a clean-tree reproduction
- Pinned native C++ target builds and focused CTest/protocol tests pass where native code is touched
- llama.cpp patch stack applies cleanly to the exact pinned commit where patch code is touched
- Read .scratch/distributed-gguf-runtime/RALPH-CONTEXT.md and this story issue completely before changing code
- Read and verify every dependency evidence README before relying on dependency behavior
- Preserve all pre-existing working-tree changes and stage only files belonging to this story
- Write .scratch/distributed-gguf-runtime/evidence/DGR-016/README.md with files changed, exact commands and real results, limitations, compatibility notes, and dependent-story handoff
- Update only this story issue to Status: done after every acceptance criterion and quality gate passes
Dependency handoff
DGR-010must havepasses: true; read../evidence/DGR-010/README.mdand verify its referenced files/commands.
Finish contract
- Create the task evidence directory and durable handoff required above.
- Preserve real failures and blockers; never fabricate benchmark, model, test or hardware output.
- Change this issue to
Status: doneonly after all criteria pass. - Emit
<promise>COMPLETE</promise>only after the evidence handoff exists.