Review corrections, each verified against an installed Qwen Code 0.25.0:
1. web_search does exist. The mapping table said WebSearch had no Qwen
equivalent; Qwen Code exposes web_search as a deferred tool backed by a
DashScope search agent. Now qualified by provider, with web_fetch as the
fallback, and web_search added to the deferred-tools sentence.
2. docs/QWEN-GUIDE.md is not installed. The installer copies .qwen/QWEN.md to
~/.qwen/ but does not copy docs/, so a relative reference to the guide is dead
in any session outside an ECC checkout. Now states that explicitly and links
the guide in the repository.
3. The AGENTS.md loading claim is now version-qualified. It is accurate for
0.25.0 under default settings -- with no context.fileName configured, Qwen's
own debug log resolves "Final ordered QWEN.md,AGENTS.md paths to read" to
both files -- but AGENTS.md is not the documented default context filename, so
the sentence no longer asserts unconditional behaviour and points at
context.fileName instead.
`.qwen/QWEN.md` is copied to `~/.qwen/QWEN.md`, which Qwen Code loads as
home-level agent context in every session. Its current content describes the
install template itself -- 'This directory contains ECC's Qwen CLI install
template', the `./install.sh` invocation, and the managed-module list -- so
every Qwen session spends its context budget on installer documentation while
getting none of the baseline workflow, coding standards, or security checklist.
Every other harness target ships real agent context here: `.gemini/GEMINI.md`
('provides Gemini CLI with the baseline ECC workflow, review standards, and
security checks') and `.codex/AGENTS.md` ('supplements the root AGENTS.md with
Codex-specific guidance'). Qwen was the only target whose context file described
the installer.
Rewrite it against the GEMINI.md structure and add two Qwen-specific sections:
- A Claude-tool-name to Qwen-tool-id mapping. ECC skills, rules, and agent
prompts are authored for Claude Code, so a Qwen agent following them needs the
translation to act correctly.
- An explicit 'Not Available On This Target' note. Hook runtime files are not
selected for Qwen, so an agent must not report a hook-enforced guard or
cost-tracking metric as active. Also records that mcp-configs/ is a baseline
catalog rather than a merged settings file.
The displaced install documentation is not lost: docs/QWEN-GUIDE.md already
covers install, layout, ecc-install-state.json, updating, uninstalling, and the
hook scope decision, so QWEN.md now points there instead of duplicating it.
Counts in the Overview (68 agents / 293 skills / 94 commands) are verified
against the repo and match the figure GEMINI.md already states.
haelyra