feat(ADR-058): Phase 3-4 — GGUF engine, Ed25519 signing, IPFS distribution, hot-patch

[ruvnet]

Summary

• Phase 3: GGUF inference engine with binary header parsing, node-llama-cpp integration (optional), async streaming, and RVKV KV-cache persistence with SHA256 integrity
• Phase 4: Ed25519 code signing (PEM key management, canonical JSON digests, tamper detection), IPFS publishing via Pinata, and RVFP hot-patch format with atomic section replacement and rollback
• Deep review fixes: PEM/DER interop, HTTP timeouts + redirect limits, mandatory cache footer, canonical JSON in patch signatures, signer flag passthrough

New modules (3)

File	Lines	Purpose
gguf-engine.ts	452	GGUF binary parser + local inference via node-llama-cpp
rvfa-signing.ts	461	Ed25519 signing/verification with PEM key management
rvfa-distribution.ts	406	RVFP patch format + Pinata IPFS publishing

Modified (3)

File	Change
ruvllm-bridge.ts	Integrated GGUF engine as preferred Tier 2 backend
appliance.ts	Wired sign/publish/update subcommands
appliance-advanced.ts	Extracted 3 CLI subcommands (500-line limit)

Test plan

• 75 new tests across 3 test files (26 GGUF, 21 signing, 28 distribution)
• 59 Phase 1-2 tests pass without regression (134/134 total)
• Tamper detection: header modification, section modification, footer corruption
• Round-trip: key generation → save → load → sign → verify
• Patch lifecycle: create → verify → apply → post-verify with rollback
• Target mismatch: wrong name, version, nonexistent section
• Gzip compression round-trip in patches
• Re-signing replaces old signature cleanly

🤖 Generated with claude-flow