metal-kompanion/docs/plan-qwen-tools.md

Plan: Qwen-2.5-Coder with Tool Support + ACF Exposure

Goals

• Make Qwen-2.5-Coder reliably call tools in Happy-Code.
• Expose Agentic-Control-Framework (ACF) as a safe tool registry to the model.
• Keep a fallback protocol (JSON-only) for models lacking native tools.

Steps

1. Profile & System Prompt
   • Enforce JSON-only responses (or native tool schema if platform supports).
   • Inject tool registry and JSON Schemas (kom.memory/local backup + ACF subset).
2. Registry
   • Allowlist: kom.memory.v1.*, kom.local.v1.backup.*, and acf.* wrapper.
   • Reject unknown tools and args mismatches (runtime guard).
3. ACF as Tools
   • Map ACF endpoints: acf.list_tasks, acf.add_task, acf.update_task, acf.read_file, acf.write_file, acf.exec.
   • Require workspace path + pattern allowlists.
4. Validation
   • Golden transcripts for: upsert/search memory, backup export, ACF addTask/execute_command.
5. Observability
   • Log tool calls (names + durations, no payloads).

Deliverables

• docs/tool-calling-without-native-support.md (done)
• docs/plan-qwen-tools.md (this)
• Happy-Code profile snippet for Qwen-2.5-Coder
• ACF tool wrapper module (C++ or Python)