gravity-cli 0.5.6__tar.gz → 0.7.0__tar.gz

{gravity_cli-0.5.6 → gravity_cli-0.7.0}/AGENT_STANDARD.md

@@ -25,7 +25,7 @@ my-agent/
 ```
 
 **Only these are bundled.** `gravity build` zips exactly `manifest.yaml`,
-`requirements.txt`, `requirements.lock`, and the contents of `src/` and
+`requirements.txt`, `requirements.lock`, `tools_needed.yaml` (if present), and the contents of `src/` and
 `tests/` (minus `__pycache__`). Anything else — `.venv/`, `build/`, notebooks,
 a `data/` folder — is not shipped, and code that reads it will fail at runtime.
 
@@ -41,14 +41,14 @@ runtime:
   framework: langgraph            # only value accepted
   python: "3.12"                  # the platform runs 3.12; validate refuses any other
   entrypoint: src/agent.py:graph  # file:object — see §3
-  timeout_seconds: 300            # 10–900
+  timeout_seconds: 300            # 10–28800
 
 dependencies:
   lockfile: requirements.lock     # leave as-is
 
 inputs:                           # becomes the consumer's form; arrives as state["inputs"]
   - name: query                   # the key in state["inputs"]
-    type: text                    # text | textarea | number | boolean | static-dropdown | email | url | date | file
+    type: text                    # text | textarea | number | boolean | static-dropdown | email | url | date | secret | file
     label: "What should I do?"    # what the consumer sees
     required: true
     # options: [a, b]             # static-dropdown only
@@ -69,6 +69,7 @@ triggers:                         # optional — what starts a run
   # schedule:
   #   cron: "0 9 * * 1"           # 5 fields: digits, * / , - only (no @daily, no MON); every 5 minutes at the fastest; one day field at most; Asia/Kolkata
   #   consumer_can_change: true
+  # webhook: [github.push]        # run on a GitHub push; the only source today
 
 approvals:                        # optional — tools that pause the run for the consumer's yes
   required_for: []                # each must also be in permissions.tools
@@ -127,9 +128,10 @@ runner is too old, not your agent.
 
 **State.** The runtime invokes `graph.astream({"inputs": {...}}, stream_mode="updates")`
 — the keyword is passed only when your `astream` accepts it, so a hand-rolled
-object with a plain `astream(state)` works too (accepting `**kwargs` is the
-safe habit). The dict is the
-dict is the consumer's form answers keyed by `inputs[].name`. Your state
+object with a plain `astream(state)` works in `gravity run` (accepting `**kwargs`
+is the safe habit). The hosted platform needs a compiled LangGraph graph: it
+injects its own checkpointer and store into it. The dict is the
+consumer's form answers keyed by `inputs[].name`. Your state
 therefore needs:
 
 ```python
@@ -259,7 +261,7 @@ leave their record in `.gravity/runs/`; one run is live per folder).
 
 | Stage | Catches |
 |---|---|
-| `gravity validate` / `build` (local) | manifest schema · entrypoint file + object exist (static) · `requirements.txt` present · lockfile compiles for aarch64 · undeclared network imports (warning) |
+| `gravity validate` / `build` (local) | manifest schema · entrypoint file + object exist (static) · `requirements.txt` present · lockfile compiles for aarch64 · undeclared tool names in source (an error for a write tool, a warning for a read tool) |
 | `gravity push` (server) | manifest re-validated with the same rules · `permissions.tools` all exist in the catalog · version not already published |
 | deploy | every pin in the lock installs on ARM64 |
 | first run | module imports · `graph` resolves to something with `astream()` · state has `inputs` · final state has `result` |

gravity_cli-0.5.6/README.md → gravity_cli-0.7.0/PKG-INFO

@@ -1,3 +1,20 @@
+Metadata-Version: 2.5
+Name: gravity-cli
+Version: 0.7.0
+Summary: gravity cli — init, run, and push python agents to the Gravity marketplace
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.12
+Requires-Dist: gravity-schema==0.7.0
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: keyring>=25.0.0
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: rich>=13.9.0
+Requires-Dist: typer>=0.15.0
+Requires-Dist: uv>=0.8.0
+Description-Content-Type: text/markdown
+
 <h1 align="center">Gravity CLI</h1>
 
 <p align="center">
@@ -75,7 +92,7 @@ gravity init my-agent
 
 ## Declare it once, enforced on every call
 
-There is no SDK to learn. Your agent is plain LangGraph that reads three environment variables. Everything Gravity enforces comes from `manifest.yaml`:
+There is almost no SDK to learn. Your agent is plain LangGraph that reads three environment variables; the one Gravity package, `gravity`, is preinstalled on the platform and is only needed to load approval-gated tools. Everything Gravity enforces comes from `manifest.yaml`:
 
 | You declare in `manifest.yaml` | What Gravity does with it |
 |---|---|
@@ -91,11 +108,11 @@ The same rules apply on your laptop and when the agent runs hosted, because both
 
 | | |
 |---|---|
-| Commands | 18, grouped into build an agent, publish, your agents, account and help |
+| Commands | 21, grouped into build an agent, publish, your agents, account, help and Gravity CLI |
 | Starter templates | 4: `minimal`, `structured`, `deepagent`, `chat` |
-| Tool catalog | 1,402 tools across 15 apps (Gmail, Slack, Linear, GitHub, Calendar, Drive, Sheets, LinkedIn, Jira, Confluence, Notion, WhatsApp, web search, and two built-ins), 28 of them curated |
-| Test suite | 466 tests (214 CLI, 252 schema), run on Ubuntu and Windows with Python 3.12 and 3.13 |
-| Runtime contract | 3 environment variables, no Gravity import in your code |
+| Tool catalog | 1,405 tools across 12 apps (Gmail, Slack, Linear, GitHub, Calendar, Drive, Sheets, LinkedIn, Jira, Confluence, Notion, WhatsApp), plus web search, Firecrawl and two built-ins; 31 of them curated |
+| Test suite | 543 tests (285 CLI, 258 schema), run on Ubuntu and Windows with Python 3.12 and 3.13 |
+| Runtime contract | 3 environment variables; an optional `import gravity` only for approval-gated tools |
 
 ## Five things to know before you start
 
@@ -194,6 +211,9 @@ Run `gravity help` for this list in the terminal, and add `-h` to any command fo
 | | [`gravity connect`](#gravity-connect) | Connect an account your agents act on (Gmail, Slack...) |
 | **Help** | [`gravity guide`](#gravity-guide) | Read the builder guide: how to build a good agent |
 | | [`gravity help`](#gravity-help) | Show the list of commands |
+| **Gravity CLI** | [`gravity docs`](#gravity-docs) | Write `Gravity.agent.md` for the coding agent in this folder |
+| | [`gravity update`](#gravity-update) | Update to the latest release and see what is new |
+| | [`gravity changelog`](#gravity-changelog) | What changed in each release |
 
 `gravity --api-url URL <command>` saves a different control-plane address to `~/.gravity/config.json`; it must start with `http://` or `https://`. The flag applies to the command it is given with; on later commands a `GRAVITY_API_URL` in `~/.gravity/.env` or the shell still wins over `config.json`, and the CLI says so when that is the case. `gravity --version` (or `-V`) prints the installed version. Wherever a command takes `[path]`, it is the agent's folder and defaults to the current one.
 
@@ -412,7 +432,7 @@ gravity logs <run_id>
 
 Browse the tool catalog: the names you can put under `permissions.tools`, with what each one does. It is the gateway's own list, so it shows exactly what a run can call, and it needs no sign-in.
 
-About 25 tools are curated, such as `gmail.read` and `web.search`. The other ~1,100 are imported from the same apps and unreviewed: any imported tool that changes something must also be under `approvals.required_for`, and `gravity validate` checks that.
+31 tools are curated, such as `gmail.read` and `web.search`. The other ~1,370 are imported from the same apps and unreviewed: any imported tool that changes something must also be under `approvals.required_for`, and `gravity validate` checks that.
 
 ```
 gravity tools [search]
@@ -485,6 +505,46 @@ gravity guide --save
 gravity guide | less
 ```
 
+### `gravity docs`
+
+Write or refresh the two files a coding agent needs to build for Gravity in this folder: `Gravity.agent.md` (how Gravity runs agents, the manifest, every tool this release knows, the output formats, the rules that fail a load) and `problem-to-agent.md` (the method for turning a problem statement into an agent that holds up).
+
+```
+gravity docs [--force]
+```
+
+| Option | Description |
+|---|---|
+| `--force` | Replace the files even where you edited them, or where a file Gravity did not write has the same name |
+
+You rarely need this. Every command writes the two files into the folder it runs in if they are missing (never into your home folder or a drive root; `gravity init` writes them into the new agent), and rewrites them when a newer release changes them. The first line of a file Gravity wrote names the release and a hash of the text after it: if you edit the file the hash no longer matches and Gravity leaves it alone. Your own `agent.md`, `AGENTS.md` and `CLAUDE.md` are never touched. Point your coding agent at `Gravity.agent.md` from them if it does not look there by itself. Set `GRAVITY_AGENT_DOCS=0` to stop the automatic writes.
+
+### `gravity update`
+
+Check PyPI for a newer release, install it, and show what is new.
+
+```
+gravity update [--check]
+```
+
+| Option | Description |
+|---|---|
+| `--check` | Only say whether a newer release exists |
+
+You do not have to run it: once every six hours a command looks for a newer release, and when there is one it says `Update available 0.6.0 → 0.6.1`, updates, and runs your command again as the new version, which lists what changed. It upgrades the way you installed it (`uv tool` or `pipx`); a copy installed any other way, or from a source checkout, is told the command to run and left alone. Nothing here can stop a command: a failed update is one warning and the command runs on the version you have. Set `GRAVITY_AUTO_UPDATE=0` to turn the check and the install off; CI never updates.
+
+### `gravity changelog`
+
+What changed in each release, written for builders.
+
+```
+gravity changelog [--all]
+```
+
+| Option | Description |
+|---|---|
+| `--all` | Every release, not only the one you are on |
+
 ### `gravity help`
 
 Show the list of commands. The same as `gravity -h`.
@@ -540,6 +600,9 @@ Set `GRAVITY_API_URL` and `GRAVITY_GATEWAY_URL` only to work against services yo
 | `GRAVITY_API_URL` | The control plane's address | `https://agents.dev.gravity.fast` |
 | `GRAVITY_API_TOKEN` | A control-plane dev token, used instead of `gravity login`. For development only. | none |
 | `GRAVITY_CONFIG_DIR` | Moves `~/.gravity` elsewhere. Useful for tests and CI. | `~/.gravity` |
+| `GRAVITY_AUTO_UPDATE` | When `0`, commands neither check for a newer release nor install one. Always off when `CI` is set. | `1` |
+| `GRAVITY_AGENT_DOCS` | When `0`, commands do not write `Gravity.agent.md` and `problem-to-agent.md` into the folder they run in. `gravity docs` still does. | `1` |
+| `GRAVITY_UPDATE_URL` | Where the latest version is read from, a JSON document with `info.version`. For tests and mirrors. | PyPI |
 | `GRAVITY_UNATTENDED` | When `1`, calls that need approval are rejected without asking. `gravity schedule` sets it for you. | unset |
 
 ### What your agent receives
@@ -775,6 +838,7 @@ Real tools act on a connected account. Connect one with `gravity-gateway connect
 
 ## What's new
 
+- **0.6.0** Gravity CLI keeps itself up to date and says what changed (`gravity update`, `gravity changelog`). `Gravity.agent.md` and `problem-to-agent.md` appear in the folder you work in, for your coding agent (`gravity docs`). `gravity` on its own shows your version, the agent in the folder, whether you are signed in, and any update. The notes shown after an update are `src/gravity_cli/CHANGELOG.md`.
 - **0.5.5** `manifest.yaml` takes an optional `display:` hint for how a run's result shows: `view` (document, report, table, chart, code or files), `field` (the result key to show) and `chart` (`type: line` or `bar`, `x`, and up to three `y` fields). It is a hint, never a rule: an unknown view or key is ignored, so it never fails a push. 0.5.4 and earlier refuse a manifest that has it.
 - **0.5.4** `gravity agents` shows each agent's review: a REVIEW column (not submitted, submitted, approved, rejected), and under "From the Gravity team" the reviewer's notes and what to do next. An agent the Gravity team turned off shows as `off` with the reason. UPDATED reads "3 min ago" instead of a timestamp, and status and review are coloured. Also, from a full audit of every command: `gravity --version`. Clear messages instead of tracebacks for: a proxy or sign-in page answering instead of Gravity, a refused `GRAVITY_API_TOKEN` or `GRAVITY_DEV_TOKEN`, an expired sign-in code, a non-UTF-8 manifest, an out-of-range `--port`, a missing agent folder, a malformed session file. `gravity validate` now refuses what the build would refuse: a `graph` that is not an async factory, `os.environ` or `asyncio.run` at import, relative imports, unquoted `python: 3.12`, schedules faster than every 5 minutes or with both day fields, out-of-range cron fields; it accepts a re-exported `graph`. `gravity agents` shows the review status and failure reasons; `gravity runs` never shortens an id; `gravity logs` never wraps. `gravity push` refuses a bundle over 30 MB or a manifest over 12 KB before uploading, and says why when a failed version is re-pushed. `gravity build` ships `tools_needed.yaml`, leaves dotfiles out, and refuses to build without `requirements.lock`. `gravity adapt` leaves the folder untouched when a model call fails. `gravity schedule` checks inputs before the first tick and runs on Asia/Kolkata like the hosted schedules. `gravity run` deletes `.gravity/payload.json` after the run, warns when no `.venv` is present, and keeps a plain agent's `result`. `gravity connect <app>` refuses on the shared test account instead of attaching your account to it. The builder guide and agent standard describe the real flow (init, validate, run or dev, build, push, review on /app).
 - **0.5.3** `gravity dev` opens a local dashboard for your agent: a form from your manifest, a live timeline, approvals, the result and run history; runs from `gravity run` in the same folder show up in it live, and the other way round. WhatsApp joins the catalog (51 tools; 1,402 across 15 apps including the curated and built-in ones). Agents can return generated images: put them in a corpus section's `images` and they land in the Word, PowerPoint and Markdown outputs. The agent standard now shows how to generate images and embeddings through the gateway. `NEEDS_RECONNECT` on the shared test account tells you to ask Gravity, not to connect your own account.
@@ -858,6 +922,8 @@ uv run python -m gravity_schema.gen_catalog --root <platform repo>/code-first
 | Document | What it covers |
 |---|---|
 | [Builder guide](src/gravity_cli/BUILDER_GUIDE.md) | How to build a good agent, start to finish, with a complete example. Also `gravity guide` |
+| [`Gravity.agent.md`](src/gravity_cli/docs/Gravity.agent.md) | The guide `gravity docs` writes for coding agents; its tool list is filled in from the catalog of the release that writes it |
+| [`problem-to-agent.md`](src/gravity_cli/docs/problem-to-agent.md) | The method for turning a problem statement into an agent that holds up |
 | [Agent standard](AGENT_STANDARD.md) | The exact rules an agent must follow |
 | [Templates](TEMPLATES.md) | The four templates and when to pick each |
 | [`manifest.schema.json`](packages/gravity-schema/schema/manifest.schema.json) | The manifest as a machine-readable JSON Schema |

gravity_cli-0.5.6/PKG-INFO → gravity_cli-0.7.0/README.md

@@ -1,20 +1,3 @@
-Metadata-Version: 2.5
-Name: gravity-cli
-Version: 0.5.6
-Summary: gravity cli — init, run, and push python agents to the Gravity marketplace
-License-Expression: Apache-2.0
-License-File: LICENSE
-License-File: NOTICE
-Requires-Python: >=3.12
-Requires-Dist: gravity-schema==0.5.6
-Requires-Dist: httpx>=0.27.0
-Requires-Dist: keyring>=25.0.0
-Requires-Dist: python-dotenv>=1.0.0
-Requires-Dist: rich>=13.9.0
-Requires-Dist: typer>=0.15.0
-Requires-Dist: uv>=0.8.0
-Description-Content-Type: text/markdown
-
 <h1 align="center">Gravity CLI</h1>
 
 <p align="center">
@@ -92,7 +75,7 @@ gravity init my-agent
 
 ## Declare it once, enforced on every call
 
-There is no SDK to learn. Your agent is plain LangGraph that reads three environment variables. Everything Gravity enforces comes from `manifest.yaml`:
+There is almost no SDK to learn. Your agent is plain LangGraph that reads three environment variables; the one Gravity package, `gravity`, is preinstalled on the platform and is only needed to load approval-gated tools. Everything Gravity enforces comes from `manifest.yaml`:
 
 | You declare in `manifest.yaml` | What Gravity does with it |
 |---|---|
@@ -108,11 +91,11 @@ The same rules apply on your laptop and when the agent runs hosted, because both
 
 | | |
 |---|---|
-| Commands | 18, grouped into build an agent, publish, your agents, account and help |
+| Commands | 21, grouped into build an agent, publish, your agents, account, help and Gravity CLI |
 | Starter templates | 4: `minimal`, `structured`, `deepagent`, `chat` |
-| Tool catalog | 1,402 tools across 15 apps (Gmail, Slack, Linear, GitHub, Calendar, Drive, Sheets, LinkedIn, Jira, Confluence, Notion, WhatsApp, web search, and two built-ins), 28 of them curated |
-| Test suite | 466 tests (214 CLI, 252 schema), run on Ubuntu and Windows with Python 3.12 and 3.13 |
-| Runtime contract | 3 environment variables, no Gravity import in your code |
+| Tool catalog | 1,405 tools across 12 apps (Gmail, Slack, Linear, GitHub, Calendar, Drive, Sheets, LinkedIn, Jira, Confluence, Notion, WhatsApp), plus web search, Firecrawl and two built-ins; 31 of them curated |
+| Test suite | 543 tests (285 CLI, 258 schema), run on Ubuntu and Windows with Python 3.12 and 3.13 |
+| Runtime contract | 3 environment variables; an optional `import gravity` only for approval-gated tools |
 
 ## Five things to know before you start
 
@@ -211,6 +194,9 @@ Run `gravity help` for this list in the terminal, and add `-h` to any command fo
 | | [`gravity connect`](#gravity-connect) | Connect an account your agents act on (Gmail, Slack...) |
 | **Help** | [`gravity guide`](#gravity-guide) | Read the builder guide: how to build a good agent |
 | | [`gravity help`](#gravity-help) | Show the list of commands |
+| **Gravity CLI** | [`gravity docs`](#gravity-docs) | Write `Gravity.agent.md` for the coding agent in this folder |
+| | [`gravity update`](#gravity-update) | Update to the latest release and see what is new |
+| | [`gravity changelog`](#gravity-changelog) | What changed in each release |
 
 `gravity --api-url URL <command>` saves a different control-plane address to `~/.gravity/config.json`; it must start with `http://` or `https://`. The flag applies to the command it is given with; on later commands a `GRAVITY_API_URL` in `~/.gravity/.env` or the shell still wins over `config.json`, and the CLI says so when that is the case. `gravity --version` (or `-V`) prints the installed version. Wherever a command takes `[path]`, it is the agent's folder and defaults to the current one.
 
@@ -429,7 +415,7 @@ gravity logs <run_id>
 
 Browse the tool catalog: the names you can put under `permissions.tools`, with what each one does. It is the gateway's own list, so it shows exactly what a run can call, and it needs no sign-in.
 
-About 25 tools are curated, such as `gmail.read` and `web.search`. The other ~1,100 are imported from the same apps and unreviewed: any imported tool that changes something must also be under `approvals.required_for`, and `gravity validate` checks that.
+31 tools are curated, such as `gmail.read` and `web.search`. The other ~1,370 are imported from the same apps and unreviewed: any imported tool that changes something must also be under `approvals.required_for`, and `gravity validate` checks that.
 
 ```
 gravity tools [search]
@@ -502,6 +488,46 @@ gravity guide --save
 gravity guide | less
 ```
 
+### `gravity docs`
+
+Write or refresh the two files a coding agent needs to build for Gravity in this folder: `Gravity.agent.md` (how Gravity runs agents, the manifest, every tool this release knows, the output formats, the rules that fail a load) and `problem-to-agent.md` (the method for turning a problem statement into an agent that holds up).
+
+```
+gravity docs [--force]
+```
+
+| Option | Description |
+|---|---|
+| `--force` | Replace the files even where you edited them, or where a file Gravity did not write has the same name |
+
+You rarely need this. Every command writes the two files into the folder it runs in if they are missing (never into your home folder or a drive root; `gravity init` writes them into the new agent), and rewrites them when a newer release changes them. The first line of a file Gravity wrote names the release and a hash of the text after it: if you edit the file the hash no longer matches and Gravity leaves it alone. Your own `agent.md`, `AGENTS.md` and `CLAUDE.md` are never touched. Point your coding agent at `Gravity.agent.md` from them if it does not look there by itself. Set `GRAVITY_AGENT_DOCS=0` to stop the automatic writes.
+
+### `gravity update`
+
+Check PyPI for a newer release, install it, and show what is new.
+
+```
+gravity update [--check]
+```
+
+| Option | Description |
+|---|---|
+| `--check` | Only say whether a newer release exists |
+
+You do not have to run it: once every six hours a command looks for a newer release, and when there is one it says `Update available 0.6.0 → 0.6.1`, updates, and runs your command again as the new version, which lists what changed. It upgrades the way you installed it (`uv tool` or `pipx`); a copy installed any other way, or from a source checkout, is told the command to run and left alone. Nothing here can stop a command: a failed update is one warning and the command runs on the version you have. Set `GRAVITY_AUTO_UPDATE=0` to turn the check and the install off; CI never updates.
+
+### `gravity changelog`
+
+What changed in each release, written for builders.
+
+```
+gravity changelog [--all]
+```
+
+| Option | Description |
+|---|---|
+| `--all` | Every release, not only the one you are on |
+
 ### `gravity help`
 
 Show the list of commands. The same as `gravity -h`.
@@ -557,6 +583,9 @@ Set `GRAVITY_API_URL` and `GRAVITY_GATEWAY_URL` only to work against services yo
 | `GRAVITY_API_URL` | The control plane's address | `https://agents.dev.gravity.fast` |
 | `GRAVITY_API_TOKEN` | A control-plane dev token, used instead of `gravity login`. For development only. | none |
 | `GRAVITY_CONFIG_DIR` | Moves `~/.gravity` elsewhere. Useful for tests and CI. | `~/.gravity` |
+| `GRAVITY_AUTO_UPDATE` | When `0`, commands neither check for a newer release nor install one. Always off when `CI` is set. | `1` |
+| `GRAVITY_AGENT_DOCS` | When `0`, commands do not write `Gravity.agent.md` and `problem-to-agent.md` into the folder they run in. `gravity docs` still does. | `1` |
+| `GRAVITY_UPDATE_URL` | Where the latest version is read from, a JSON document with `info.version`. For tests and mirrors. | PyPI |
 | `GRAVITY_UNATTENDED` | When `1`, calls that need approval are rejected without asking. `gravity schedule` sets it for you. | unset |
 
 ### What your agent receives
@@ -792,6 +821,7 @@ Real tools act on a connected account. Connect one with `gravity-gateway connect
 
 ## What's new
 
+- **0.6.0** Gravity CLI keeps itself up to date and says what changed (`gravity update`, `gravity changelog`). `Gravity.agent.md` and `problem-to-agent.md` appear in the folder you work in, for your coding agent (`gravity docs`). `gravity` on its own shows your version, the agent in the folder, whether you are signed in, and any update. The notes shown after an update are `src/gravity_cli/CHANGELOG.md`.
 - **0.5.5** `manifest.yaml` takes an optional `display:` hint for how a run's result shows: `view` (document, report, table, chart, code or files), `field` (the result key to show) and `chart` (`type: line` or `bar`, `x`, and up to three `y` fields). It is a hint, never a rule: an unknown view or key is ignored, so it never fails a push. 0.5.4 and earlier refuse a manifest that has it.
 - **0.5.4** `gravity agents` shows each agent's review: a REVIEW column (not submitted, submitted, approved, rejected), and under "From the Gravity team" the reviewer's notes and what to do next. An agent the Gravity team turned off shows as `off` with the reason. UPDATED reads "3 min ago" instead of a timestamp, and status and review are coloured. Also, from a full audit of every command: `gravity --version`. Clear messages instead of tracebacks for: a proxy or sign-in page answering instead of Gravity, a refused `GRAVITY_API_TOKEN` or `GRAVITY_DEV_TOKEN`, an expired sign-in code, a non-UTF-8 manifest, an out-of-range `--port`, a missing agent folder, a malformed session file. `gravity validate` now refuses what the build would refuse: a `graph` that is not an async factory, `os.environ` or `asyncio.run` at import, relative imports, unquoted `python: 3.12`, schedules faster than every 5 minutes or with both day fields, out-of-range cron fields; it accepts a re-exported `graph`. `gravity agents` shows the review status and failure reasons; `gravity runs` never shortens an id; `gravity logs` never wraps. `gravity push` refuses a bundle over 30 MB or a manifest over 12 KB before uploading, and says why when a failed version is re-pushed. `gravity build` ships `tools_needed.yaml`, leaves dotfiles out, and refuses to build without `requirements.lock`. `gravity adapt` leaves the folder untouched when a model call fails. `gravity schedule` checks inputs before the first tick and runs on Asia/Kolkata like the hosted schedules. `gravity run` deletes `.gravity/payload.json` after the run, warns when no `.venv` is present, and keeps a plain agent's `result`. `gravity connect <app>` refuses on the shared test account instead of attaching your account to it. The builder guide and agent standard describe the real flow (init, validate, run or dev, build, push, review on /app).
 - **0.5.3** `gravity dev` opens a local dashboard for your agent: a form from your manifest, a live timeline, approvals, the result and run history; runs from `gravity run` in the same folder show up in it live, and the other way round. WhatsApp joins the catalog (51 tools; 1,402 across 15 apps including the curated and built-in ones). Agents can return generated images: put them in a corpus section's `images` and they land in the Word, PowerPoint and Markdown outputs. The agent standard now shows how to generate images and embeddings through the gateway. `NEEDS_RECONNECT` on the shared test account tells you to ask Gravity, not to connect your own account.
@@ -875,6 +905,8 @@ uv run python -m gravity_schema.gen_catalog --root <platform repo>/code-first
 | Document | What it covers |
 |---|---|
 | [Builder guide](src/gravity_cli/BUILDER_GUIDE.md) | How to build a good agent, start to finish, with a complete example. Also `gravity guide` |
+| [`Gravity.agent.md`](src/gravity_cli/docs/Gravity.agent.md) | The guide `gravity docs` writes for coding agents; its tool list is filled in from the catalog of the release that writes it |
+| [`problem-to-agent.md`](src/gravity_cli/docs/problem-to-agent.md) | The method for turning a problem statement into an agent that holds up |
 | [Agent standard](AGENT_STANDARD.md) | The exact rules an agent must follow |
 | [Templates](TEMPLATES.md) | The four templates and when to pick each |
 | [`manifest.schema.json`](packages/gravity-schema/schema/manifest.schema.json) | The manifest as a machine-readable JSON Schema |

{gravity_cli-0.5.6 → gravity_cli-0.7.0}/RELEASING.md

@@ -35,6 +35,8 @@ Three places must carry the same number:
 | `pyproject.toml` | `"gravity-schema==X.Y.Z"` under `dependencies` |
 | `packages/gravity-schema/pyproject.toml` | `version = "X.Y.Z"` |
 
+Add the release to `src/gravity_cli/CHANGELOG.md`: a `## X.Y.Z - date` heading and one `- new|improved|fixed: Headline. Detail.` line per change a builder would care about. It is what `gravity update` shows after an update, and `tests/test_changelog.py` fails a version that has no entry. Set the date to the day you tag.
+
 Then refresh the lockfile:
 
 ```bash
@@ -116,6 +118,8 @@ gh run rerun <run-id> --failed
 
 ## Rules
 
+- **A release reaches every installed CLI within about six hours.** Each command checks PyPI for a newer version and updates itself (`src/gravity_cli/updater.py`), so a bad release is out of your hands quickly: ship the fix as the next version, and yank on PyPI only if it is harmful (a yanked release is no longer offered). Verify step 6 before you walk away.
+
 - No copies of the source in other repositories. Pin the PyPI version in your requirements instead.
 - No PyPI API tokens. The trusted publisher configured for this repository is the only credential. If you hold a token for either package, say so and it gets revoked.
 - Every change is a pull request, however small. Review turnaround is same day.

{gravity_cli-0.5.6 → gravity_cli-0.7.0}/TEMPLATES.md

@@ -169,5 +169,5 @@ src/agent.py        exports `graph`
 .gitignore          .venv and caches. requirements.lock is NOT ignored: it ships.
 ```
 
-Note: templates declare `python: "3.13"`; the AgentCore base image is 3.12.
+Note: templates declare `python: "3.12"`, the version the platform runs.
 Set `runtime.python: "3.12"` in the manifest before `gravity push`.

{gravity_cli-0.5.6 → gravity_cli-0.7.0}/packages/gravity-schema/gravity_schema/__init__.py

@@ -22,13 +22,19 @@ from .errors import (
 )
 from .export import manifest_json_schema
 from .manifest import (
+    ActionSpec,
     ApprovalsSpec,
+    ChooseOneSpec,
+    CollectionSpec,
     DependenciesSpec,
     InputSpec,
     InputType,
     Manifest,
+    MemoryScope,
+    MemorySpec,
     ModelsSpec,
     ModelTier,
+    OfferAs,
     PermissionsSpec,
     ResourcesSpec,
     RuntimeSpec,
@@ -36,6 +42,7 @@ from .manifest import (
     StateSpec,
     TriggersSpec,
 )
+from .rules import apply_rules, chosen_actions, problems, visible_inputs
 from .source_scan import is_agent_source, undeclared_write_tools
 from .validation import (
     check_imported_write_approvals,
@@ -70,6 +77,17 @@ __all__ = [  # noqa: RUF022 - grouped by concern, not alphabetical
     "ScheduleSpec",
     "ApprovalsSpec",
     "StateSpec",
+    "MemorySpec",
+    "MemoryScope",
+    "CollectionSpec",
+    "ChooseOneSpec",
+    "ActionSpec",
+    "OfferAs",
+    # input rules
+    "visible_inputs",
+    "apply_rules",
+    "problems",
+    "chosen_actions",
     # validation
     "validate_manifest",
     "load_manifest_text",

{gravity_cli-0.5.6 → gravity_cli-0.7.0}/packages/gravity-schema/gravity_schema/contract.py

@@ -67,6 +67,22 @@ MAX_MEMORY_MB: Final[int] = 4096
 MIN_STATE_KB: Final[int] = 1
 MAX_STATE_KB: Final[int] = 256
 
+# Memory collections (manifest `memory.collections`): keyed records, per user or per thread.
+MAX_COLLECTIONS: Final[int] = 20
+MAX_ITEM_KB: Final[int] = 64
+DEFAULT_ITEM_KB: Final[int] = 16
+MAX_ITEMS_PER_COLLECTION: Final[int] = 10_000
+MAX_KEEP_DAYS: Final[int] = 730
+DEFAULT_KEEP_DAYS: Final[int] = 30
+# Across every collection and the notebook, one user's memory of one agent.
+MAX_MEMORY_BYTES_PER_USER: Final[int] = 25 * 1024 * 1024
+MAX_MEMORY_WRITES_PER_RUN: Final[int] = 5_000
+# memory.previous(): the last finished run's result, passed whole up to this size.
+MAX_PREVIOUS_KB: Final[int] = 256
+
+# Declared actions (manifest `actions`).
+MAX_ACTIONS: Final[int] = 20
+
 
 # Generous bounds, so a pathological manifest can't tie up the validator.
 

{gravity_cli-0.5.6 → gravity_cli-0.7.0}/packages/gravity-schema/gravity_schema/errors.py

@@ -36,6 +36,9 @@ class ErrorCode(str, Enum):
     INVALID_STATE = "INVALID_STATE"
     INVALID_KIND = "INVALID_KIND"
     INVALID_OUTPUT = "INVALID_OUTPUT"
+    INVALID_CONDITION = "INVALID_CONDITION"
+    INVALID_ACTION = "INVALID_ACTION"
+    INVALID_MEMORY = "INVALID_MEMORY"
     LOCKFILE_MISMATCH = "LOCKFILE_MISMATCH"
     MISSING_FIELD = "MISSING_FIELD"
     UNKNOWN_FIELD = "UNKNOWN_FIELD"