paseo-agy-acp v2.0.0.1

Why v2.0

Admission Controller v2 addresses the concurrency failure pattern reported in the official Antigravity CLI tracker at google-antigravity/antigravity-cli#573: agy -p can hang under sustained neighboring CLI concurrency even when solo and lighter runs succeed. This is a bounded Paseo-side mitigation; no Google endorsement is claimed.

Highlights

• Coordinates all local Paseo agents through a durable account-wide queue with three shared active seats, one serialized start permit, a two-second minimum start interval, FIFO eligibility, and agent fairness.
• Recovers capacity through durable leases, process identity, owner-death handling, startup recovery, and a runtime reaper without guessing that a live process is dead.
• Adds soft drain from three seats to one, provider/model-scoped capacity cooldown, atomic queue timeout/cancel settlement, and typed terminal outcomes.
• Fences the one-shot business write so ambiguous dispatch becomes durable recovery state and is never silently replayed.
• Hardens native conversation binding, provider terminal failure handling, Claude effort selection, and secure 0700 Admission state preflight.
• Expands both English and Chinese README documentation with the queue model, operational advantages, conservative policy controls, and validation boundary.

Verification

• npm run validate: 58 test files passed; 626 tests passed, 2 skipped; architecture and secret scans passed.
• Fresh 2.0.0.1 tarball installation passed package version, public-entry import, CLI bin, native PTY, ACP initialize, and secure state-mode checks.
• Production-candidate acceptance on 127.0.0.1:6767 passed real Gemini and Claude turns, stable 3 active + 1 queued FIFO handoff, and an additional six-request mixed-provider pressure run.
• Nine additional agy 1.1.13 Claude probes completed through the production queue; final ledger state was zero leases and zero retained payloads, SQLite integrity passed, and no OOM or candidate process remained.

Provider capacity evidence boundary

The final agy 1.1.13 pressure window did not emit a live capacity 503. Historical native agy 1.1.12 logs establish the trusted 503 UNAVAILABLE carrier, while deterministic tests verify the current classifier and provider/model cooldown boundary. Unknown or untrusted failures continue to fail closed without creating a capacity cooldown.

Artifact

• paseo-agy-acp-2.0.0.1.tgz
• SHA-256: 0131ee7497f60c749a87709a1daeda398cbb92a9972b51d19e3f2e2d1cecaa43