* feat: add OpenClaw platform support
Add OpenClaw as an install target so the skill can be installed with
`uipro init --ai openclaw` and removed via `uipro uninstall`.
OpenClaw discovers AgentSkills-format skills from `.agents/skills` in the
agent workspace and from `~/.agents/skills` (personal library on the default
state dir), so the platform config reuses the `.agents` layout already used
by the universal/codex targets with its own display name, detection entry,
and docs.
- new platform config src/ui-ux-pro-max/templates/platforms/openclaw.json
(synced to cli/assets via sync:assets)
- register 'openclaw' in AIType, AI_TYPES, AI_FOLDERS, AI_TO_PLATFORM
- detect the shared .agents workspace directory and describe the platform
- keep the .agents-family suggestion on codex when all four .agents
consumers are detected (length 2-3 -> 2-4)
- cover openclaw in the dry-run, template-script-paths, and
agent-query-contract e2e specs
- document OpenClaw in README and cli/README
* chore: bump version to 2.15.0 in skill metadata files
Aligns skill.json, marketplace.json, and plugin.json with the latest
v2.15.0 release; main was still at 2.13.0. CLI package version stays on
its own npm release track.
* fix: cover OpenClaw in offline validator and detection regression
- bump scripts/validate-agent-guide.py PLATFORM_COUNT 21 -> 23 (main
already had 22 configs with a stale count of 21; OpenClaw widens the
gap to 23, so update the gate and keep it meaningful)
- add e2e regression: a sole .agents directory detects all four
consumers (antigravity, codex, universal, openclaw) and still
suggests codex rather than all
* feat: add Amazon Q Developer platform support
Add Amazon Q Developer as an install target so the skill can be installed
with `uipro init --ai amazonq` and removed via `uipro uninstall`.
Amazon Q loads every Markdown file under .amazonq/rules/ (recursively) as
always-on chat context, so only the rendered rule file goes there
(.amazonq/rules/ui-ux-pro-max.md). Data, scripts and the bundled
sub-skills go to .amazonq/skills/ via dataPath, the same split copilot
uses, so their reference docs are not pulled into every chat.
- new platform config src/ui-ux-pro-max/templates/platforms/amazonq.json
(synced to cli/assets via sync:assets)
- register 'amazonq' in AIType, AI_TYPES, AI_FOLDERS, AI_TO_PLATFORM
- detect .amazonq workspace directories and describe the platform
- cover amazonq in the dry-run and template-script-paths e2e specs
- document Amazon Q Developer in README and cli/README
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* docs: note that Amazon Q only auto-loads the rule file
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(cli): add --global flag to update command and support --ai universal (#435, #436)
* fix(cli): support dist package.json resolution in update command
* fix CLI asset sync
* fix(cli): normalize line endings in asset sync/check
check:assets hashed raw bytes, so identical CSV/JSON/py content with
CRLF vs LF (git autocrlf on checkout) was reported as stale drift,
blocking the release guard on Windows/mixed checkouts.
- fileHash now normalizes CRLF->LF before hashing, so check:assets
compares content, not line endings.
- sync:assets writes LF-normalized copies instead of a raw byte copy,
so re-syncing is deterministic across platforms.
All synced assets are text (csv/json/md/py); no binaries affected.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* ci: enforce CLI asset sync on PRs
Adds a Check asset sync workflow that runs `npm run check:assets` on any
PR touching src/ui-ux-pro-max/** or cli/assets/**, so the bundled CLI
assets can't silently drift from the source of truth.
The check uses only node builtins (no install step) and normalizes
line endings before hashing, so it hard-fails on real content drift
without the CRLF/LF soft-fail hack other approaches needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
* fix: V-001 security vulnerability
Automated security fix generated by Orbis Security AI
* feat(cli): add optional GitHub token support with proper UX and docs
- Rename env var from GITHUB_TOKEN to UI_PRO_MAX_GITHUB_TOKEN (primary),
with GITHUB_TOKEN as fallback — avoids silently attaching CI workflow
credentials that GitHub Actions injects automatically
- Add whitespace trim guard to prevent malformed Authorization headers
- Add getGitHubTokenGuidance() helper exported from github.ts so rate-limit
errors and spinner warnings tell users exactly how to fix the problem
- Thread optional token param through fetchReleases, getLatestRelease,
downloadRelease signatures
- Add --token flag to init, versions, update commands (Commander.js wiring)
- Update rate-limit catch in tryGitHubInstall to show token guidance
- Document token options (flag, env var, fallback) in cli/README.md with
CI warning about GITHUB_TOKEN scope
Supersedes the narrower env-only approach in PR #294 and incorporates the
safeguards requested during review of closed PR #186.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add GitHubRateLimitError and GitHubDownloadError for better error handling
- Detect rate limits (403 with remaining=0, 429)
- Try downloading from GitHub releases first
- Fall back to bundled assets on network error, rate limit, or download failure
- Add --offline flag to skip GitHub download
- Use GitHub auto-generated archive URL as fallback when no ZIP asset exists
- Update CLI to v1.9.0
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>