stuntdouble 2.0.1__tar.gz

stuntdouble-2.0.1/.github/CODEOWNERS

@@ -0,0 +1,10 @@
+# List of source code paths and code owners
+# For more information on the CODEOWNERS file go to: 
+# https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-syntax
+
+# Uncomment line 10 and add the correct owners's usernames.
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+*       @bbenchaya

stuntdouble-2.0.1/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+### Checklist
+🚨 Please review this repository's [contribution guidelines](./CONTRIBUTING.md).
+
+- [ ] I've read and agree to the project's contribution guidelines.
+- [ ] I'm requesting to **pull a topic/feature/bugfix branch**.
+- [ ] I checked that my code additions will pass code linting checks and unit tests.
+- [ ] I updated unit and integration tests (if applicable).
+- [ ] I'm ready to notify the team of this contribution.
+
+### Description
+What does this change do and why?
+
+Fixes #(issue number)
+
+Thank you!

stuntdouble-2.0.1/.github/workflows/ci.yml

@@ -0,0 +1,67 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    name: Lint
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+
+      - name: Set up Python
+        run: uv python install 3.13
+
+      - name: Install dependencies
+        run: uv sync --all-extras --group dev
+
+      - name: Check formatting  - lint (ruff)
+        run: uv run ruff check
+
+  test:
+    name: Test (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+
+      - name: Set up Python ${{ matrix.python-version }}
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv sync --all-extras --group dev
+
+      - name: Run tests with coverage
+        run: |
+          uv run pytest tests/ \
+            --color=yes \
+            --cov=src/stuntdouble \
+            --cov-report=term \
+            --cov-report=xml:coverage.xml \
+            --cov-fail-under=74 \
+            -v
+
+      - name: Upload coverage
+        if: matrix.python-version == '3.13'
+        uses: actions/upload-artifact@v7
+        with:
+          name: coverage-report
+          path: coverage.xml
+

stuntdouble-2.0.1/.github/workflows/release.yml

@@ -0,0 +1,67 @@
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Version to release (e.g. 0.2.0)"
+        required: true
+        type: string
+      bump-type:
+        description: "Version bump type (used as label only)"
+        required: false
+        default: "patch"
+        type: choice
+        options: [patch, minor, major]
+
+permissions:
+  contents: write
+  id-token: write  # required for OIDC trusted publishing
+  
+jobs:
+  release:
+    name: Tag & Publish
+    runs-on: ubuntu-latest
+    environment: pypi
+
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Install deps
+        run: uv sync --group dev
+
+      - name: Run tests before release
+        run: uv run pytest tests/
+
+      - name: bot login
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Create and push tag
+        run: |
+          TAG="v${{ github.event.inputs.version }}"
+          git tag "$TAG" -m "Release $TAG"
+          git push origin "$TAG"
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: v${{ github.event.inputs.version }}
+          name: v${{ github.event.inputs.version }}
+          generate_release_notes: true
+          files: dist/*

stuntdouble-2.0.1/.gitignore

@@ -0,0 +1,75 @@
+# macOS
+.DS_Store
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+*.pyc
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+.claude
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Unit test / coverage reports
+htmlcov/
+htmlcov*/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+coverage*.xml
+coverage.json
+junit_results.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+*.xml
+
+# Virtual environments
+venv/
+ENV/
+env/
+.venv/
+.env
+
+# IDEs
+.idea/
+.vscode/
+.cursor/
+*.swp
+*.swo
+*~
+
+# MyPy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Ruff
+.ruff_cache/
+
+# Logs
+*.log
+

stuntdouble-2.0.1/CHANGELOG.md

@@ -0,0 +1,19 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## 0.1.0
+
+Initial public release.
+
+### Features
+
+- Per-invocation tool mocking via `MockToolsRegistry`
+- Fluent mock builder API (`registry.mock("tool").returns(...)`)
+- Data-driven mock factory with JSON scenario files
+- Input matching with operator-based predicates
+- Dynamic value resolution with placeholders
+- Call recording for test assertions
+- Mock signature validation against real tool schemas
+- MCP tool mirroring (auto-discover and mock MCP server tools)
+- LangGraph ToolNode integration via `create_mockable_tool_wrapper`

stuntdouble-2.0.1/CLAUDE.md

@@ -0,0 +1,31 @@
+# StuntDouble
+
+Tool mocking framework for AI agent testing, built for LangGraph.
+
+## Build & Test
+
+```bash
+uv sync                          # Install deps
+uv run pytest                    # Run unit tests
+uv run pytest tests-e2e/         # Run e2e tests
+uv run ruff check .              # Lint
+uv run ruff format .             # Format
+uv run mypy src/                 # Type check
+```
+
+## Package Structure
+
+- `src/stuntdouble/` — single flat namespace, all public exports in `__init__.py`
+- `src/stuntdouble/mirroring/` — MCP tool mirroring subsystem
+- `tests/` — unit tests
+- `tests-e2e/` — end-to-end tests
+- `docs/` — Sphinx documentation
+
+## Conventions
+
+- Line length: 120 (ruff)
+- Python: 3.11+
+- Build: hatchling
+- Package manager: uv
+- All public API exported from `stuntdouble.__init__`
+- No subpackage public APIs (import from `stuntdouble`, not `stuntdouble.X`)

stuntdouble-2.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **stuntdouble@proton.me**. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

stuntdouble-2.0.1/CONTRIBUTING.md

@@ -0,0 +1,80 @@
+Contribution Guidelines
+=======================
+
+Great to have you here! Whether it's improving documentation, adding a new component, or reporting a bug, all contributions are welcome!
+
+Please note that this project is released with a [Code of Conduct](./CODE_OF_CONDUCT.md). By participating, you agree to abide by its terms.
+
+- [Contribution Expectations](#contribution-expectations)
+- [Contribution Process](#contribution-process)
+- [After Contribution is Merged](#after-contribution-is-merged)
+- [Contact Information](#contact-information)
+
+## Contribution Expectations
+
+#### Adding Functionality or Reporting Bugs
+* Browse [open issues](https://github.com/stuntdouble/stuntdouble/issues) to find something to work on, or open a new issue to report a bug or suggest a feature.
+* Bug reports should include as much detail as possible: logs, stacktraces, Python version, OS, and steps to reproduce.
+
+#### Code Quality Expectations
+- **Tests**: All new code should have corresponding unit tests (pytest)
+- **Coverage**: Ensure that code coverage meets or exceeds 80%
+- **Documentation**: Code should be well-documented. What code is doing should be self-explanatory based on coding conventions. Why code is doing something should be explained:
+	* Python code should have docstrings (Google style)
+	* `pyproject.toml` should have comments for non-obvious settings
+	* Unit tests should have clear names and docstrings
+	* Integration tests should document their scenarios
+- **Code Style**: We follow PEP 8 conventions. Use `ruff` for formatting and linting. Run `uv run ruff check .` and `uv run ruff format --check .` to check compliance
+
+#### Review SLAs
+- Pull request reviews are targeted within 48 hours
+- Maintainers will support contributors through code guidance and contribution recognition
+
+## Contribution Process
+
+**All contributions should be done through a fork.**
+
+1. **Fork and Clone.** From the GitHub UI, fork the project into your user space. Then clone locally and add the upstream remote:
+	```sh
+	git clone git@github.com:YOUR_USERNAME/stuntdouble.git
+	cd stuntdouble
+	git remote add upstream git@github.com:stuntdouble/stuntdouble.git
+	```
+
+1. **Create a branch.** Use a descriptive name prefixed with `feature/` or `bugfix/` and the issue number:
+	```sh
+	git checkout -b feature/123-add-conditional-matching
+	```
+
+1. **Make your changes**, including documentation. Writing good commit logs is important. Follow the [Local Development](./README.md#getting-started-with-local-development) steps to get started.
+	```text
+	A commit log should describe what changed and why.
+	Reference the GitHub issue number in the commit message (e.g., "Fixes #123").
+	```
+
+1. **Test.** Bug fixes and features **should come with tests** and coverage should meet or exceed 80%. Make sure all tests pass. Please do not submit patches that fail this check.
+
+1. **Push your changes** to your fork's branch. Use `git rebase` (not `git merge`) to sync your work from time to time:
+   ```sh
+   git fetch upstream
+   git rebase upstream/main
+   git push origin name-of-your-branch
+   ```
+
+1. **Open a Pull Request** to the upstream repository. On your forked repo, click the "Pull Request" button and fill out the form.
+1. A PR will automatically trigger CI checks against your changes.
+1. Maintainers will review and may request changes or ask questions.
+
+## After Contribution is Merged
+
+Once the PR is approved, a maintainer will merge it and you'll be credited as a contributor. New releases are published to PyPI periodically -- check the [CHANGELOG](./CHANGELOG.md) for release notes.
+
+## License
+
+By contributing to StuntDouble, you agree that your contributions will be licensed under the [MIT License](./LICENSE).
+
+## Contact Information
+
+* Need to get in contact with the maintainers? The best people to start with are the project [code owners](https://github.com/stuntdouble/stuntdouble/blob/main/CODEOWNERS).
+* Open a [GitHub Discussion](https://github.com/stuntdouble/stuntdouble/discussions) for questions or ideas.
+* File a [GitHub Issue](https://github.com/stuntdouble/stuntdouble/issues) for bugs or feature requests.

stuntdouble-2.0.1/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2024 StuntDouble Contributors
+
+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.
+