gravity-cli 0.1.0__tar.gz → 0.3.0__tar.gz

{gravity_cli-0.1.0 → gravity_cli-0.3.0}/.env.example

@@ -3,19 +3,20 @@
 # What each variable does: README.md, "Environment variables".
 
 # --- gravity run / schedule / adapt -------------------------------------
-# Your gateway dev token. Required to run an agent. A local gateway prints
-# one at startup, or uses its LOCAL_DEV_TOKEN.
+# Your gateway dev token. Required to run an agent. Issued by the Gravity team;
+# a local gateway prints one at startup, or uses its LOCAL_DEV_TOKEN.
 GRAVITY_DEV_TOKEN=
 
-# The gateway's MCP endpoint. Leave unset for a local gateway on port 8000.
-# GRAVITY_GATEWAY_URL=https://<hosted gateway host>/mcp
+# The gateway's MCP endpoint. Leave unset: the CLI asks Gravity where the gateway is.
+# Set it only for a local gateway.
+# GRAVITY_GATEWAY_URL=http://127.0.0.1:8000/mcp
 
 # The model endpoint. Leave unset: it follows the gateway (<gateway>/v1).
 # GRAVITY_LLM_URL=
 
 # --- push / tools / agents / runs / logs / whoami ------------------------
-# The control plane. Leave unset for a local one at http://localhost:3010.
-# GRAVITY_API_URL=https://<control plane host>
+# The control plane. Leave unset for Gravity's; set it only for a local one.
+# GRAVITY_API_URL=http://localhost:3010
 
 # Development only: the control plane's dev token, instead of `gravity login`.
 # GRAVITY_API_TOKEN=

{gravity_cli-0.1.0 → gravity_cli-0.3.0}/.github/workflows/ci.yml

@@ -58,11 +58,13 @@ jobs:
           GRAVITY_CONFIG_DIR: ${{ runner.temp }}/gravity-config
         run: |
           uv venv "$RUNNER_TEMP/smoke"
-          uv pip install --python "$RUNNER_TEMP/smoke/bin/python" --find-links dist gravity-cli
+          # The wheel files themselves: by name, uv would pick the copy already on PyPI.
+          uv pip install --python "$RUNNER_TEMP/smoke/bin/python" dist/*.whl
           cd "$RUNNER_TEMP"
           "$RUNNER_TEMP/smoke/bin/gravity" --help > /dev/null
           "$RUNNER_TEMP/smoke/bin/gravity" init smoke-agent
           "$RUNNER_TEMP/smoke/bin/gravity" validate smoke-agent
+          "$RUNNER_TEMP/smoke/bin/gravity" guide > /dev/null  # the guide ships inside the wheel
       - uses: actions/upload-artifact@v4
         with:
           name: ci-dist

{gravity_cli-0.1.0 → gravity_cli-0.3.0}/AGENT_STANDARD.md

@@ -94,7 +94,7 @@ that nothing can start (`manual: false` with no schedule) is rejected.
 
 `slots` (optional) declares swappable adapters: `slots.<slot>.adapters.<name>: [tools]`, one file
 per adapter at `src/adapters/<slot>/<name>.py`. A run is granted `permissions.tools` plus only the
-picked adapter's tools; the pick arrives as `state["inputs"][<slot>]`. See `BUILDER_GUIDE.md` §9.
+picked adapter's tools; the pick arrives as `state["inputs"][<slot>]`. See the builder guide (`gravity guide`).
 
 The same schema is validated twice — by `gravity validate` on your machine
 and again by the server on push — because an attacker won't use the CLI.