docs/cli.md tool ID list out of sync with src/core/config.ts

[coderabbitai]

Summary

The Supported tool IDs (--tools) line in docs/cli.md is missing vibe, which is a valid, available tool registered in src/core/config.ts.

This is a pre-existing gap — vibe was already absent before PR #1211 (which only added atomcode to the existing list). The companion doc docs/supported-tools.md already lists vibe correctly, so only docs/cli.md needs updating.

Missing entry

Tool ID	Present in config.ts	Present in docs/cli.md	Present in docs/supported-tools.md
vibe	✅	❌	✅

Note: agents also appears in src/core/config.ts but is not in the docs/cli.md list — please verify whether it is a user-facing tool ID or an internal/group entry and update docs accordingly if needed.

Fix

In docs/cli.md, line 110, add vibe in alphabetical order between trae and windsurf:

-**Supported tool IDs (`--tools`):** `amazon-q`, `antigravity`, `atomcode`, `auggie`, `bob`, `claude`, `cline`, `codex`, `forgecode`, `codebuddy`, `continue`, `costrict`, `crush`, `cursor`, `factory`, `gemini`, `github-copilot`, `iflow`, `junie`, `kilocode`, `kimi`, `kiro`, `opencode`, `pi`, `qoder`, `lingma`, `qwen`, `roocode`, `trae`, `windsurf`
+**Supported tool IDs (`--tools`):** `amazon-q`, `antigravity`, `atomcode`, `auggie`, `bob`, `claude`, `cline`, `codex`, `forgecode`, `codebuddy`, `continue`, `costrict`, `crush`, `cursor`, `factory`, `gemini`, `github-copilot`, `iflow`, `junie`, `kilocode`, `kimi`, `kiro`, `opencode`, `pi`, `qoder`, `lingma`, `qwen`, `roocode`, `trae`, `vibe`, `windsurf`

References

• Identified during review of PR feat: add AtomCode command adapter support #1211 (comment: feat: add AtomCode command adapter support #1211 (comment))
• Reported by @hu-qi

[clay-good]

Closing as fixed. docs/cli.md was brought back in sync in the stores rework (#1190, commit a0decbe), including vibe.

Verified exact parity against src/core/config.ts on current main: all 34 available tool IDs match in both directions, nothing missing either way. On the agents question: it is marked available: false in config (internal entry), so its absence from the user-facing list is correct rather than lucky.