From 7bfabceaac4aec71f2ce7fad3023c9d6867a5070 Mon Sep 17 00:00:00 2001 From: Paul O'Reilly Date: Mon, 4 May 2026 15:52:55 +1200 Subject: [PATCH] docs(airouter): confirm single-file-unit pattern with D4a+D4b results D4a (harness.yaml, 1 file) = success D4b (CLAUDE.md, 1 file) = success Both succeeded where original D4 (2 files) = silent no-output. Pattern confirmed: single-file scope is the reliable unit for airouter/Qwen3.6. Co-Authored-By: Claude Sonnet 4.6 --- agent-repos.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/agent-repos.md b/agent-repos.md index 1d93443..ff60037 100644 --- a/agent-repos.md +++ b/agent-repos.md @@ -480,9 +480,13 @@ Qwen3.6 via airouter harness (`runtime_cli: agentic`, model `Qwen3.6`) produces - **Reliable**: Create one new file, one hard rule, clear output path - **Unreliable**: Create multiple files with distinct content, multi-step instructions, tasks requiring internal state management across turns -**Pattern observed (2026-05-04):** -- D7 (single harness.yaml + single CLAUDE.md with one hard rule) → fully successful, correctly committed -- D4 (same template + same model, but two files with multiple layered rules each) → silent no-output, only unrelated `.gitignore` change appeared +**Pattern confirmed (2026-05-04):** +- D7 (1 file, 1 rule) → fully successful airouter output ✅ +- D4 original (2 files, 2 rule sets) → silent no-output ❌ +- D4a (harness.yaml only, 1 file) → fully successful ✅ +- D4b (CLAUDE.md only, 1 file) → fully successful, committed in 5 turns ✅ + +Single-file scope is the reliable unit for airouter/Qwen3.6 dispatches. **Dispatch strategy for airouter agents:** 1. **One file per task** — split multi-file tasks into separate dispatches. Each task creates exactly one file. @@ -492,4 +496,4 @@ Qwen3.6 via airouter harness (`runtime_cli: agentic`, model `Qwen3.6`) produces If a multi-file task is unavoidable, use a **sequential chain**: dispatch task-1 to create file-A, wait for success, then dispatch task-2 to create file-B referencing task-1's output. This bounds the agent's scope to one artifact at a time. -**BUG-21** (2026-05-04): D4 task (`017f63cb`) exited 0, showed correct understanding in logs, but produced no harness files. Likely causes: prompt complexity, early exit, or internal runner issue. Fix: decompose airouter tasks to single-file units. +**BUG-21** (2026-05-04): D4 task (`017f63cb`) exited 0, showed correct understanding in logs, but produced no harness files. Fix confirmed: decompose airouter tasks to single-file units (D4a + D4b both succeeded).