feat(framework+cli): fw-4.41.0 / cli-3.42.0 — Qwen Code agent surface

[montfort]

What

Qwen Code becomes a first-class agent surface, and the update path that would have withheld it from existing installations is fixed.

Why

The question was narrow — do the Qwen and Qoder CLIs get the same rules and configuration Claude Code gets, at init and at later update? The answer split:

• Qoder — covered. Skills ship at dist/.qoder/skills/ (init / install-skills: Qoder CLI is not a supported skill target — .qoder/skills/ is never materialized #399), and rules arrive via AGENTS.md: the Qoder runtime file-searches **/AGENTS.md and injects each match as an instruction source.
• Qwen Code — not covered at all. Verified against the installed @qwen-code/qwen-code: its context-filename resolver ends in ["QWEN.md"] : Array.isArray(configured) ? configured : [configured] — the default is QWEN.md alone. AGENTS.md occurs exactly once in the bundle, inside a system-prompt string enumerating files the agent must not modify without permission. Recognized, never loaded. So a Qwen Code user received no governance whatsoever, a strictly worse position than Codex or Qoder.

Changes

New Qwen Code surface

• QWEN.md directive injection (template cloned from GEMINI.md — Qwen Code is a Gemini CLI fork — with a qwen-code-v{version} identity).
• dist/.qwen/skills/ — 15 skills, byte-for-byte mirror of the Claude variants. Qwen Code parses allowed-tools and resolves skills at both project and user scope, so the richer frontmatter is usable rather than merely tolerated.
• straymark install-skills --agent qwen → $QWEN_HOME/skills/, the directory Qwen Code's own Storage.getGlobalQwenDir() resolves.
• straymark validate --agent qwen, and remove cleanup.

Two defects surfaced by the review

• update-framework never created newly-declared injection targets. It skipped every target absent from disk, so an agent surface added to the manifest after installation reached fresh inits only — while STRAYMARK.md § "Directive Injection Markers" documents that init, update-framework and repair all "create any missing target file". The code was the outlier. This is what makes QWEN.md land on existing installations via straymark update rather than requiring straymark repair.
• The Qoder documentation asserted the opposite of the runtime. README + CLI-REFERENCE (3 languages) said Qoder reads skills from ~/.qoder/skills/ "not from the project tree". It resolves a Project scope (<projectRoot>/.qoder/skills/) and watches it. install-skills --agent qoder is a convenience; Codex remains the only agent for which it is mandatory.

Along the way

• validate --agent generalized off its Codex-only shape. The claude-only-key check is now conditional — Qoder and Qwen legitimately carry allowed-tools, so flagging it there would be a false positive by construction.
• New skill-mirror-parity CI job. The .qoder mirror had a parity test since init / install-skills: Qoder CLI is not a supported skill target — .qoder/skills/ is never materialized #399, but the pipeline runs no cargo test, so .codex was the only gated channel. The job runs exactly the two mirror suites — narrow enough not to reopen the deferred "no full suite in CI" decision.
• ADOPTION-GUIDE.md compatibility tables (3 languages) resynced with the README, which had been two releases ahead (no Codex, no Qoder).
• qoder-v1.0 added to the agent identity lists, missing since init / install-skills: Qoder CLI is not a supported skill target — .qoder/skills/ is never materialized #399.

Verification

• cargo test — 949 passed, 0 failed.
• New tests: tree parity + install-skills e2e under QWEN_HOME + manifest surface + validate --agent acceptance (qwen_skills_test.rs); update_creates_injection_targets_that_are_missing_on_disk; inject_test extended from AGENTS.md-only to all seven targets plus template-on-disk.
• Manual e2e against a simulated post-init tree: 15 skills installed into a temp $QWEN_HOME; validate --agent qwen clean with no allowed-tools false positives. This caught a real bug — validate --agent's clap value_parser lives in main.rs, separate from the dispatch in validate.rs, so widening only the latter left the flag rejected at parse time. Fixed and pinned by a test.

straymark init downloads the published release ZIP, so it cannot exercise a local dist/. Confirming QWEN.md through a real init / update, and in the live qwen and qoder CLIs, is deferred to after the fw-4.41.0 tag lands — recorded as a follow-up.

Release

fw-4.40.0 → fw-4.41.0, cli-3.41.1 → cli-3.42.0. Governance footers, version tables (3 languages) and CHANGELOG.md updated. Decision in AIDEC-2026-08-05-001, work in AILOG-2026-08-05-003.

🤖 Generated with Claude Code