James VeitchandClaude Sonnet 5
d3ee35bfda
Full spec/plan/tasks/BDD scaffold for the llamacpp-integration epic, now that its dependency (llm-provider-abstraction, PR #17) is satisfied. Researched llama-server's router-mode API shape live (postdates training data) rather than assuming it — two details that would have been wrong by assumption: the model identifier field is "id" not "name" (differs from Ollama's /api/tags), and "status" is a nested object ({"value": "..."}) not a flat string. Unlike the prerequisite epic, this decomposition genuinely holds as 4 independent user stories — LlamaCppClient is a new node, not a changed one, so there's no shared "output type" migration forcing an atomic cutover. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0132ojafeazQ3ephcBejEWFj
230 B
230 B
For additional context about technologies to be used, project structure, shell commands, and other important information, read the current plan at specs/008-llamacpp-integration/plan.md