windtunnel-bench 0.1.0__tar.gz

windtunnel_bench-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,31 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.11"
+      - name: Install
+        run: uv sync
+      - name: Lint
+        run: uv run ruff check windtunnel/ tests/
+      - name: Unit tests (no infrastructure required)
+        run: uv run pytest -m "not integration" -q --timeout=120
+
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.11"
+      - name: Build docs (strict — broken nav/links fail)
+        run: uv run --group docs mkdocs build --strict

windtunnel_bench-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,40 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# One Pages deploy at a time; don't cancel a deploy mid-flight.
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.11"
+      - name: Build site
+        run: uv run --group docs mkdocs build --strict
+      - uses: actions/configure-pages@v5
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

windtunnel_bench-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,25 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    # Trusted Publishing (OIDC) — no API token. The PyPI project must list
+    # this repo + workflow + environment as a trusted publisher (see
+    # CONTRIBUTING.md "One-time repository setup").
+    environment: pypi
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.11"
+      - name: Build sdist and wheel
+        run: uv build
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

windtunnel_bench-0.1.0/.github/workflows/release-please.yml

@@ -0,0 +1,18 @@
+name: Release Please
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: googleapis/release-please-action@v4
+        with:
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json

windtunnel_bench-0.1.0/.gitignore

@@ -0,0 +1,23 @@
+# Virtual environments
+.venv/
+
+# Run artifacts (traces + score sidecars + reports — generated, not source)
+runs/*
+!runs/.gitkeep
+report.html
+
+# Caches
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+*.egg-info/
+
+# OS noise
+.DS_Store
+
+# MkDocs build output
+site/
+
+# Build artifacts
+dist/

windtunnel_bench-0.1.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.1.0"
+}

windtunnel_bench-0.1.0/AGENTS.md

@@ -0,0 +1,40 @@
+# Wind Tunnel — agent notes
+
+unittest for agents: scenarios score tool-using LLM agents on four layers
+(outcome / trajectory / constraint / robustness). Layout: `windtunnel/api`
+(scenario authoring), `windtunnel/spi` (runtime Protocols),
+`windtunnel/scenarios/dim_*` (the dimension catalog), `tests/`.
+
+## Commands
+
+```bash
+uv sync                                  # setup (.venv + dev group)
+uv run pytest -m "not integration" -q    # unit suite — must always pass, no infra
+uv run ruff check windtunnel/ tests/     # lint — keep at zero
+uv run wt run --scenario <name> --runtime in_memory --runs 1   # smoke a scenario
+```
+
+## Invariants (test-enforced — do not weaken)
+
+- Scenarios NEVER import `windtunnel.runtimes.*` (`tests/test_import_invariants.py`).
+- Scenario `must_call`/`forbidden_calls` use canonical bare tool names
+  (`client_lookup`); the evaluator matches platform decorations.
+- The per-run pass/fail gate is the **outcome layer only**; trajectory,
+  constraint, and robustness are recorded, not gating
+  (`windtunnel/api/aggregate.py`).
+- `evaluate_outcome` scores the actual last assistant turn, even if empty —
+  never backfill from earlier turns (`windtunnel/api/evaluators.py`).
+- Synthetic data stays fictional: fake orgs, `.example` domains.
+
+## Gotchas
+
+- The `in_memory` runtime never calls tools — `requires_tool_use` scenarios
+  correctly FAIL under it. That's the gate working, not a bug.
+- Entry points (`windtunnel.runtimes` and `windtunnel.scenario_packs` groups)
+  refresh only on reinstall: after touching pyproject entry points, `uv sync`
+  before trusting resolution.
+- `runs/` is generated output (gitignored); traces pair with `.score.json`
+  sidecars written by `wt run`/`wt replay`.
+
+Integrating Wind Tunnel into another repo? Use
+[docs/agent-quickstart.md](docs/agent-quickstart.md).

windtunnel_bench-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,127 @@
+# Contributing to Wind Tunnel
+
+## Dev setup
+
+```bash
+git clone https://github.com/syntropy-systems-oss/windtunnel
+cd windtunnel
+uv sync                  # creates .venv, installs editable + the dev group
+```
+
+## Running checks
+
+```bash
+uv run pytest -m "not integration" -q   # the unit suite — fast, no infrastructure
+uv run ruff check windtunnel/ tests/
+```
+
+The `integration` marker is reserved for tests that need a live agent stack;
+the unit suite must always pass with no network, no Docker, no model.
+
+## The one rule that is not negotiable
+
+**Scenarios never import platform-specific types.** If you can't write a
+scenario without importing `windtunnel.runtimes.*`, the SPI has leaked — fix
+the contract, not the scenario. This is enforced by
+`tests/test_import_invariants.py`; a PR that weakens that test needs a very
+good story.
+
+Two corollaries:
+
+- Scenario `must_call` / `forbidden_calls` use **canonical bare tool names**
+  (`client_lookup`), never platform-decorated ones — the trajectory evaluator
+  matches decorations (`mcp_<server>_<prefix>_client_lookup`, dotted forms)
+  for you.
+- New runtime drivers ship as **separate packages** registering the
+  `windtunnel.runtimes` entry-point group (see
+  [docs/writing-a-runtime.md](docs/writing-a-runtime.md)); they don't get
+  merged into `windtunnel/runtimes/`. The in-tree `in_memory` runtime is the
+  only exception — it's the zero-infrastructure reference. Scenario
+  dimensions have the same seam: external dims ship as `ScenarioPack`s
+  registering the `windtunnel.scenario_packs` group (see
+  [docs/writing-a-scenario.md](docs/writing-a-scenario.md#shipping-a-scenario-pack)).
+
+## Code style
+
+- Python 3.11+, ruff (`E,F,W,I,UP`, line length 100), full type hints on
+  public API surfaces.
+- Dataclasses for data shapes; Protocols for contracts.
+- Docstrings explain *why* and record behavioral contracts — the evaluator
+  semantics in `windtunnel/api/evaluators.py` are the house style to imitate.
+- Tests: one behavior per test, names that read as sentences, and when you
+  fix a bug, the regression test's docstring says what broke.
+
+## Adding a scenario or dimension
+
+Read [docs/writing-a-scenario.md](docs/writing-a-scenario.md). A new dim
+package needs `scenarios.py`, a mock MCP server (build on
+`windtunnel.mcp.fastmcp.server.LoggingFastMCP` — call logging and failure
+injection come free), a synthetic DB, and a `PACK` (a
+`windtunnel.api.ScenarioPack` in the dim's `__init__.py`, listed in
+`windtunnel/scenarios/__init__.py`'s `builtin_packs()`). Keep synthetic data
+fictional: fake names, `.example` domains.
+
+## Docs
+
+The docs site is MkDocs Material over `docs/`, deployed to GitHub Pages by
+`.github/workflows/docs.yml` on every push to `main`. Preview locally:
+
+```bash
+uv run --group docs mkdocs serve
+```
+
+CI builds the site with `--strict`, so a broken nav entry or dead internal
+link fails the build — treat docs like code.
+
+## Releases
+
+Releases are automated with [release-please](https://github.com/googleapis/release-please)
+and **conventional commits** — commit messages drive the version:
+
+- `fix:` → patch, `feat:` → minor, `feat!:`/`BREAKING CHANGE:` → major
+  (pre-1.0, majors are taken as minors).
+- On every push to `main`, release-please maintains a release PR that
+  accumulates the CHANGELOG and the next version (in `pyproject.toml` +
+  `.release-please-manifest.json`). **Merging that PR is the release**: it
+  tags `vX.Y.Z`, creates the GitHub release, and the publish workflow
+  (`.github/workflows/publish.yml`) builds with `uv build` and uploads to
+  PyPI via Trusted Publishing — no API tokens anywhere.
+
+Pre-1.0: breaking changes are allowed but must be a `feat!:` so the
+changelog calls them out. The config encodes the pre-1.0 stance:
+
+- `bump-minor-pre-major: true` — a `feat!:` bumps 0.x → 0.(x+1), never
+  to 1.0.0. Going 1.0 is a deliberate act, not a commit-message accident.
+- `prerelease: true` — GitHub releases are flagged "pre-release" while
+  we're 0.x. This is display-only; PyPI never sees it.
+- We deliberately do NOT use release-please's prerelease *versioning*
+  (rc/beta suffixes): it emits semver-style `0.2.0-rc.1`, which is not a
+  valid PEP 440 version — PyPI wants `0.2.0rc1`. Plain 0.x versions are
+  pip-installable and honest about stability.
+- `include-component-in-tag: false` — tags are plain `vX.Y.Z`, not
+  `windtunnel-vX.Y.Z`, so the manual first tag and release-please's tags
+  agree.
+
+**At 1.0**: remove `bump-minor-pre-major` and `prerelease` from
+`release-please-config.json`. That's the whole graduation ceremony.
+
+### One-time repository setup (maintainers)
+
+Things the workflows need that only the GitHub/PyPI UIs can grant:
+
+1. **Pages**: repo Settings → Pages → Source = "GitHub Actions".
+2. **Release PRs**: Settings → Actions → General → enable
+   "Allow GitHub Actions to create and approve pull requests"
+   (release-please needs it).
+3. **PyPI Trusted Publisher**: on PyPI, add a publisher for project
+   `windtunnel-bench` → owner `syntropy-systems-oss`, repo `windtunnel`,
+   workflow `publish.yml`, environment `pypi`. (For a not-yet-existing
+   project, use PyPI's "pending publisher" flow.) Then create the `pypi`
+   environment in repo Settings → Environments. The bare name
+   `windtunnel` is a squatted empty registration on PyPI; a PEP 541
+   transfer request is pending — if granted, the distribution may be
+   renamed (the import name `windtunnel` is unaffected either way).
+4. **First release**: release-please versions *changes since the last
+   release*, so the initial `v0.1.0` is cut by hand once:
+   `gh release create v0.1.0 --title "v0.1.0" --generate-notes` — the
+   publish workflow takes it from there. Everything after is release PRs.

windtunnel_bench-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 2026 Bryson Tang
+
+   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.