kitchenbench 0.3.0__tar.gz

kitchenbench-0.3.0/.github/workflows/ci.yml

@@ -0,0 +1,55 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  quality:
+    name: lint · type
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          cache-dependency-glob: "**/pyproject.toml"
+      - name: Create venv
+        run: uv venv --python 3.11
+      - name: Install (dev extras; inspect_robots from git via tool.uv.sources)
+        run: uv pip install -e ".[dev]"
+      - name: Ruff (lint)
+        run: uv run ruff check .
+      - name: Ruff (format check)
+        run: uv run ruff format --check .
+      - name: Mypy (strict)
+        run: uv run mypy
+
+  test:
+    name: test (${{ matrix.os }}, py${{ matrix.python-version }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          cache-dependency-glob: "**/pyproject.toml"
+      - name: Create venv (py${{ matrix.python-version }})
+        run: uv venv --python ${{ matrix.python-version }}
+      - name: Install (dev extras)
+        run: uv pip install -e ".[dev]"
+      - name: Pytest (100% coverage gate)
+        run: uv run pytest --cov --cov-report=term-missing

kitchenbench-0.3.0/.github/workflows/release.yml

@@ -0,0 +1,23 @@
+name: Release
+
+# Publishes to PyPI via trusted publishing (OIDC) — no API tokens.
+# Authenticates against the PyPI trusted-publisher entry for this repo
+# (workflow: release.yml, environment: pypi).
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # OIDC token for PyPI trusted publishing
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Build sdist + wheel
+        run: uv build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

kitchenbench-0.3.0/.gitignore

@@ -0,0 +1,224 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer,
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# uv lockfile (this is a library; CI resolves from pyproject)
+uv.lock
+
+# Local read-only copy of the methodology reference (not part of the package)
+reference/

kitchenbench-0.3.0/.pre-commit-config.yaml

@@ -0,0 +1,57 @@
+# Pre-commit hooks for KitchenBench. Install once per clone:
+#
+#     uv run pre-commit install        # sets up both pre-commit and pre-push hooks
+#
+# On commit: file hygiene + ruff (lint & format) + mypy (strict).
+# On push:   pytest with the 100% coverage gate.
+#
+# Run everything manually with:  uv run pre-commit run --all-files
+#
+# The ruff / mypy / pytest hooks are "local" so they use the exact versions
+# pinned in this project's dev environment (matching CI) rather than a separate
+# pinned copy.
+default_install_hook_types: [pre-commit, pre-push]
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-toml
+      - id: check-merge-conflict
+      - id: check-added-large-files
+
+  # Local hooks run through `uv run` so they use this project's dev environment
+  # (matching CI) regardless of whether a virtualenv is activated. Requires uv.
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff (lint, autofix)
+        entry: uv run ruff check --fix
+        language: system
+        types_or: [python, pyi]
+        require_serial: true
+
+      - id: ruff-format
+        name: ruff (format)
+        entry: uv run ruff format
+        language: system
+        types_or: [python, pyi]
+        require_serial: true
+
+      - id: mypy
+        name: mypy (strict)
+        entry: uv run mypy
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: pytest-coverage
+        name: pytest (100% coverage gate)
+        entry: uv run pytest --cov --cov-report=term-missing
+        language: system
+        always_run: true # run on every push, even when no .py files changed
+        pass_filenames: false
+        stages: [pre-push]

kitchenbench-0.3.0/CITATION.cff

@@ -0,0 +1,9 @@
+cff-version: 1.2.0
+message: "If you use this software, please cite it as below."
+title: "KitchenBench: A bimanual kitchen-manipulation benchmark for VLA models"
+authors:
+  - name: "Robocurve"
+type: software
+license: MIT
+repository-code: "https://github.com/robocurve/kitchenbench"
+version: "0.3.0"

kitchenbench-0.3.0/CLAUDE.md

@@ -0,0 +1,68 @@
+# KitchenBench — agent guide
+
+KitchenBench is a **standalone benchmark repo**: 10 bimanual kitchen-manipulation
+tasks for VLA models, expressed as [Inspect Robots](https://github.com/robocurve/inspect-robots)
+`Task`s. It is the first member of
+[WorldEvals](https://github.com/robocurve/worldevals) (the "Inspect Evals for
+robotics"). It is a **Inspect Robots plugin** — it depends on Inspect Robots, defines tasks,
+and registers them via entry points.
+
+## The one big idea
+
+A benchmark is **embodiment-agnostic**: it defines *what* to evaluate (scenes +
+scorers), never *how* the robot is built. The same 10 tasks run against the
+dependency-free mock kitchen (for CI) and against real **YAM bimanual arms +
+MolmoAct2** — only the `Policy`/`Embodiment` change.
+
+Each task is a set of **task instances** (the
+[physical-automation methodology](https://github.com/jeqcho/physical-automation-methodology-docs),
+cloned read-only into `reference/`, gitignored). A task instance is a *stochastic
+environment spec* (named random variables + **distributions**) + a goal. Defaults
+follow the methodology: **5 instances per task** (one `Scene` each) × **5
+realizations per instance** (`Epochs(count=5, reducer="mean")`) = 50 scenes. The
+mean over 5 realizations makes each scene's reduced `task_success` the instance
+success probability **P̂[Yᵢ=1]**. Instances are AI-authored drafts
+(`Validation(source="opus-draft")`, `validated=False`) — not yet human-validated.
+
+## Layout
+
+- `src/kitchenbench/` — the package (see `src/kitchenbench/CLAUDE.md` for the
+  module map and how to add a task).
+- `tests/` — pytest; the mock `KitchenEmbodiment` + scripted policy exercise the
+  whole stack with no hardware.
+- `plans/0002-task-instances-distributions.md` — the design doc for the
+  task-instance/distribution model (read before changing the task set, the
+  distributions, or the 5×5 defaults).
+- `reference/` — read-only local copy of the methodology PDFs (gitignored).
+- `README.md` — the task table + how to run on the mock and on YAM/MolmoAct2.
+
+## Working here (important gotchas)
+
+- **Dependency on Inspect Robots is a git tag.** `pyproject.toml` declares
+  `inspect-robots>=0.3` with `[tool.uv.sources] inspect-robots = { git = ..., tag = "v0.3.0" }`.
+  CI uses `uv` (plain pip ignores `tool.uv.sources`). A sibling checkout exists at
+  `../inspect-robots`; for local dev against it, override with
+  `uv pip install -e ../inspect-robots`.
+- **Conda is active in this shell.** `uv pip install` targets the *active* env, so
+  a bare `uv pip install -e .` lands in conda base, not `.venv`. Always
+  `source .venv/bin/activate && export VIRTUAL_ENV="$PWD/.venv"` first (or use
+  `uv run`).
+- Dev loop: `uv venv && uv pip install -e ".[dev]"`, `uv run pre-commit install`,
+  `uv run pytest --cov`.
+- **Gates (all must pass):** `ruff check .`, `ruff format --check .`, `mypy`
+  (strict), `pytest --cov` at **100% coverage**. Pre-commit runs ruff+mypy on
+  commit and the coverage gate on push (via `uv run`). CI (Linux+macOS ×
+  py3.11/3.12) and the 100% gate are **required, blocking PR checks**.
+- **Authoring imports come from the top-level `inspect_robots` package** (its public
+  API, stable as of v0.3.0): `from inspect_robots import Task, Scene, Target, task,
+  ActionChunk, ...`. Don't import from `inspect_robots.<submodule>` unless a symbol
+  isn't re-exported (capability flags like `SEEDABLE` live in
+  `inspect_robots.embodiment`).
+
+## Out of scope (lives elsewhere)
+
+The real YAM-arms `Embodiment` and the MolmoAct2 `Policy` are *adapters* and live
+in their own package (e.g. `robocurve/embodiments`), not here. KitchenBench ships
+only the tasks + a mock world. See the README's "Run it on real hardware" section
+for the contract those adapters must implement (operator-confirmed success →
+`termination_reason="success"`; declare `"self_paced"` and pace `step()`).

kitchenbench-0.3.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 robocurve
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.