feat: support CodeBuddy as an installation target

[XuQianJin-Stars]

• install.sh / install.ps1: add 'codebuddy' platform, install skills to ~/.codebuddy/skills/ via symlinks (parity with claude/cursor/etc.)
• README.md / README_zh.md: document CodeBuddy as a supported client
• pnpm-workspace.yaml / pnpm-lock.yaml: minor housekeeping
• .gitignore: ignore .idea/

Verified locally: 8 understand-* skills are recognized and dispatchable inside CodeBuddy after running ./install.sh codebuddy.

Summary

Adds CodeBuddy as a first-class installation target for Understand-Anything, on par with Claude / Cursor / Trae / Cline / KIMI CLI / etc.

After this PR, users can run a single command to wire all 8 understand-* skills into CodeBuddy:
bash ./install.sh codebuddy # macOS / Linux .\install.ps1 codebuddy # Windows

The installer creates per-skill symlinks under ~/.codebuddy/skills/, mirroring the layout CodeBuddy already uses for its built-in skills, so they show up natively in the slash-command picker.

What changed

File	Change
install.sh	Register a new platform row: codebuddy | ~/.codebuddy/skills | per-skill
install.ps1	Same registration on the PowerShell side (Windows parity)
README.md	Add codebuddy to the one-liner help text, the supported-<platform> list, and the platform compatibility table
.gitignore	Ignore .idea/ (IntelliJ project metadata)
understand-anything-plugin/pnpm-workspace.yaml understand-anything-plugin/pnpm-lock.yaml	Minor workspace/lockfile housekeeping picked up while validating the install

Note: The auto-generated commit message also mentions README_zh.md, but the i18n README was not modified in this PR — happy to follow up in a separate PR if maintainers want zh-CN parity.

Why per-skill instead of folder?

CodeBuddy (like Trae) discovers skills by enumerating direct children of ~/.codebuddy/skills/, where each child is itself a skill directory containing SKILL.md. The per-skill style in install.sh already produces exactly that shape, so no new install style had to be invented.

Linked issue(s)

N/A — net-new platform support, no tracking issue.

How I tested this

Manual end-to-end smoke test on macOS 14 / zsh / CodeBuddy desktop:

• ./install.sh codebuddy succeeded; ~/.codebuddy/skills/ now contains 8 symlinks pointing into ~/.understand-anything/repo/understand-anything-plugin/skills/understand-*
• ls -la ~/.codebuddy/skills/ shows: understand, understand-chat, understand-dashboard, understand-diff, understand-domain, understand-explain, understand-knowledge, understand-onboard
• Restarted CodeBuddy → all 8 skills are listed in the skill picker and are dispatchable
• ./install.sh --uninstall codebuddy cleanly removes only our symlinks, leaves user's other skills (e.g. godogen, ppt, harness-engineering) intact
• ./install.sh --update re-syncs the repo and the symlinks remain valid
• pnpm lint
• pnpm --filter @understand-anything/core test
• pnpm test
• Manual smoke test (described above)

The pnpm test suites were not run because this PR touches only shell installers + docs; no TypeScript/runtime code paths are affected.

Versioning

• Version bumped in all five manifests, OR
• N/A — installer + docs only, no published package code changed