gravity-cli 0.11.1__tar.gz → 0.12.0__tar.gz

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/AGENT_STANDARD_V2.md

@@ -16,7 +16,7 @@ that package disagree, the package wins and this document has a bug.
 (`issue.list`) and what it changes (`issue.create`); the consumer picks the
 app — Linear, Jira, Asana — when they set it up. `contract: v1` manifests
 (tool names) are still accepted while the platform moves to v2; their standard is
-AGENT_STANDARD.md. **v2 is a preview:** it runs only against a gateway that serves v2.
+AGENT_STANDARD.md. Gravity runs both.
 
 ## 1. Layout
 
@@ -373,7 +373,8 @@ outputs:                   # what the consumer may ask the result to become
 capability that takes its rendering — markdown: `message.send`,
 `message.create`, `document.create`, `issue.create`, `comment.create`,
 `post.create`, `file.create`; docx and pptx: `file.create`, `message.send`
-(and `presentation.create` for a deck); rows: `row.append`, `file.create`.
+(and `presentation.create` for a deck); rows: `row.append`, `spreadsheet.create`,
+`file.create`; xlsx: `file.create`, `spreadsheet.create` (a new Google Sheet, every table a tab).
 `default` (expected; `gravity validate` warns without it) is where it goes
 unless the consumer picks otherwise: a download, or a destination and its
 app. The consumer can change it, and picks the place (a Slack channel, a

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.5
 Name: gravity-cli
-Version: 0.11.1
+Version: 0.12.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.11.1
+Requires-Dist: gravity-schema==0.12.0
 Requires-Dist: httpx>=0.27.0
 Requires-Dist: keyring>=25.0.0
 Requires-Dist: python-dotenv>=1.0.0
@@ -756,17 +756,18 @@ outputs:                          # extra formats the platform renders and deliv
 
 Unknown fields are rejected rather than ignored, so a typo is reported instead of silently dropped.
 
-### Contract v2 (preview)
+### Contract v2
 
 The CLI also reads `contract: v2` manifests, where an agent names **capabilities** (`message.list`, `issue.create`)
 instead of tools, and the person picks the app when they set it up: Gmail or Outlook, Linear or Jira. What it reads
 goes under `sources`, what it changes under `writes`; code calls `gravity.read("inbox")` and `gravity.act("send", ...)`.
-v2 runs only against a gateway that serves it, and Gravity's hosted gateway runs v1 for now.
+Gravity runs both contracts. A v2 agent runs once a consumer has set it up (their app and place for each source,
+write and output); `gravity init` stays on v1 by default until that setup page is on the web app.
 
 ```bash
 gravity init my-agent --contract v2      # the v2 templates
 gravity capabilities message             # what exists, and which apps serve it
-gravity check message.list --app gmail   # try one on your own account (v2 gateway)
+gravity check message.list --app gmail   # try one on your own account
 gravity run --use inbox=outlook          # pick the app for a local run
 gravity guide --contract v2              # the v2 guide; the rules are in AGENT_STANDARD_V2.md
 ```

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/README.md

@@ -739,17 +739,18 @@ outputs:                          # extra formats the platform renders and deliv
 
 Unknown fields are rejected rather than ignored, so a typo is reported instead of silently dropped.
 
-### Contract v2 (preview)
+### Contract v2
 
 The CLI also reads `contract: v2` manifests, where an agent names **capabilities** (`message.list`, `issue.create`)
 instead of tools, and the person picks the app when they set it up: Gmail or Outlook, Linear or Jira. What it reads
 goes under `sources`, what it changes under `writes`; code calls `gravity.read("inbox")` and `gravity.act("send", ...)`.
-v2 runs only against a gateway that serves it, and Gravity's hosted gateway runs v1 for now.
+Gravity runs both contracts. A v2 agent runs once a consumer has set it up (their app and place for each source,
+write and output); `gravity init` stays on v1 by default until that setup page is on the web app.
 
 ```bash
 gravity init my-agent --contract v2      # the v2 templates
 gravity capabilities message             # what exists, and which apps serve it
-gravity check message.list --app gmail   # try one on your own account (v2 gateway)
+gravity check message.list --app gmail   # try one on your own account
 gravity run --use inbox=outlook          # pick the app for a local run
 gravity guide --contract v2              # the v2 guide; the rules are in AGENT_STANDARD_V2.md
 ```

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/packages/gravity-schema/gravity_schema/manifest_v2.py

@@ -54,8 +54,8 @@ RENDERER_DESTINATIONS: dict[Renderer, tuple[str, ...]] = {
     Renderer.DOCX: ("file.create", "document.create", "message.send"),
     Renderer.PPTX: ("file.create", "presentation.create", "message.send"),
     Renderer.PDF: ("file.create", "message.send"),
-    Renderer.ROWS: ("row.append", "file.create"),
-    Renderer.XLSX: ("file.create",),
+    Renderer.ROWS: ("row.append", "spreadsheet.create", "file.create"),
+    Renderer.XLSX: ("file.create", "spreadsheet.create"),
 }
 
 # A filter on one of these fields takes one of the shape's listed values.

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/packages/gravity-schema/gravity_schema/vocabulary/connectors/googlesheets.yaml

@@ -537,10 +537,19 @@ writes:
       args: {spreadsheet_id: "{target}", ranges: ["{sheet ?? ='Sheet1'}"]}
       check: rows_present
   spreadsheet.create:
+    # draft.tables (optional), each {name, range, values}: an output delivered as a new spreadsheet, every table a tab.
+    # The first fills the tab a new spreadsheet comes with (its range names no tab: "A1", whatever the locale calls
+    # it); each later one gets its own tab first. values: the header line, then the table's lines
     steps:
       - action: GOOGLESHEETS_CREATE_GOOGLE_SHEET1
         args: {title: "{draft.title}"}
         save: {id: "data.response_data.spreadsheetId ?? data.spreadsheetId", link: "data.response_data.spreadsheetUrl ?? data.spreadsheetUrl"}
+      - action: GOOGLESHEETS_ADD_SHEET
+        each: draft.tables|rest
+        args: {spreadsheet_id: "{id}", title: "{item.name}"}
+      - action: GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND
+        each: draft.tables
+        args: {spreadsheetId: "{id}", range: "{item.range}", valueInputOption: RAW, values: "{item.values}"}
     returns: {id: id, title: draft.title, link: link}
   # verified live 2026-10-12
   row.update: &sheet_row_update

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/packages/gravity-schema/gravity_schema/vocabulary/connectors/slack.yaml

@@ -1397,7 +1397,10 @@ writes:
     target: {resource: channel, label: Channel}
     steps:
       - action: SLACK_SEND_MESSAGE
-        args: {channel: "{target}", markdown_text: "{draft.text}", thread_ts: "{draft.thread}"}
+        # a draft with `blocks` (Gravity's digest, pictures and all) posts them, its text only as their fallback:
+        # Slack takes markdown_text or blocks, never both
+        args: {channel: "{target}", markdown_text: "{draft|text_unless_blocks}", blocks: "{draft.blocks}",
+               fallback_text: "{draft|text_if_blocks}", thread_ts: "{draft.thread}"}
         save: {id: "data.ts ?? data.message.ts", channel: "data.channel ?? ={target}"}
     returns: {id: id, channel: channel, text: draft.text}
     read_back:

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/packages/gravity-schema/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "gravity-schema"
-version = "0.11.1"
+version = "0.12.0"
 description = "Gravity agent manifest contract — models, validation, and JSON Schema export"
 readme = "README.md"
 license = "Apache-2.0"

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "gravity-cli"
-version = "0.11.1"
+version = "0.12.0"
 description = "gravity cli — init, run, and push python agents to the Gravity marketplace"
 readme = "README.md"
 license = "Apache-2.0"
 license-files = ["LICENSE", "NOTICE"]
 requires-python = ">=3.12"
 dependencies = [
-    "gravity-schema==0.11.1",  # released in lockstep: always the same version as this package
+    "gravity-schema==0.12.0",  # released in lockstep: always the same version as this package
     "typer>=0.15.0",
     "httpx>=0.27.0",
     "rich>=13.9.0",

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/BUILDER_GUIDE.md

@@ -869,9 +869,8 @@ see, locally or hosted:
 - [ ] `gravity validate` passes and a `gravity run` (or `gravity dev` run) produced the result you expect (§8, §9)
 - [ ] No keys or secrets anywhere; nothing your code needs lives outside `src/` and `tests/`
 
-## 12. Contract v2 (preview)
+## 12. Contract v2
 
-This guide is contract v1, what Gravity runs today. Contract v2 names what an agent reads and changes as
-capabilities (`message.list`, `issue.create`) instead of tools, and the person picks the app at setup. It runs only
-against a gateway that serves v2. Its guide is `gravity guide --contract v2`, and `gravity init my-agent --contract v2`
+This guide is contract v1. Contract v2 names what an agent reads and changes as capabilities (`message.list`,
+`issue.create`) instead of tools, and the person picks the app at setup. Gravity runs both. Its guide is `gravity guide --contract v2`, and `gravity init my-agent --contract v2`
 starts one.

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/BUILDER_GUIDE_V2.md

@@ -1,8 +1,8 @@
-# Build an agent for Gravity: contract v2 (preview)
+# Build an agent for Gravity: contract v2
 
-> **Preview.** Contract v2 runs only against a gateway that serves it; Gravity's hosted gateway runs contract v1
-> for now, and `gravity guide` (without `--contract v2`) is v1's guide. Start a v2 agent with
-> `gravity init my-agent --contract v2`. Everything else here is how v2 works once your gateway serves it.
+> Gravity runs contract v1 and v2; `gravity guide` (without `--contract v2`) is v1's guide. Start a v2 agent with
+> `gravity init my-agent --contract v2`. A v2 agent runs once its consumer has set it up: their app and place for
+> each source, write and output.
 
 Everything you need to build, test and submit a Gravity agent, in the order you'll do it. What you can use on
 which app is in `gravity capabilities`; the exact rules are in `AGENT_STANDARD_V2.md` in the gravity-cli repo.

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/CHANGELOG.md

@@ -4,6 +4,13 @@ Shown by `gravity update` and `gravity changelog`, and after an update. Each rel
 then one bullet per change: `- new|improved|fixed: A one-line headline. The detail behind it.`
 Write it for a builder, not for a maintainer. `tests/test_changelog.py` fails a release that has no entry.
 
+## 0.12.0 - 2026-10-31
+
+- new: Contract v2 is no longer a preview: Gravity's hosted platform runs v1 and v2 agents side by side. A v2 agent runs once its consumer has set it up (their app and place for each source, write and output). `gravity init` still starts v1 unless you pass `--contract v2`.
+- new: A v2 output can go to a new Google Sheet: `spreadsheet.create` takes a `rows` or `xlsx` output and makes a spreadsheet with a tab for every table in your corpus.
+- improved: A v2 output sent to Slack posts the same digest Gravity shows (headings, tables, pictures as Slack blocks), not a plain-text copy.
+- improved: The v2 minimal template shows how to declare an output and return the corpus it's rendered from; an output without a corpus fails at delivery.
+
 ## 0.11.1 - 2026-10-31
 
 - fixed: `gravity connect sheets` (and the other v1 app names) works again on a gateway that serves both contracts. 0.9.0 through 0.11.0 took the v2 path on any gateway that served v2, where v1's names aren't apps; now only a v2-only gateway gets it.

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/commands/guide.py

@@ -10,13 +10,13 @@ from gravity_schema import CONTRACT_V1, CONTRACT_V2
 from .. import Problem, ui
 
 GUIDE = Path(__file__).parent.parent / "BUILDER_GUIDE.md"  # ships inside the package
-GUIDE_V2 = GUIDE.with_name("BUILDER_GUIDE_V2.md")  # contract v2, a preview
+GUIDE_V2 = GUIDE.with_name("BUILDER_GUIDE_V2.md")  # contract v2
 
 
 def guide_command(
     save: bool = typer.Option(False, "--save", help="Write the guide to the current folder instead of showing it"),
     contract: Annotated[str, typer.Option(
-        "--contract", metavar="v1|v2", help="v1 (tools, what the platform runs today) or v2 (capabilities, a preview)",
+        "--contract", metavar="v1|v2", help="v1 (tools) or v2 (capabilities, the app picked at setup)",
     )] = CONTRACT_V1,
 ):
     """How to build a good agent: the builder guide."""

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/commands/init.py

@@ -48,8 +48,7 @@ def init_command(
     # Annotated, so a call from Python (the welcome's first agent, tests) gets the plain default.
     contract: Annotated[str, typer.Option(
         "--contract", metavar="v1|v2",
-        help="v1 names the tools the agent calls; v2 names capabilities and the user picks the app (preview: "
-             "needs a gateway that runs v2)",
+        help="v1 names the tools the agent calls; v2 names capabilities and the user picks the app at setup",
     )] = CONTRACT_V1,
 ):
     """Scaffold a working agent: manifest, pinned deps and a src/agent.py that runs."""
@@ -99,6 +98,5 @@ def init_command(
     workspace.refresh(dest)
     install = "uv venv && uv pip install -r requirements.txt"
     if contract == CONTRACT_V2:
-        ui.note("Contract v2 is a preview: it runs only against a gateway that serves v2.")
         install += f" && {SDK_INSTALL}"
     ui.next_steps(f"cd {name}", install, 'gravity run --input query="hello"')

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/docs/Gravity.agent.md

@@ -1155,11 +1155,10 @@ your folder: read them as examples of structure, and follow the method.
 - [ ] `gravity validate` passes; a `gravity run` or `gravity dev` run produced the result you expect
 - [ ] No keys or secrets in any file; nothing the code needs lives outside `src/` and `tests/`
 
-## 17. Contract v2 (preview): capabilities instead of tools
+## 17. Contract v2: capabilities instead of tools
 
-Everything above is contract v1, which is what Gravity's hosted platform runs. Contract v2 is a preview: build on it
-only when the person says their gateway serves v2 (`gravity connect` and `gravity check` work against it). The CLI
-reads both, picked by the manifest's `contract`; `gravity guide --contract v2` is the full v2 guide and
+Everything above is contract v1. Gravity's hosted platform runs v1 and v2; build on v2 when the person asks for it
+(`gravity init --contract v2`), else stay on v1. The CLI reads both, picked by the manifest's `contract`; `gravity guide --contract v2` is the full v2 guide and
 `AGENT_STANDARD_V2.md` its exact rules.
 
 In v2 the manifest never names an app or a tool. It names **capabilities**, `<shape>.<verb>` (`message.list`,

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/templates/v2/minimal/manifest.yaml

@@ -38,6 +38,15 @@ models:
 #     label: "Where follow-ups go"
 # approvals:
 #   required_for: [issue.create]      # each call waits for the consumer's yes
+#
+# What the result can become, delivered by Gravity after the run (the agent declares no write for it). An agent with
+# outputs returns a corpus in its final state (see src/agent.py); without one the delivery fails.
+# outputs:
+#   summary:
+#     renderer: markdown              # markdown | docx | pptx | pdf | rows | xlsx
+#     label: "Summary"
+#     destinations: [download, message.send]
+#     default: {destination: message.send, app: gmail}
 
 resources:
   memory_mb: 512                # a request — the platform clamps, never guarantees

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/src/gravity_cli/templates/v2/minimal/src/agent.py

@@ -13,6 +13,7 @@ from langgraph.prebuilt import create_react_agent
 class State(TypedDict):
     inputs: dict
     result: str
+    corpus: dict  # what the manifest's outputs are rendered from (unused without outputs)
 
 
 # ← manifest.runtime.entrypoint. An async factory the runner calls per run; building the
@@ -41,7 +42,10 @@ async def graph():
     async def run_agent(state: State):
         query = state["inputs"].get("query", "")
         result = await react.ainvoke({"messages": [{"role": "user", "content": query}]})
-        return {"result": result["messages"][-1].content}
+        text = result["messages"][-1].content
+        # With `outputs` in the manifest, return the corpus they're rendered from as well:
+        #   return {**gravity.Corpus(title="Summary", summary=text).to_state(), "result": text}
+        return {"result": text}
 
     workflow = StateGraph(State)
     workflow.add_node("agent", run_agent)

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/tests/test_v2_cli.py

@@ -23,10 +23,11 @@ def test_templates_are_v2_and_their_example_is_valid_when_uncommented(tmp_path,
     (tmp_path / "manifest.yaml").write_text(text, encoding="utf-8")
     assert load_manifest(tmp_path / "manifest.yaml").contract == "v2"
     # the commented example, uncommented, is a valid manifest too: it names real capabilities
-    example = re.sub(r"^# (sources:|writes:|approvals:|  .*)$", r"\1", text, flags=re.MULTILINE)
+    example = re.sub(r"^# (sources:|writes:|approvals:|outputs:|  .*)$", r"\1", text, flags=re.MULTILINE)
     (tmp_path / "manifest.yaml").write_text(example, encoding="utf-8")
     m = load_manifest(tmp_path / "manifest.yaml")
-    assert m.capabilities == {"issue.list", "issue.create"} and m.approvals.required_for == ["issue.create"]
+    output = {"message.send"} if template == "minimal" else set()  # the one that shows an output, sent by mail
+    assert m.capabilities == {"issue.list", "issue.create", *output} and m.approvals.required_for == ["issue.create"]
 
 
 STARTER = Path(__file__).resolve().parents[1] / "starter-v2"  # the contract v2 example; starter/ is v1

{gravity_cli-0.11.1 → gravity_cli-0.12.0}/uv.lock

@@ -164,7 +164,7 @@ wheels = [
 
 [[package]]
 name = "gravity-cli"
-version = "0.11.1"
+version = "0.12.0"
 source = { editable = "." }
 dependencies = [
     { name = "gravity-schema" },
@@ -201,7 +201,7 @@ dev = [
 
 [[package]]
 name = "gravity-schema"
-version = "0.11.1"
+version = "0.12.0"
 source = { editable = "packages/gravity-schema" }
 dependencies = [
     { name = "pydantic" },