Prevent duplicate team creation from informational queries

[RerankerGuo]

Summary

• Bug fix: Manager incorrectly created duplicate teams when asked about team relationships
• Root cause: No guardrail in team-management skill to distinguish informational queries from explicit creation requests
• Fix: Added guardrails in SKILL.md + duplicate name detection in create-team.sh

Changes

• manager/agent/skills/team-management/SKILL.md: Added ⚠️ Informational Queries section with explicit rules against creating/modifying teams in response to questions. Added pre-flight check example. Added duplicate creation reminder in Gotchas.
• manager/agent/skills/team-management/scripts/create-team.sh: Added duplicate name detection that fails fast with a clear error message if a team with the same name already exists
• changelog/current.md: Added changelog entry

Test plan

• Shell syntax validation (bash -n)
• CI run on GitHub
• Manual: ask Manager about team relationships, verify no duplicate creation

Closes #987

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[shiyiyue1102]

Thanks for the fix. The informational-query guardrail is aligned with #987, but a few issues need to be addressed before merging:

1. The new duplicate-team error suggests agt get team, while the registered CLI command is agt get teams <name> -o json. Running the suggested singular form only prints the generic agt get help and does not inspect the Team.
2. Please add focused tests for the duplicate check, including existing, missing, and list-command failure cases.
3. Please align the documented condition with the example: the text says name + leader + workers, while the jq expression checks worker list OR leader and does not compare the name.
4. This PR currently conflicts with main in changelog/current.md; please resolve the conflict.

---

感谢修复。针对信息查询增加防误创建规则的方向与 #987 一致，但合并前还需要处理：

1. 新增报错提示使用了 agt get team，实际注册的命令是 agt get teams <name> -o json。执行提示中的单数形式只会输出通用的 agt get 帮助，不会查询 Team。
2. 请为重复检查补充针对性测试，覆盖已存在、不存在以及列表查询失败。
3. 请统一文档和示例的判断条件：文字是 name + leader + workers，jq 示例却是 worker 列表或 leader，且没有比较 name。
4. 当前 PR 与 main 的 changelog/current.md 存在冲突，请先解决。

[RerankerGuo]

Addressed the review feedback and rebuilt the branch on current main.

Changes:

• corrected the inspection command to agt get teams <name> -o json;
• made duplicate checking fail closed when agt get teams fails or returns invalid JSON;
• aligned the Manager guidance and jq example on the actual name-based uniqueness rule;
• added focused regression coverage for an existing Team, a missing Team, and a list-command failure.

Verification:

• bash manager/tests/test-create-team-duplicate-check.sh
• bash -n manager/agent/skills/team-management/scripts/create-team.sh manager/tests/test-create-team-duplicate-check.sh
• git diff --check origin/main...HEAD

[RerankerGuo]

CI attribution: the only failing job is the shared CoPaw test-23-runtime-switch path. It fails because CoPaw state is not persisted to MinIO within the test timeout, then the unrelated CoPaw→QwenPaw migration assertions fail. This PR does not touch runtime persistence or test-23; the other 11 shard-C tests pass. The same failure reproduced on #1101. I attempted gh run rerun --failed, but GitHub requires repository-admin rights for an external contributor, so no empty commit was added merely to retrigger CI.