3.1 KiB
3.1 KiB
04 — Create the reproducible pinned llama.cpp patch stack
Status: ready-for-agent
Mandatory fresh-session context
- Read RALPH-CONTEXT.md completely before changing code.
- This issue is
DGR-004in 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 a small auditable fork boundary so that upstream updates do not turn the runtime into an unmaintainable stitched codebase.
Expected durable outputs
- Exact llama.cpp upstream pin
- Numbered minimal patch stack
- Reproducible fetch/apply/build smoke
- evidence/DGR-004/README.md
Acceptance criteria
- Pin one exact llama.cpp commit through a reproducible source dependency mechanism.
- Store a numbered minimal patch stack separately from Meshnet networking code.
- Add a build script that applies/checks patches and builds the standalone worker without manual source copying.
- Record upstream file/ABI assumptions and fail clearly when the pin changes.
- Preserve upstream license and attribution notices.
- Add a clean rebuild smoke test that does not download a model.
- 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-004/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-001must havepasses: true; read../evidence/DGR-001/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.