levain-cli 0.1.0__tar.gz

levain_cli-0.1.0/.gitignore

@@ -0,0 +1,119 @@
+# Local secrets
+.secrets
+
+# Dependencies
+node_modules/
+
+# Terraform
+.terraform/
+terraform.tfstate
+terraform.tfstate.backup
+*.tfvars
+*.tfvars.json
+.terraform.tfstate.lock.info
+
+# Built code
+dist/
+build/
+!**/platform_agents/build/
+!**/src/build/
+
+# Binaries
+bin/
+
+# Packaged code
+*.tgz
+*.zip
+*.tar
+*.tar.gz
+
+# Environments
+.env
+*.env
+.venv
+
+# Misc
+.DS_Store
+*.log
+
+# Python bytecode
+__pycache__/
+*.py[cod]
+*.egg-info/
+
+# Test coverage
+.coverage
+.coverage.*
+.pytest_cache/
+htmlcov/
+
+# Ruff / MyPy caches
+.ruff_cache/
+.mypy_cache/
+
+# VS Code (enable sharing settings)
+!.vscode
+
+# Claude Code local settings
+.claude/settings.local.json
+.claude/worktrees/
+
+# Skills tooling installed locally via `hyperframes skills` (keep the repo's own skills, e.g. check-pr)
+.agents/
+skills-lock.json
+.claude/skills/*
+!.claude/skills/check-pr/
+
+# Knead orchestrator state
+.knead/
+
+# Local-mode harness session state (per-session workspace +
+# Claude session map, bind-mounted into the harness + sandbox
+# containers).  Path is referenced from local_sandbox.py and
+# docker-compose.yaml; safe to delete to wipe local sessions.
+.levain-cache/
+
+# Full-stack marker written by ``./levain init --all``.
+.levain-full
+
+# Nested repos (legacy, from old multi-repo setup)
+repos/
+
+# Local kubeconfig (legacy path — kubeconfig now lives in
+# ~/.levain/proxy/<env>/kubeconfig). Kept ignored to clean up stale
+# files from older checkouts.
+.kube/
+
+# Legacy proxy state (SSH keypair, PIDs). Superseded by
+# ~/.levain/proxy/<env>/. Kept ignored so `git add .` on existing
+# checkouts can't accidentally commit the private key.
+.proxy/
+
+# Next.js
+.next/
+next-env.d.ts
+
+# Vite
+.vite/
+
+# Generated workspace file
+levain.code-workspace
+.gstack/
+.env.local
+.env.development.local
+*.tsbuildinfo
+.eslintcache
+.playwright-mcp/
+
+# issue2pr recipe→monitor IPC outcome file (transient, never committed —
+# a tracked copy breaks every other branch's rebase via detach-HEAD conflicts)
+.issue2pr/
+
+# Generated PlusCal specs (scratch/example output)
+specs/
+.claude/scheduled_tasks.lock
+.claude/worktrees/
+kubeconfig
+
+# Local TLC toolchain drop-in (CI extracts it from the ghcr carrier)
+tools/tla2tools.jar

levain_cli-0.1.0/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.

levain_cli-0.1.0/PKG-INFO

@@ -0,0 +1,77 @@
+Metadata-Version: 2.5
+Name: levain-cli
+Version: 0.1.0
+Summary: Levain recipe toolchain: PlusCal validator, TLC model checking, and GraphState codegen for agent recipes
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: httpx==0.28.1
+Requires-Dist: pydantic==2.13.4
+Requires-Dist: tree-sitter-tlaplus==1.5.0
+Requires-Dist: tree-sitter==0.26.0
+Requires-Dist: typer==0.26.8
+Provides-Extra: mcp
+Requires-Dist: fastmcp==3.4.7; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# levain-cli
+
+The open toolchain for authoring [Levain](https://levainlabs.com) agent
+recipes: a validator, model checker, and code generator for the PlusCal
+recipe format that Levain agents are defined in.
+
+A recipe package is a `graph.tla` PlusCal spec (the agent's node graph
+and state) plus a Python package with one function per node. This tool
+checks both halves and keeps them coherent:
+
+- **validate** — parse the spec, enforce the recipe grammar profile,
+  check graph topology, translate PlusCal to TLA+, and model-check the
+  result with TLC (deadlock and termination).
+- **validate-package** — all of the above, plus Python source
+  cross-checks (every `@node` function exists and is importable) and
+  `pyproject.toml` checks.
+- **generate-state** — regenerate `_state.py`, the typed `GraphState`
+  TypedDict node functions program against.
+
+## Install
+
+```
+uv tool install levain-cli
+```
+
+TLC model checking (stages 4-5) needs a Java runtime; `tla2tools.jar`
+is fetched automatically on first use. Without Java the tool degrades
+to the pure-Python stages and says so — the Levain platform re-runs
+full validation on every push, so nothing is lost, only local
+feedback latency.
+
+## Use
+
+```
+levain validate graph.tla
+levain validate-package .
+levain generate-state .
+levain --version
+```
+
+The import package is `levain_recipe` — use it to lint recipes from
+your own CI or scripts:
+
+```python
+from levain_recipe.validate import validate_fast
+```
+
+Validation errors are prescriptive (`[stage] line N: message`, with
+TLC counterexample traces) — they are the recipe format's primary
+teaching interface, for humans and agents alike.
+
+For MCP clients that cannot run shell commands (e.g. Claude Desktop),
+`levain mcp` serves the same operations over stdio; install
+with the `[mcp]` extra.
+
+## What this is not
+
+Recipe *execution* — compiling a validated spec into a running agent,
+sandboxing, integrations — happens on the Levain platform. Passing
+local validation is necessary, not sufficient: the platform validates
+again server-side before a version can be published.

levain_cli-0.1.0/README.md

@@ -0,0 +1,61 @@
+# levain-cli
+
+The open toolchain for authoring [Levain](https://levainlabs.com) agent
+recipes: a validator, model checker, and code generator for the PlusCal
+recipe format that Levain agents are defined in.
+
+A recipe package is a `graph.tla` PlusCal spec (the agent's node graph
+and state) plus a Python package with one function per node. This tool
+checks both halves and keeps them coherent:
+
+- **validate** — parse the spec, enforce the recipe grammar profile,
+  check graph topology, translate PlusCal to TLA+, and model-check the
+  result with TLC (deadlock and termination).
+- **validate-package** — all of the above, plus Python source
+  cross-checks (every `@node` function exists and is importable) and
+  `pyproject.toml` checks.
+- **generate-state** — regenerate `_state.py`, the typed `GraphState`
+  TypedDict node functions program against.
+
+## Install
+
+```
+uv tool install levain-cli
+```
+
+TLC model checking (stages 4-5) needs a Java runtime; `tla2tools.jar`
+is fetched automatically on first use. Without Java the tool degrades
+to the pure-Python stages and says so — the Levain platform re-runs
+full validation on every push, so nothing is lost, only local
+feedback latency.
+
+## Use
+
+```
+levain validate graph.tla
+levain validate-package .
+levain generate-state .
+levain --version
+```
+
+The import package is `levain_recipe` — use it to lint recipes from
+your own CI or scripts:
+
+```python
+from levain_recipe.validate import validate_fast
+```
+
+Validation errors are prescriptive (`[stage] line N: message`, with
+TLC counterexample traces) — they are the recipe format's primary
+teaching interface, for humans and agents alike.
+
+For MCP clients that cannot run shell commands (e.g. Claude Desktop),
+`levain mcp` serves the same operations over stdio; install
+with the `[mcp]` extra.
+
+## What this is not
+
+Recipe *execution* — compiling a validated spec into a running agent,
+sandboxing, integrations — happens on the Levain platform. Passing
+local validation is necessary, not sufficient: the platform validates
+again server-side before a version can be published.

levain_cli-0.1.0/levain_recipe/__init__.py

@@ -0,0 +1,20 @@
+"""Levain recipe toolchain — PlusCal validator + state codegen.
+
+The open, client-side half of the Levain recipe toolchain: parse,
+profile and graph checks, PlusCal→TLA+ translation, TLC model
+checking, and ``GraphState`` codegen.  Recipe compilation and
+execution stay platform-side, and a pushed version is always
+re-validated there.
+
+Import models from ``.models`` and validation functions from
+``.validate`` directly — the validate submodule pulls in
+tree-sitter and other heavy deps, and keeping ``__init__`` empty
+lets light callers (version reporting, service health checks)
+avoid them.
+"""
+
+# The recipe *language* version — bumped when the grammar profile
+# or annotation vocabulary changes, independently of tool
+# releases.  The API's toolchain handshake compares this against
+# the server's copy.
+LANGUAGE_VERSION = "1.0"

levain_cli-0.1.0/levain_recipe/__main__.py

@@ -0,0 +1,6 @@
+"""``python -m levain_recipe`` — CLI entrypoint."""
+
+from .cli import app
+
+if __name__ == "__main__":
+    app()

levain_cli-0.1.0/levain_recipe/_format.py

@@ -0,0 +1,45 @@
+"""Validation-result formatting shared by the CLI and MCP server.
+
+The exact output strings are load-bearing: build agents parse the
+``VALIDATION FAILED``/``VALIDATION PASSED`` headers and per-error
+``[stage] line N: message`` lines.  Change them only with a
+language-version bump.
+"""
+
+from __future__ import annotations
+
+from .models import ValidatedSpec, ValidationError
+
+
+def format_error(err: ValidationError) -> str:
+    """Format a single error for the builder to parse."""
+    loc = f" line {err.line}:" if err.line else ":"
+    line = f"[{err.stage}]{loc} {err.message}"
+    if err.counterexample:
+        line += "\n  Counterexample:"
+        for step in err.counterexample:
+            line += f"\n    {step}"
+    return line
+
+
+def format_errors(errors: list[ValidationError]) -> str:
+    """Format all errors into structured output."""
+    n = len(errors)
+    noun = "error" if n == 1 else "errors"
+    header = f"VALIDATION FAILED ({n} {noun})\n"
+    body = "\n".join(format_error(e) for e in errors)
+    return f"{header}\n{body}\n\nFix these errors and regenerate the spec."
+
+
+def format_success(spec: ValidatedSpec) -> str:
+    """Format the success summary."""
+    nodes = ", ".join(n.label for n in spec.nodes)
+    transitions = sum(len(r.routes) for r in spec.routing)
+    invariants = ", ".join(spec.invariants) if spec.invariants else "(none)"
+    return (
+        f"VALIDATION PASSED\n\n"
+        f"Module: {spec.module_name}\n"
+        f"Nodes: {nodes}\n"
+        f"Transitions: {transitions}\n"
+        f"Invariants: {invariants}"
+    )

levain_cli-0.1.0/levain_recipe/_java.py

@@ -0,0 +1,95 @@
+"""Shared Java/tla2tools.jar helpers for stages 4-5."""
+
+from __future__ import annotations
+
+import os
+import re
+import shutil
+import sys
+import urllib.request
+from pathlib import Path
+
+from .models import ValidationError
+
+RE_MODULE_NAME = re.compile(r"^[a-zA-Z_]\w*$")
+
+TLA2TOOLS_VERSION = "1.8.0"
+# Upstream release assets are mutable (re-uploaded in place before);
+# service images therefore pin the jar via a ghcr carrier image.
+# This URL is only the client-side convenience fetch — best-effort,
+# and the platform re-validates server-side regardless.
+_JAR_URL = (
+    "https://github.com/tlaplus/tlaplus/releases/download/"
+    f"v{TLA2TOOLS_VERSION}/tla2tools.jar"
+)
+_JAR_CACHE = Path.home() / ".local" / "share" / "tla" / "tla2tools.jar"
+
+
+def resolve_jar() -> str | None:
+    """Find tla2tools.jar.
+
+    Order: ``TLA2TOOLS_JAR`` env var (service images set it),
+    ``tools/tla2tools.jar`` relative to a source checkout (CI
+    extracts the ghcr carrier there), then the user cache that
+    :func:`ensure_jar` fills.
+    """
+    env = os.environ.get("TLA2TOOLS_JAR")
+    if env:
+        path = os.path.normpath(env)
+        if os.path.isfile(path):
+            return path
+        return None
+    repo_tools = os.path.normpath(
+        os.path.join(
+            os.path.dirname(__file__),
+            "..",
+            "..",
+            "..",
+            "tools",
+            "tla2tools.jar",
+        )
+    )
+    if os.path.isfile(repo_tools):
+        return repo_tools
+    if _JAR_CACHE.is_file():
+        return str(_JAR_CACHE)
+    return None
+
+
+def ensure_jar() -> str | None:
+    """Resolve the jar, downloading to the user cache on first use.
+
+    CLI/MCP-only convenience — library callers use
+    :func:`resolve_jar` so validation never does network I/O.
+    """
+    found = resolve_jar()
+    if found is not None:
+        return found
+
+    _JAR_CACHE.parent.mkdir(parents=True, exist_ok=True)
+    tmp = _JAR_CACHE.with_suffix(".part")
+    print(
+        f"Fetching tla2tools.jar {TLA2TOOLS_VERSION} (one-time)...",
+        file=sys.stderr,
+    )
+    try:
+        urllib.request.urlretrieve(_JAR_URL, tmp)
+        tmp.replace(_JAR_CACHE)
+    except OSError as exc:
+        tmp.unlink(missing_ok=True)
+        print(f"Could not fetch tla2tools.jar: {exc}", file=sys.stderr)
+        return None
+    return str(_JAR_CACHE)
+
+
+def require_java(stage: str) -> str | list[ValidationError]:
+    """Return the java binary path, or a ValidationError."""
+    java = shutil.which("java")
+    if java is None:
+        return [
+            ValidationError(
+                stage=stage,
+                message="Java not found.",
+            )
+        ]
+    return java