tangram-app-sdk 0.1.0rc2__tar.gz

tangram_app_sdk-0.1.0rc2/.gitignore

@@ -0,0 +1,7 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+dist/
+.venv/
+.preview/

tangram_app_sdk-0.1.0rc2/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

tangram_app_sdk-0.1.0rc2/PKG-INFO

@@ -0,0 +1,410 @@
+Metadata-Version: 2.5
+Name: tangram-app-sdk
+Version: 0.1.0rc2
+Summary: Python SDK for building, validating, and running Tangram apps and connectors locally
+Project-URL: Homepage, https://github.com/tangram-data/tangram-app-manifest
+Project-URL: Documentation, https://github.com/tangram-data/tangram-app-manifest/tree/main/python-sdk/docs
+Project-URL: Source, https://github.com/tangram-data/tangram-app-manifest
+Project-URL: Issues, https://github.com/tangram-data/tangram-app-manifest/issues
+Author: Tangram
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent,connector,manifest,sdk,tangram
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Requires-Dist: pyyaml<7,>=6.0.2
+Description-Content-Type: text/markdown
+
+# Tangram App SDK for Python
+
+The SDK documentation starts at [docs/sdk-guide.md](docs/sdk-guide.md). This
+README provides the shorter repository overview and common examples.
+
+This directory contains the first authoring and standalone runtime SDK layer for the
+[Tangram App Manifest](../spec/README.md). It evaluates a real manifest package
+with Pkl, decodes the result into Python dataclasses mirroring the public Scala
+domain model, and separately loads compiled Tangram Capability Graphs for the
+transport-independent action host.
+
+The SDK is deliberately small. Its only Python dependency is PyYAML for
+OpenAPI documents authored as YAML. It currently provides:
+
+- immutable, validated capability-graph models;
+- `Application`, `AppResourceTypeDefinition`, `AppResourceTypeVersion`,
+  `ResourceTypeAction`, `OpenApiMapping`, extractor, role, and configuration
+  dataclasses corresponding to the Scala manifest-facing classes;
+- a restricted Python-driven `pkl eval` integration and standard package-entry
+  point loader;
+- canonical action and binding lookup;
+- JSON Schema input validation for the graph's supported schema subset;
+- a read-only-by-default local development policy;
+- one invocation path shared by future CLI, MCP, and HTTP adapters;
+- pluggable execution drivers; and
+- metadata-only audit events that do not record arguments or results.
+- a `TangramApp` facade for package/graph discovery and local binding;
+- a versioned JSON command surface through `python -m tangram_app` and
+  `tangram-app`; and
+- integrity-locked portable agent-skill generation for shell-capable agents;
+- a `TangramProject` facade for AI-assisted source validation and compilation;
+- canonical `[tool.tangram.backend]` parsing and host-native FastAPI source
+  supervision; and
+- a cached per-project Python 3.12 environment and staged backend `tangram`
+  module;
+- a loopback per-project PostgreSQL provider with persistent `.preview/pgdata`
+  and checksum-ledgered migrations; and
+- managed React component dependencies, esbuild compilation, and a loopback UI
+  host with a browser `window.tangram` bridge; and
+- source-mode local calls that verify the live `/openapi.json` contract before
+  exposing any action.
+
+It now compiles validated App and Connector mappings into a capability graph
+and executes those bindings through a bounded HTTP driver, but does **not** yet
+expose MCP. Agent skills use the Python command surface instead; protocol
+adapters remain optional. The Tangram validator/compiler remains the publishing conformance authority;
+Python's Pkl loader provides direct access to the manifest model and its draft
+compiler derives the versioned runtime graph from the same evaluated values.
+The graph wire contract is published as
+[`schema/capability-graph.schema.json`](schema/capability-graph.schema.json).
+
+## Loading a manifest package
+
+Install a compatible [Pkl CLI](https://pkl-lang.org/) and load the directory
+that contains `manifests/`:
+
+```python
+from tangram_app import PklManifestLoader
+
+package = PklManifestLoader().load(".")
+
+print(package.application.id)
+orders = package.resource_type("Order")
+list_orders = orders.active.action("List")
+print(list_orders.effect, list_orders.all_open_api_mappings)
+```
+
+The evaluator roots file access at the package directory, permits dependency
+aliases declared by `PklProject`, rejects direct `package:` imports, and denies
+ambient environment and author-defined external-property reads. Resolving a
+declared dependency may still populate Pkl's package cache from its pinned
+package URI; run with a pre-populated cache when validation must make no network
+requests. Deployment expressions that require platform-injected properties are
+outside this initial package-model loader.
+
+## Validating a package
+
+`validate_manifest` returns structured findings instead of throwing on normal
+manifest errors:
+
+```python
+from tangram_app import validate_manifest
+
+result = validate_manifest(".")
+
+for finding in result.findings:
+    print(finding.severity.value, finding.code, finding.path, finding.message)
+
+package = result.require_valid()
+```
+
+Validation currently covers required layout and dependency locks, Pkl loading,
+application metadata, settings and secrets, resource/version/action uniqueness,
+required action semantics, OpenAPI 3 parsing, operation uniqueness, action
+mapping and extractor resolution, Agent tool and skill shapes, Connector
+endpoint/OAuth safety, application-type deployment restrictions, and core UI
+component/path checks. Pkl schema constraints remain the first validation
+layer; these checks handle relationships across evaluated files. App deployment
+inputs and integration modules currently produce explicit coverage warnings;
+use `tangram app manifest validate` for their authoritative schema-reflection
+checks.
+
+## Compiling a capability graph
+
+Compilation validates the package, selects active resource-type versions,
+resolves mapped OpenAPI operations, flattens agent-facing inputs, records their
+reverse path/query/header/body bindings, and calculates a deterministic digest
+over `manifests/` and `libs/`:
+
+```python
+from tangram_app import compile_manifest
+
+compiled = compile_manifest(".")
+graph = compiled.graph
+
+print(graph.package.digest)
+print(graph.actions[0].bindings[0].input_schema)
+graph.write_file("dist/tangram-app.json")
+```
+
+Only actions with `openApiMapping` or `openApiMappings` become executable graph
+capabilities. Compilation findings retain validation warnings, including the
+current deployment and integration coverage limits.
+
+## Using the facade and command line
+
+`TangramApp.from_package` compiles source through Pkl. `from_graph` loads a
+precompiled snapshot without Pkl. Runtime backend configuration is applied
+separately with `bind`:
+
+```python
+from tangram_app import TangramApp
+
+app = TangramApp.from_package(".")
+print([tool.id for tool in app.tools()])
+
+bound = app.bind(backend="http://127.0.0.1:8000")
+result = await bound.call("com.example/orders#Order.List@listOrders", {})
+```
+
+The Python package also exposes a machine-readable command interface. Every
+command writes exactly one versioned JSON envelope to stdout:
+
+```sh
+python -m tangram_app build . --output dist/tangram-app.json
+python -m tangram_app inspect . --tools --format json
+printf '%s' '{}' | python -m tangram_app call \
+  dist/tangram-app.json \
+  com.example/orders#Order.List@listOrders \
+  --backend http://127.0.0.1:8000 \
+  --input-json -
+```
+
+Python compiler results are labeled `authority: development` until shared
+golden fixtures prove parity with Tangram's publishing validator. That authority,
+plus a `developmentOnly` marker for local Pkl project dependencies, is persisted
+in the graph so loading a snapshot cannot accidentally upgrade its provenance.
+Source-mode inspection reports manifest/OpenAPI validation as enforced;
+snapshot-mode inspection reports it as delegated to the compiled artifact.
+
+Runtime requirements are also part of the graph. Settings, secrets, and
+deployment claims owned by an already-running App service are reported as
+delegated to that backend. Required Connector or Agent requirements that this
+standalone host cannot resolve block `bind()` before any network request.
+
+## Authoring and running an agent-built app
+
+`TangramProject` represents the mutable canonical source package used by a
+coding agent or app author:
+
+```python
+from tangram_app import TangramProject
+
+project = TangramProject.open(".")
+validation = project.validate()
+app = project.compile()
+
+with project.run_local() as running:
+    result = await running.call("com.example/todos#Todo.List@listTodos", {})
+```
+
+The local runtime reads
+`manifests/deployment/source/backend/pyproject.toml`, resolves the declared
+Python 3.12 entry module under `src/`, prepares a cached
+`.preview/backend-venv` from the Tangram runtime pins, stages the backend
+`tangram` module, starts `entry:app` with uvicorn on loopback, waits for
+`/openapi.json`, and refuses startup when a compiled action operation is
+missing. It executes the source tree, never the deployment image.
+
+When `deployment/dependencies.pkl` declares the canonical `main`
+`PostgresqlDatabaseClaim`, the SDK discovers a host PostgreSQL installation,
+starts a project-scoped instance backed by `.preview/pgdata`, creates the
+`app` database, and applies `deployment/migrations/main/Vn__*.sql` in order.
+Applied checksums are recorded in `_tangram_app_migrations`; changing an
+already-applied migration is refused. Install PostgreSQL separately or set
+`TANGRAM_LOCAL_PG_BIN_DIR` to its `bin` directory. Other infrastructure claims,
+settings, and secrets remain explicit unsupported requirements.
+
+The local host is read-only by default. Embedded callers can pass a
+`LocalDevelopmentPolicy` to `run_local()` to grant specific mutating action IDs
+and, separately, preauthorize confirmation-gated actions.
+
+For one governed call, the CLI can own the backend lifecycle automatically:
+
+```sh
+printf '%s' '{}' | python -m tangram_app call . \
+  com.example/todos#Todo.List@listTodos --local --input-json -
+```
+
+For a long-running local backend session:
+
+```sh
+python -m tangram_app run .
+```
+
+The command emits one readiness envelope and stays in the foreground until
+interrupted. It captures backend output in the contained `.preview` directory
+and terminates the backend process group on shutdown.
+
+Capability graphs retain declared root UI metadata, and `run_local()` compiles
+the sandboxed root component and exposes it through `running.ui_url`. The first
+run prepares `.preview/ui-runtime` with the server-compatible component catalog
+and esbuild; callers may instead set `TANGRAM_ESBUILD_BIN` and
+`TANGRAM_COMPONENT_NODE_MODULES`. The injected browser SDK routes
+`performAction` to the same validated backend action host. Reversible UI actions
+run directly; irreversible or confirmation-required actions require a browser
+confirmation before the exact frozen request is retried.
+
+## Installing the authoring skills
+
+The SDK bundles two authoring skills: `tangram-app-builder` (apps with
+their own backend/database/UI: layout, manifest templates, the
+validate/run/call loop, platform-parity gotchas) and
+`tangram-connector-builder` (connectors mapping an external SaaS API —
+Gmail/Slack style — into governed actions with platform-managed OAuth).
+Install either where your agent discovers instructions:
+
+```sh
+python -m tangram_app skill install NAME --project .   # ./.claude/skills/  (Claude Code, this repo)
+python -m tangram_app skill install NAME --user        # ~/.claude/skills/  (Claude Code, all repos)
+python -m tangram_app skill install NAME --codex       # ~/.codex/prompts/  (Codex, no Claude needed)
+```
+
+`skill install-builder` remains an alias for
+`skill install tangram-app-builder`.
+
+Claude Code users can instead install it as a plugin without the SDK:
+`/plugin marketplace add tangram-data/tangram-app-manifest` then
+`/plugin install tangram-app-builder`.
+
+For **Codex-only** machines, `--codex` installs the full skill as the
+custom prompt `/tangram-app-builder`. To make Codex apply it automatically
+instead of on invocation, add to `~/.codex/AGENTS.md`:
+
+```markdown
+When asked to create, modify, or debug a Tangram app, first read
+~/.codex/prompts/tangram-app-builder.md and follow it.
+```
+
+The packaged copy is release-authoritative; the repo mirrors are
+sha-checked against it in CI.
+
+## Installing and opening apps locally
+
+Agents (or humans) can install a built app — a generated source package,
+or an App Hub tarball — into the user-level store at `~/.tangram/apps/`,
+then address it by id everywhere a package path is accepted:
+
+```sh
+tangram-app app install ./my-app            # or app.tar.gz, or an https URL
+tangram-app app list
+tangram-app open my-app                     # run + open the UI in a browser
+printf '{}' | tangram-app call my-app 'com.example/my-app#Todo.List@listTodos' \
+  --local --input-json -
+tangram-app app uninstall my-app
+```
+
+`install` validates the package first and refuses stale layouts with
+actionable findings. Runtime state stays under the installed app's own
+`.preview/`. Override the store root with `TANGRAM_HOME`.
+
+## Generating an agent skill
+
+Generate a portable, graph-backed skill for Codex, Claude, or another
+shell-capable agent:
+
+```sh
+python -m tangram_app skill generate . \
+  --output dist/agent-skills/orders
+```
+
+The artifact contains a concise `SKILL.md`, optional Codex UI metadata, a
+relative-path runner, a compact action catalog, an executable capability-graph
+snapshot, and `skill.lock.json`. The runner verifies the graph against the lock
+before every inspection or call and imports the installed Python SDK directly;
+it does not require the native Tangram CLI or Pkl at invocation time.
+When the canonical source package is available, the runner also accepts
+`--local-package <app-dir>`: it recompiles the source, verifies its digest still
+matches the skill snapshot, starts the declared Python backend, invokes the
+action, and shuts the backend down. This source mode requires Pkl.
+
+## Calling a local HTTP backend
+
+`LocalHttpDriver` reverses the graph's flat agent inputs into OpenAPI path,
+query, header, and JSON-body inputs. It is loopback-only, disables redirects
+and ambient proxies, bounds URLs/headers/bodies/responses, and redacts upstream
+error bodies:
+
+```python
+import asyncio
+
+from tangram_app import LocalHttpDriver, TangramHost, compile_manifest
+
+
+async def main() -> None:
+    graph = compile_manifest(".").graph
+    host = TangramHost(
+        graph,
+        driver=LocalHttpDriver("http://127.0.0.1:8000"),
+    )
+    result = await host.call(
+        "com.example/orders#Order.List",
+        {"status": "pending"},
+    )
+    print(result)
+
+
+asyncio.run(main())
+```
+
+`HttpExecutionDriver(..., allow_remote=True)` is the explicit remote connector
+escape hatch. Only use it with a trusted configured base URL; redirects remain
+disabled and configured headers are injected after agent-provided inputs so
+credentials cannot be overridden.
+
+## Development
+
+Create an isolated environment and install the SDK. The real-Pkl integration
+tests run when `pkl` is installed and are otherwise skipped:
+
+```sh
+cd python-sdk
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install -e .
+python -m unittest discover -s tests -v
+```
+
+## Example
+
+```python
+import asyncio
+
+from tangram_app import (
+    CapabilityGraph,
+    InMemoryDriver,
+    LocalDevelopmentPolicy,
+    TangramHost,
+)
+
+
+async def main() -> None:
+    graph = CapabilityGraph.from_file("dist/tangram-app.json")
+    driver = InMemoryDriver()
+
+    @driver.handler("com.example/orders#Order.List@listOrders")
+    async def list_orders(arguments):
+        return {"orders": [], "status": arguments.get("status")}
+
+    host = TangramHost(
+        graph,
+        driver=driver,
+        policy=LocalDevelopmentPolicy(),
+    )
+    result = await host.call(
+        "com.example/orders#Order.List@listOrders",
+        {"status": "pending"},
+    )
+    print(result)
+
+
+asyncio.run(main())
+```
+
+`LocalDevelopmentPolicy` allows `Stateless` actions and denies mutations. A
+mutating binding must be named explicitly in `allow_mutations`; an action that
+requires confirmation must additionally be named in
+`preauthorized_confirmations`. This is startup pre-authorization, not a claim
+that a generic agent protocol supplied per-call human confirmation.