mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-10-21 14:21:48 +00:00
6a2b3a38ac
* feat(managed-agent): Collect retired tool output safely Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * chore(managed-agent): Sync retention formatting and verify collection Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * codex: address PR review feedback (#13087) * codex: address PR review feedback (#13087) * test(managed-agent): Add tool output collection deployment gates Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * codex: address PR review feedback (#13090) * docs(managed-agent): Preserve deployment gate identifiers * fix(managed-agent): Advance eligible tool output collection * codex: address PR review feedback (#13090) * chore(ci): Drop merged O4-2 base branch from SDK Java trigger This PR's base moved to main after #13225 merged; no PR will target the merged codex/managed-tool-result-o4-2 branch again. Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * docs(managed-agent): Refresh operations runbook for merged O4-2 Audit found the runbook still pointed at the pre-merge baseline SHA and the old collection V33, contradicting the lifecycle design doc in the same diff. State the merged stack without a volatile SHA, use the current V30/V31/V32/V33(definitions)/V34(collection) sequence in both languages, and say the SDK Java workflow targets main now that the stacked base branch is merged. Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> --------- Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> Co-authored-by: yiliang114 <1204183885@qq.com> Co-authored-by: Shaojin Wen <szujobs@gmail.com> |
||
|---|---|---|
| .. | ||
| client | ||
| managed-agent-server | ||
| qwencode | ||
| runtime-broker | ||