skynet/best-practices
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(airouter): confirm single-file-unit pattern with D4a+D4b results

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Paul O'Reilly
2026-05-04 15:52:55 +12:00
parent e618ca4d22
commit 7bfabceaac
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
agent-repos.md
View File

@@ -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).