kylon-cli 0.7.10-next.1401 → 0.7.10

package/README.md

@@ -841,9 +841,6 @@ instead of waiting out inactivity timeouts and heartbeat intervals.
   a readiness probe or assignment. Provider authentication and model selection
   remain in Grok's local configuration.
 - `hermes` — Hermes over ACP, using `hermes-acp` or `hermes acp`.
-- `antigravity` — Antigravity CLI over ACP, through the Antigravity ACP server
-  that `kylon provider install antigravity` installs. See
-  [Antigravity CLI](#antigravity-cli).
 - `openclaw` — OpenClaw CLI using `openclaw agent --message <prompt> --json`.
   A message too large for the command line is delivered as a file via
   `--message-file <path>` instead (requires OpenClaw 2026.6.11 or newer; the
@@ -939,8 +936,7 @@ back to another saved identity.
   or arbitrary error text. Identity and workspace attribution come from server
   authentication, not client fields.
 - **Anonymous** (status (`status`/`auth status`, `gateway status`), `diagnose`,
-  the upgrade and install commands (`upgrade`, `provider update`,
-  `provider install`, `gateway service`)): the
+  the upgrade commands (`upgrade`, `provider update`, `gateway service`)): the
   same URL without a credential, command outcomes only, with an even narrower
   metadata allowlist. The setup commands (`auth login`, `agent link`, `connect`,
   `onboard`) report anonymously only when they fail, with the setup session id
@@ -1294,30 +1290,6 @@ new production CLI build must be published. Service deployment alone leaves
   a fresh CLI-only PR from the current `main`, merge it, and dispatch stable
   on that commit, keeping `main` still until the CLI is published.
 
-- **Run the stable preflight before every stable dispatch.** A stable run
-  needs about an hour and a human approval before it reaches the gates that
-  most often fail, so check them first, read-only:
-
-  ```bash
-  node scripts/ci/cli-stable-preflight.mjs --mac-host p2compat@autodeploy-bj
-  ```
-
-  It takes the current `main` head (or `--sha <main sha>`) and prints one
-  pass/fail row per gate: the merged main PR behind that commit, the newest
-  production deploy and every changed file since it that is not CLI-only, the
-  merged PR's latest `preview-deploy.yml` run (completed, successful, and
-  merged onto `main`'s exact tree), the package version against npm `@latest`,
-  any stable `cli-publish.yml` run still queued or running, the
-  `p2-external-compat` macOS runner (online and idle; reading runners needs repo
-  admin), and, over SSH with `--mac-host`, the harness `active-run` lock. The
-  harness never steals that lock, so a held or stale one fails the row; recover
-  a stale lock through `external-agent-compat-harness.yml` `recovery_run`,
-  never by deleting it. The preflight dispatches, reruns and deletes nothing,
-  and exits non-zero when any row fails. It cannot see qualification failures,
-  Windows host state, or macOS privacy (TCC) denials for the runner service.
-  On the `publish_cli=true` and `release:cli` paths the production row passes
-  only after that Deploy completes; check the other rows before requesting it.
-
 Do not `npm publish` ad hoc: use the stable workflow and its OIDC provenance.
 Pushing a version tag alone does not publish.
 
@@ -1379,37 +1351,6 @@ request `external-agent:full`. Stable CLI publication always runs fresh full
 provider/platform qualification after the service deployment, independently
 of these cheap checks.
 
-### Antigravity CLI
-
-Kylon runs Antigravity CLI through the Antigravity ACP server, a separate
-download that each Kylon CLI release pins and verifies:
-
-1. Install the server with `kylon provider install antigravity` (`--json` for
-   one machine-readable result). It downloads the pinned release, checks its
-   sha256 against the pin and, on macOS and Windows, the executables'
-   signature from Google, and unpacks it into
-   `~/.kylon/providers/antigravity-acp/<version>/`. Run again, it verifies the
-   existing install without downloading. Run it with the installed `kylon`
-   (`~/.kylon/bin/kylon` if it is not on your PATH), not through `npx`: it
-   removes server releases older than the one its own version pins, so a newer
-   copy would remove the one the running service starts. `kylon gateway service repair`
-   installs it as well when an Antigravity CLI agent on this computer has no
-   server, or when Kylon's copy no longer matches what it installed.
-2. Sign in once with `agy`, Antigravity CLI itself, which the server download
-   does not include. If `agy` is missing, `kylon provider install antigravity`
-   prints its installer. The server reuses that sign-in, and a turn it refuses
-   for want of one fails with the instruction to run `agy` once.
-3. Link the agent with the command Kylon gives you,
-   `kylon agent link --url "<link>"`. `--url` is required, and the provider
-   comes from the link: `kylon agent link --url "<link>" --provider antigravity`
-   restates it, and an agent's link refuses any other provider.
-
-The launch is built in: `agent configure` cannot override it. An Antigravity
-CLI agent runs only where the computer's running Kylon CLI reports Antigravity
-CLI support, so a link to a computer whose service still runs an older Kylon
-CLI is refused with `EXTERNAL_AGENT_CLI_PROVIDER_UNSUPPORTED` and leaves the
-link unused. Upgrade with `kylon upgrade`, then run the same setup again.
-
 ### Gemini CLI
 
 Install stable Gemini CLI 0.58.0 or newer with

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.7.10-next.1401",
-  "fingerprint": "9bfe9300ac039c49a0d95dec2c1e5b0547eb6f25cdbc2ad8cafc12e3f62f1523",
-  "source_commit": "169ab20bf5aca2b316aeded0685ff6e658337cd1"
+  "version": "0.7.10",
+  "fingerprint": "55ea4526a571d7bf6bfe5208f7afbc9a906d2bf9c6e0c7bcb9f8dbb2b061e562",
+  "source_commit": "463880e40a8deef3aed33e447509f52710bd021e"
 }