paseo-agy-acp 2.2.0

package/CHANGELOG.md

@@ -0,0 +1,296 @@
+# Changelog
+
+All notable changes to `paseo-agy-acp` are recorded here.
+
+## 2.2.0 - 2026-08-29
+
+### Changed
+
+- npm-publishable semver: `2.2.0` is the same product as GitHub tag
+  `v2.2.0.0`. Install with `npx -y paseo-agy-acp@2.2.0`. The package `bin`
+  includes a `paseo-agy-acp` alias so `npx` can infer the CLI. npm still does
+  **not** ship Google's `.par`.
+
+## 2.2.0.0 - 2026-08-29
+
+### Added
+
+- Local **opt-in** compatibility on the **official** Antigravity ACP kernel so
+  entitled Claude 4.6 and GPT-OSS 120B sessions can complete through Paseo.
+  Gemini-family models stay the stock official path until an operator prepares
+  and points `PASEO_AGY_ACP_OFFICIAL_BIN` at the stable wrapper
+  (`agy-acp-kernel-compat-active`).
+- `agy-acp-prepare-official-kernel-compat` lifecycle (`prepare` / `verify` /
+  `activate` / `status` / `rollback` / `cleanup`), RC01 pin checks, and
+  `paseo_model_compat.py` request transforms (tool schema, tool-call ids,
+  GPT-OSS generation config; Gemini/unknown identity).
+- Isolated acceptance harness coverage (catalog, text, tools, warm resume,
+  capability-gated load/media/timeout) and an operator
+  [runbook](docs/operations/official-kernel-compat-runbook.md).
+- Sanitized maintainer-host production evidence
+  ([P7](docs/operations/official-kernel-compat-p7-production-evidence.md)):
+  catalog 14, live text/tools; official RC01 active cancel not confirmed;
+  real 503/quota not induced.
+
+### Unchanged
+
+- Execution kernel remains official `agy_acp_server`. npm still does **not**
+  ship Google's proprietary `.par` or runfiles. Admission defaults stay
+  **8 / 8 / 2s** (tested default, not a product ceiling). No daemon restart
+  is required for new provider processes to read an updated launcher.
+
+## 2.1.0.0 - 2026-08-23
+
+### Changed
+
+- Switched ACP execution from the PTY/SQLite scraper to the official Google
+  `agy-acp` NDJSON server (Registry id `antigravity-acp`). The product binary
+  stays `agy-acp` and runs as a thin proxy: it injects Paseo daemon
+  `appendSystemPrompt`, maps session modes, rewrites MCP `http` servers to
+  `sse`, overlays product identity, and fences Admission around the official
+  `session/prompt` write.
+- Official live modes are `default`, `auto_edit`, and `yolo`. Legacy
+  `accept-edits` maps to `auto_edit`, `dangerously-skip-permissions` maps to
+  `yolo`, and `plan` maps to `default` because official has no plan mode.
+- Blank official `end_turn` results with no visible assistant output become a
+  JSON-RPC error instead of an empty successful turn.
+- **Deleted** the scraper kernel. `PASEO_AGY_ACP_KERNEL=legacy` and
+  `--legacy-kernel` fail closed. The product source stays **Apache-2.0**; the
+  official kernel binary is proprietary and is spawned, not redistributed.
+  Set `PASEO_AGY_ACP_OFFICIAL_BIN` to override the pinned official wrapper.
+  Official Admission state is isolated under `$AGY_ACP_STATE_DIR/official-kernel`.
+- Isolated canary on `127.0.0.1:6768` proved product `2.1.0.0` + official
+  kernel + daemon context (`ISOLATED_OFFICIAL_KERNEL_CANARY_OK`). Production
+  `127.0.0.1:6767` was not mutated by that canary.
+- Default Admission is **8 shared seats / 8 concurrent starts / 2s start
+  interval**, from production testing (including a 10-agent Antigravity
+  dispatch that did not reproduce the scraper hang). The queue stays enabled
+  so Paseo → Antigravity delegation stays steadier under burst. Env integers
+  **≥ 1** can raise seats/starts for concurrency experiments; this repo does
+  **not** publish a product maximum. Admission schema v3 rebuilds
+  `policy_state` so SQLite no longer carries a leftover upper CHECK from the
+  old 1–8 ledger. Isolated 6-way yolo stress on `127.0.0.1:6768` also did not
+  reproduce the scraper hang; official ACP is still not proven unlimited.
+  Optional `AGY_ACP_ADMISSION_MAX_ACTIVE_TURNS=3` and
+  `AGY_ACP_ADMISSION_MAX_CONCURRENT_STARTS=1` remain a tighter fence, not the
+  default.
+
+### Unchanged
+
+- Production Paseo daemon `127.0.0.1:6767` was **not restarted**. After the
+  8/8 Admission raise, `/home/tiezbro/.local/bin/agy-acp` was retargeted to
+  `/home/tiezbro/.local/opt/paseo-agy-acp-2.1.0.0-20260823T112457Z/bin/agy-acp-production`
+  with a fresh ledger at
+  `/home/tiezbro/.local/state/paseo-agy-acp/production-official-8` so the
+  durable 3+1 fingerprint cannot fail-close the new policy. The default Paseo
+  `antigravity` provider still runs that symlink. `antigravity-official-canary`
+  is disabled so production is not split. Idle Antigravity agents pick up 8/8
+  on the next spawn; live Cursor/Claude agents were left running.
+- Stage 2 Scheme pointers and the 2.0.0.0 closeout facts below are unchanged.
+
+## 2.0.0.2 - 2026-08-19
+
+### Changed
+
+- Recorded authorized live Antigravity CLI observation for the trusted-503
+  physical-source gate. Current `agy 1.1.14` produced Gemini successes and a
+  Claude individual-quota failure on the stream-json `result.error` carrier,
+  with no `httpStatus`, `code`, `reason`, or HTTP 503.
+- Corrected the earlier 2.0.0.1 verification claim that historical native
+  `1.1.12` logs establish the trusted `503 UNAVAILABLE` carrier. Those logs
+  remain unverified prose; this release does not close Scheme §4.5 and does
+  not change the fail-closed classifier.
+- Runtime Admission and Connector code is unchanged from `2.0.0.1`. This
+  patch ships evidence and documentation only.
+
+### Verification
+
+- Live observation receipts: `docs/design/receipts/S3-T08/observation-1.txt`
+  and `observation-2.txt`, plus raw captures. `LIVE_503_CAPTURED=no`.
+- Repository validation is recorded in the release commit. One existing
+  symlink cleanup in `tests/edit-reconcile.test.ts` now unlinks the
+  directory symlink so current Node `fs.rmSync` does not treat it as a
+  directory.
+
+## 2.0.0.1 - 2026-08-17
+
+### Changed
+
+- Promoted `2.0.0.1` after separating the earlier isolated happy-path canary
+  from formal production acceptance and completing both.
+- Documented why Admission Controller v2 exists: we first encountered
+  concurrency failures while running multiple Paseo agents against the same
+  Antigravity account, then surveyed the wider community to confirm the
+  behavior was not isolated. Antigravity CLI issue
+  [#573](https://github.com/google-antigravity/antigravity-cli/issues/573),
+  which reports `agy -p` hanging under three or more longer-running neighboring
+  CLI processes, is public corroborating evidence rather than the original
+  cause. The durable account-wide queue, three shared active seats, one paced
+  start permit, reaping, recovery, soft drain, and typed settlement are the
+  bounded Paseo-side mitigation; no Google endorsement is claimed.
+- Bound fresh Linux interactive streams to the conversation database opened by
+  the exact Antigravity child process, preventing concurrent agents from
+  attaching to another process's newly-created conversation.
+- Made final persisted model-provider errors fail both interactive and print
+  turns immediately, instead of waiting for the turn timeout or completing an
+  empty successful turn. ACP admission still owns the typed terminal mapping.
+- Accepted Paseo's `low`, `medium`, and `high` reasoning selections for Claude
+  models whose Antigravity catalog has one base model rather than separate
+  effort variants. The native default remains available without `--effort`.
+- Made every enabled runtime opener claim or assert the shared durable policy
+  before startup recovery. A connector with a mismatched policy now fails
+  closed instead of running with an empty `policy_state` singleton.
+- Added the packaged `agy-acp-prepare-state` preflight so installation and
+  isolated acceptance create account state directories with exact mode `0700`
+  and reject existing permissive directories without silently changing them.
+
+### Verification
+
+- The state-directory preflight passed focused tests for secure creation,
+  fail-closed handling of an existing `0775` directory, and published-manifest
+  exposure. The complete repository validation passed with 58 test files,
+  626 passed tests, 2 skipped tests, architecture PASS, and secret scan PASS.
+- A fresh `2.0.0.1` tarball installed into a new prefix and exposed the packaged
+  preflight binary. That binary created an absent state directory as `0700`;
+  its `admission.key` and `runtime.sqlite` were `0600`. A clean isolated Paseo
+  daemon on `127.0.0.1:6768` then completed a real Antigravity turn with marker
+  `STATE_DIR_FIX_R11_OK`; the durable request was `completed`, with zero leases
+  and zero retained payloads afterward.
+- The complete fault matrix passed for concurrent admission, queueing and
+  pressure, crash/restart recovery, reaping and queued-owner death, soft drain,
+  ambiguous dispatch, queue timeout, auth/permission modes, typed terminal
+  outcomes, and trusted Provider capacity classification.
+- Production-candidate acceptance on `127.0.0.1:6767` passed with real Gemini
+  and Claude turns, stable `3 active + 1 queued` FIFO handoff, an additional
+  six-request mixed-provider pressure run, zero final leases, zero retained
+  payloads, SQLite integrity PASS, and no OOM or candidate-process residue.
+- Nine additional `agy 1.1.13` Claude pressure probes completed through the
+  production queue. The Provider did not emit a live capacity `503` in that
+  window; historical native `1.1.12` logs establish the trusted
+  `503 UNAVAILABLE` carrier while deterministic tests verify the current
+  classifier and cooldown boundary.
+
+## 2.0.0.0 - 2026-08-16
+
+### Changed
+
+- Closed the final Stage 3 v2 migration for `shared-admission-queue` schema v2:
+  `turn_requests.agent_id`, `policy_state` with `policy_fingerprint`,
+  `queued_owner_instances`, lease suspect metadata, and the v1 to v2 migration
+  ledger are now the local database contract.
+- Made durable policy the single runtime authority. Connectors claim or assert
+  the same `policy_state`, and soft drain moves `3 -> soft_draining_to_1 ->
+  steady(max_active_turns=1)` without killing active turns.
+- Closed owner, recovery, and runtime reaper behavior. Queued owner death is
+  bounded, `recovery_required` remains non-replayable, and suspect leases are
+  released only after process evidence proves the local turn is gone.
+- Wired enabled production dispatch through durable dispatch intent before the
+  prompt write. Ambiguous or blocked writes become durable terminal states.
+- Added the enabled-mode auth gate for v1/v2 login/logout, preserved disabled
+  legacy auth, restored the interactive permission chain, and kept official ACP
+  session history replay in the connector.
+- Mapped `queue_timeout`, `provider_capacity`/provider failure, cancellation,
+  and `recovery_required` through typed terminal behavior instead of treating
+  known failures as successful `end_turn`.
+- Made the packaged ACP entry importable from its built public layout and kept
+  provider discovery available before Paseo assigns `PASEO_AGENT_ID` while
+  still rejecting business prompts until Admission composition is complete.
+- Corrected prompt-free argv ordering and made cold-start interactive PTY
+  dispatch wait for Antigravity's authentication/model redraws to settle before
+  the single durable fenced prompt write.
+
+### Added
+
+- Added Stage 3 closeout documentation that points README.md and
+  README.zh-CN.md at the confirmed Scheme and accepted Stage 2 artifacts.
+- Added a clause-by-clause historical disposition for the legacy admission
+  design file so it cannot act as a second authority.
+- Added `tests/closeout-docs-contract.test.ts` to keep the bilingual
+  documentation, CHANGELOG, and historical design disposition aligned.
+
+### Removed
+
+- Removed the old documentation authority claim from the legacy design. It is
+  retained only as historical input with dispositions grounded in the Scheme
+  and accepted Stage 2 artifacts.
+
+### Verification
+
+- Final validation passed with `npm test -- --maxWorkers=1`: 56 test files,
+  611 passed tests, and 2 skipped tests. Architecture boundaries, secret scan,
+  GitNexus detect-changes, and `git diff --check` also passed.
+- Stage 3 documentation receipts remain in `docs/design/receipts/S3-T21/`.
+- A local `2.0.0.0` tarball passed fresh-prefix installation, built public
+  entry import, CLI EOF, and native PTY smoke tests.
+- The installed tarball ran a real Antigravity `gemini-3.1-pro` Admission turn
+  on an isolated `127.0.0.1:6768` daemon. The exact canary response was
+  `STAGE4_ADMISSION_CANARY_OK`; the durable request completed and released its
+  lease. Production `127.0.0.1:6767` was not switched or mutated.
+
+## 1.0.0.4 - 2026-08-07
+
+### Fixed
+
+- Suppress the connector's posthoc completed-edit approval bridge when the
+  active Antigravity session mode is `dangerously-skip-permissions`. This keeps
+  Paseo unattended runs fully unattended after Antigravity has already applied
+  an edit through `agy --dangerously-skip-permissions`.
+- Parse tab-separated `agy models` output as `modelId<TAB>display name` and pass
+  the exact provider-native model id to Antigravity. This prevents display
+  labels such as `Gemini 3.6 Flash (High)` from being folded into the model id
+  and avoids sending unsupported `--effort` flags for exact variant ids.
+
+### Verification
+
+- `npx vitest run tests/cli.test.ts --testNamePattern "posthoc edit review|dangerous permission bypass"` — passes.
+- `npx vitest run tests/acp-server.test.ts tests/cli.test.ts --testNamePattern "tab-separated|exact tab-list|modern stable model slugs|passes --effort|parseAgyModels|dangerous permission bypass"` — passes.
+
+## 1.0.0.3 - 2026-08-07
+
+### Changed
+
+- Added bilingual README navigation and refreshed the provider feature table.
+
+## 1.0.0.2 - 2026-08-07
+
+### Added
+
+- Expose Antigravity CLI's native unattended permission bypass as ACP mode id
+  `dangerously-skip-permissions`.
+- Map that mode directly to the official `agy --dangerously-skip-permissions`
+  parameter. The adapter does not introduce a custom `full-access` alias for
+  Antigravity.
+- Support `/mode dangerously-skip-permissions` and common operator aliases such
+  as `/mode yolo`.
+
+### Changed
+
+- When `agy-acp` itself is launched with `--dangerously-skip-permissions`, the
+  initial ACP mode is now reported as `dangerously-skip-permissions`.
+- Switching away from `dangerously-skip-permissions` through ACP mode/config
+  selection disables the bypass for later turns in that session.
+
+### Verification
+
+- `env -u PASEO_AGENT_ID -u PASEO_AGENT_CWD -u PASEO_HOME npm test` — 383 passed, 1 skipped.
+- `env -u PASEO_AGENT_ID -u PASEO_AGENT_CWD -u PASEO_HOME npm run build` — passes.
+
+## 1.0.0.1 - 2026-08-06
+
+### Fixed
+
+- Treat `PASEO_HOME` as optional when reading Paseo daemon context. The bridge
+  falls back to `~/.paseo` when `PASEO_AGENT_ID` is present and `PASEO_HOME` is
+  unset or empty.
+
+## 1.0.0.0 - 2026-08-06
+
+### Added
+
+- Initial Paseo-focused Antigravity ACP adapter release derived from upstream
+  `shindgew/agy-acp`.
+- Paseo daemon append-system-prompt bridge.
+- Permission denial authority fixes.
+- Stronger turn-completion detection.
+- Foreground command task-state repair.
+- Whole-file edit revert newline tolerance.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Shindge Wong
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.