mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-21 07:45:38 +00:00
* feat(skills): install bundled orchestration skills for Antigravity Antigravity CLI (`agy`), App, and IDE do not scan `~/.agents/skills` or `~/.claude/skills` globally; they discover global skills one level deep from `~/.gemini/config/skills/<skill>/SKILL.md`. Gemini CLI already discovers `~/.agents/skills`, so targeting `~/.gemini/config/skills` only (instead of `~/.gemini/skills`) avoids duplicate skill entries in both Gemini CLI and `agy`. Appends `antigravityDir` at root index 3 in skill transactions so any in-flight pre-upgrade transaction manifest retains its existing backup indices, and includes `antigravityDir` in legacy Codex alias checks so symlinked roots are not retired. * fix(skills): unify install roots and keep rollback/updates resilient to unwritable targets - Replace separate per-target fields on SkillTargets with an ordered `installDirs` list plus `codexDir`, deriving status, sync, removal, legacy Codex alias checks, and transaction root indexing from one source while preserving pre-upgrade backup indices 0–2 (`codexDir` at index 2, additional install roots at index 3+). - Skip unreadable `add` entries with no backup during transaction rollback so an ENOTDIR/EACCES parent under `~/.gemini` does not fail rollback and leave a stuck transaction blocking later skills calls. - Ignore `ENOTDIR` in `removeSkill` (a skill cannot exist below a regular file). - Continue syncing remaining skills and install roots in `syncSkills` before throwing the first error so an unwritable `~/.gemini` does not block startup auto-updates from reaching `~/.agents` and `~/.claude`. * fix(skills): finish removing reachable skills during uninstall when one root is unreadable Continue across every target root in `removeSkill` and every managed skill in `uninstallSkills` before throwing the first error (matching `syncSkills`), while still reporting `EACCES` rather than ignoring it. * test(agent): synchronize stale-session retry before checking cleared run Replace the racy `setTimeout(0)` in `agent-manager.test.ts` with a deferred gate on `resumeSession`. Under CI load, `setTimeout(0)` could fire after the immediate retry had already resumed and started its new in-flight run, causing `hasInFlightRun(agent.id)` to read `true`.