feat(install): unify per-platform installers into install.sh / install.ps1

[Lum1104]

Summary

• Replace 7 nearly-identical .<platform>/INSTALL.md files (gemini/codex/opencode/pi/openclaw/antigravity/vscode) with a single install.sh + install.ps1 at the repo root. Skills are enumerated dynamically from understand-anything-plugin/skills/ — the old hardcoded list of 6 was already stale (missing understand-domain and understand-knowledge).
• Single shared checkout at ~/.understand-anything/repo (override via UA_DIR). Antigravity keeps its existing ~/.gemini/antigravity/skills path for backward compatibility; OpenClaw keeps its folder-symlink style. Universal ~/.understand-anything-plugin link unchanged.
• README.md and 6 translated READMEs (READMEs/*.md) replace the per-platform "Fetch and follow instructions from .../<plat>/INSTALL.md" blocks with one curl | bash / iwr | iex one-liner. Compatibility tables updated to show install.sh codex, etc.
• Adds __pycache__/ to .gitignore.

Usage

# Interactive prompt:
curl -fsSL https://raw.githubusercontent.com/Lum1104/Understand-Anything/main/install.sh | bash

# Or pass platform directly:
curl -fsSL https://raw.githubusercontent.com/Lum1104/Understand-Anything/main/install.sh | bash -s codex

# Update / uninstall:
./install.sh --update
./install.sh --uninstall codex

Windows: iwr -useb https://raw.githubusercontent.com/Lum1104/Understand-Anything/main/install.ps1 | iex

Test plan

• bash -n install.sh — syntax check
• Smoke-test against fake checkout with stubbed git, exercising all 7 platforms — verified per-skill symlinks land in ~/.agents/skills/ (gemini/codex/opencode/pi), folder symlinks land in ~/.openclaw/skills/understand-anything and ~/.gemini/antigravity/skills/understand-anything, and per-skill links land in ~/.copilot/skills/ for vscode
• --uninstall <plat> removes the skill links and the universal plugin link, keeps the shared checkout
• --update runs git pull --ff-only on the existing checkout
• --help prints usage
• Unknown platform exits non-zero with supported-list hint
• Prompt mode without a tty fails with a friendly "pass platform as argument" message
• grep -n 'INSTALL.md' README.md READMEs/*.md — empty (no stale links)
• Test on a real Windows machine with install.ps1
• Verify curl | bash works against the live main branch once this PR lands

Notes

• This is purely an installation/docs refactor. No plugin behavior changes, so no version bumps in plugin.json files.
• Existing users who installed via the old per-platform clone path (~/.gemini/understand-anything, etc.) are not affected — their installs keep working until they re-run the new script, which clones into ~/.understand-anything/repo instead.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Understand-Anything/install.ps1

Lines 176 to 177 in 966d607

	if (Test-Path $PluginLink) {
	Remove-Item -Force -Recurse $PluginLink

Guard uninstall from deleting non-junction plugin directory

Cmd-Uninstall removes ~/.understand-anything-plugin whenever it exists, but Cmd-Install explicitly leaves a pre-existing path untouched; if that path is a normal directory (not the junction created by this installer), Remove-Item -Recurse will delete user files. This creates a destructive data-loss path for users who already had a real directory at that location, so uninstall should verify the path is the installer-managed junction/reparse point before deleting it.

---

Understand-Anything/install.sh

Lines 189 to 191 in 966d607

	if [[ ! -d "$REPO_DIR" ]]; then
	printf 'No checkout found at %s — nothing to unlink.\n' "$REPO_DIR"
	exit 0

Continue uninstall even when checkout directory is missing

The uninstall flow exits early when $REPO_DIR is absent, so it skips removing platform links and the universal plugin symlink. If a user deleted or moved the checkout first (or changed UA_DIR), --uninstall leaves stale/broken links behind instead of cleaning up the installation. Uninstall should still remove known link paths from the platform map without requiring the repo checkout to exist.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".