tamarind-cli 0.2.0__tar.gz → 0.3.0__tar.gz

{tamarind_cli-0.2.0 → tamarind_cli-0.3.0}/.github/workflows/ci.yml

@@ -9,6 +9,41 @@ permissions:
   contents: read
 
 jobs:
+  generated:
+    name: Generated transport is current
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - name: Verify backend provenance and generated client freshness
+        run: |
+          uv run --extra dev python scripts/check_custom_tools_provenance.py
+          tmp_dir=$(mktemp -d .custom-tools-generated.XXXXXX)
+          trap 'rm -rf "$tmp_dir"' EXIT
+          uv run --extra dev openapi-python-client generate --path openapi/public-v1.json \
+            --config openapi/openapi-python-client.json --meta none \
+            --output-path "$tmp_dir/generated" --overwrite
+          diff -ru --exclude=.ruff_cache src/tamarind/custom_tools/_generated "$tmp_dir/generated"
+
+  typecheck:
+    name: Custom Tools type check
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          python-version: "3.12"
+      - name: Check the public SDK and transport boundary
+        run: >-
+          uv run --extra dev mypy
+          src/tamarind/custom_tools
+          src/tamarind/http.py
+          src/tamarind/errors.py
+          scripts/sync_custom_tools_contract.py
+
   package:
     name: Build release artifacts
     runs-on: ubuntu-latest

tamarind_cli-0.2.0/README.md → tamarind_cli-0.3.0/PKG-INFO

@@ -1,3 +1,28 @@
+Metadata-Version: 2.5
+Name: tamarind-cli
+Version: 0.3.0
+Summary: Command-line interface for the Tamarind Bio platform — submit, monitor, and download protein/molecule jobs from your terminal or an AI agent.
+Project-URL: Homepage, https://tamarind.bio
+Project-URL: Documentation, https://app.tamarind.bio/api-docs
+Project-URL: Source, https://github.com/Tamarind-Bio/tamarind-cli
+Author: Tamarind Bio
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agents,alphafold,bioinformatics,boltz,cli,protein
+Requires-Python: >=3.10
+Requires-Dist: attrs>=23.1
+Requires-Dist: httpx>=0.27
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: typer>=0.12
+Requires-Dist: typing-extensions>=4.7
+Provides-Extra: dev
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: openapi-python-client==0.28.4; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: respx>=0.21; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
 # Tamarind CLI
 
 [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
@@ -78,6 +103,40 @@ tamarind submit boltz \
   --name quick-fold
 ```
 
+## Python SDK
+
+The package also exposes a typed Custom Tools SDK. It checks archive-local
+safety, packages a folder, uploads it directly to object storage, and submits the
+digest-checked build request. The server
+remains authoritative for source readiness, Versions, logs, and the evolving
+`config.json` contract.
+
+```python
+from tamarind import Tamarind
+from tamarind.errors import CustomToolNotFoundError
+
+with Tamarind() as client:
+    try:
+        tool = client.custom_tools.get("my-esmfold")
+    except CustomToolNotFoundError:
+        tool = client.custom_tools.create("my-esmfold", display_name="My ESMFold")
+
+    result = tool.build("./my-esmfold")
+    print(result.action)  # build, reuse_image, or unchanged
+    version = result.version
+    if not version.terminal:
+        version = version.monitor(timeout=1800, on_event=print)
+```
+
+`build()` returns a typed result describing what the request did and the durable
+Version it produced. It is convenience orchestration, not a durable request
+object. If the connection is lost during the build response, fetch the tool's
+versions before retrying. Interrupting `monitor()` stops local monitoring; it
+does not cancel the remote build.
+
+Custom Tool CLI commands are not part of this release. Existing CLI commands
+remain unchanged.
+
 ## Output for agents
 
 Every command emits JSON when stdout is not a TTY, or with `--json`. Result

tamarind_cli-0.2.0/PKG-INFO → tamarind_cli-0.3.0/README.md

@@ -1,24 +1,3 @@
-Metadata-Version: 2.4
-Name: tamarind-cli
-Version: 0.2.0
-Summary: Command-line interface for the Tamarind Bio platform — submit, monitor, and download protein/molecule jobs from your terminal or an AI agent.
-Project-URL: Homepage, https://tamarind.bio
-Project-URL: Documentation, https://app.tamarind.bio/api-docs
-Project-URL: Source, https://github.com/Tamarind-Bio/tamarind-cli
-Author: Tamarind Bio
-License: Apache-2.0
-License-File: LICENSE
-Keywords: agents,alphafold,bioinformatics,boltz,cli,protein
-Requires-Python: >=3.10
-Requires-Dist: httpx>=0.27
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: typer>=0.12
-Provides-Extra: dev
-Requires-Dist: pytest>=8.0; extra == 'dev'
-Requires-Dist: respx>=0.21; extra == 'dev'
-Requires-Dist: ruff>=0.5; extra == 'dev'
-Description-Content-Type: text/markdown
-
 # Tamarind CLI
 
 [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
@@ -99,6 +78,40 @@ tamarind submit boltz \
   --name quick-fold
 ```
 
+## Python SDK
+
+The package also exposes a typed Custom Tools SDK. It checks archive-local
+safety, packages a folder, uploads it directly to object storage, and submits the
+digest-checked build request. The server
+remains authoritative for source readiness, Versions, logs, and the evolving
+`config.json` contract.
+
+```python
+from tamarind import Tamarind
+from tamarind.errors import CustomToolNotFoundError
+
+with Tamarind() as client:
+    try:
+        tool = client.custom_tools.get("my-esmfold")
+    except CustomToolNotFoundError:
+        tool = client.custom_tools.create("my-esmfold", display_name="My ESMFold")
+
+    result = tool.build("./my-esmfold")
+    print(result.action)  # build, reuse_image, or unchanged
+    version = result.version
+    if not version.terminal:
+        version = version.monitor(timeout=1800, on_event=print)
+```
+
+`build()` returns a typed result describing what the request did and the durable
+Version it produced. It is convenience orchestration, not a durable request
+object. If the connection is lost during the build response, fetch the tool's
+versions before retrying. Interrupting `monitor()` stops local monitoring; it
+does not cancel the remote build.
+
+Custom Tool CLI commands are not part of this release. Existing CLI commands
+remain unchanged.
+
 ## Output for agents
 
 Every command emits JSON when stdout is not a TTY, or with `--json`. Result

{tamarind_cli-0.2.0 → tamarind_cli-0.3.0}/docs/architecture.md

@@ -2,10 +2,10 @@
 
 The CLI, the [MCP server](https://mcp.tamarind.bio), and the web app are all
 **thin clients** over the same platform. The CLI never re-implements business
-logic; it only knows how to call two well-defined surfaces. This is what keeps
+logic; it only knows how to call three well-defined surfaces. This is what keeps
 the CLI and the MCP from drifting as the platform evolves.
 
-## Two surfaces, two single sources of truth
+## Three surfaces, three single sources of truth
 
 ### 1. Job/file REST surface — source of truth: the OpenAPI spec
 
@@ -37,6 +37,43 @@ Because the logic lives in one module, *where* discovery is hosted (the MCP host
 today; potentially the main API or a dedicated service later) is a deployment
 detail that can change without any client change and without drift.
 
+### 3. Custom Tools surface — source of truth: the public OpenAPI artifact
+
+Custom Tool creation, source upload, build, Versions, logs, and cancellation
+are generated from the website backend's dedicated public OpenAPI artifact:
+
+```text
+backend-owned custom-tools-v1.generated.json
+  -> Git-object provenance verification
+  -> vendored spec + lock
+  -> openapi-python-client==0.28.4
+  -> generated models/endpoints
+  -> thin Tamarind transport and resource adapters
+```
+
+The Website owns the projection and its referenced-component closure. The CLI sync
+verifies the exact producer repository, commit, path, and bytes before atomically
+installing the spec, provenance lock, generated server metadata, and generated package.
+CI regenerates with the pinned mature generator and rejects drift. The handwritten
+layer contains only HTTP/error normalization and ergonomic resource composition; it
+does not parse OpenAPI or maintain a second schema IR/compiler.
+
+The SDK owns archive-local concerns that only the client can decide safely:
+deterministic ZIP construction, symlink and junction rejection, upload limits,
+JSON parseability and top-level object shape, and warnings about the networkless
+runtime. Archives use stored ZIP entries so source digests do not depend on a
+platform zlib build. Modes are also platform-stable: `run.sh` and files beginning
+with a shebang are executable, while all other files are regular. The backend owns
+the evolving `config.json` business contract and
+validates it before accepting a build. The SDK deliberately does not maintain a
+second list of configuration fields, enums, or cross-field rules.
+
+`CustomTool.build()` composes the existing requests: create upload, PUT the archive,
+submit the digest-checked build request, and return a typed result containing the server's
+action plus its durable Version. It adds no server-side
+BuildRequest, queue, lease, claim, or repair state. An ambiguous build response
+is therefore handled honestly by listing Versions before a manual retry.
+
 ## Why not a single binary that re-encodes the API?
 
 A from-scratch client in another language would re-encode the request shapes and

tamarind_cli-0.3.0/openapi/openapi-python-client.json

@@ -0,0 +1,4 @@
+{
+  "package_name_override": "_generated",
+  "project_name_override": "tamarind-custom-tools-generated"
+}