toolyard 0.1.0__tar.gz

toolyard-0.1.0/.editorconfig

@@ -0,0 +1,23 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+[*.py]
+indent_size = 4
+max_line_length = 100
+
+[*.{toml,yml,yaml,json}]
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false
+max_line_length = off
+
+[Makefile]
+indent_style = tab

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

@@ -0,0 +1,136 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  format:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install ruff
+      - run: ruff format --check .
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install ruff
+      - run: ruff check .
+
+  types:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: mypy src tests
+
+  boundaries:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: lint-imports
+
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "${{ matrix.python-version }}" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m "not live and not performance" --cov --cov-report=xml
+
+  tests-314-early-warning:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.14" }
+      # Deliberately unpinned: ci.lock is resolved on 3.13, and pinning a version that has no
+      # 3.14 wheels would defeat the purpose of an early warning.
+      - run: pip install -e ".[dev]"
+      - run: pytest -m "not live and not performance"
+
+  coverage:
+    needs: [tests]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m "not live and not performance" --cov --cov-report=term-missing --cov-fail-under=95
+
+  contracts:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m contract
+
+  security:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        # gitleaks scans *history*, and `actions/checkout` fetches a single commit by default.
+        # For a push it is handed `<first-pushed>^..<last-pushed>`, so the parent of the first
+        # pushed commit has to be in the object store; in a depth-1 clone it is not, and git
+        # answers "unknown revision", which the action reports as exit code 1. It fails the same
+        # way whether or not a secret exists, so a green run would not have meant anything either.
+        with: { fetch-depth: 0 }
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install pip-audit
+      # Audit the locked sets, not the job's own environment: a bare `pip-audit` here would
+      # inspect an environment containing only pip-audit itself (Security Standards §11).
+      - run: pip-audit --require-hashes -r requirements/ci.lock
+      - run: pip-audit --require-hashes -r requirements/release.lock
+      - uses: gitleaks/gitleaks-action@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/release.lock
+      - run: python -m build --no-isolation
+      - run: twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with: { name: dist, path: dist/ }
+
+  install-check:
+    needs: [build]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - uses: actions/download-artifact@v4
+        with: { name: dist, path: dist/ }
+      - run: pip install dist/*.whl
+      - run: python -c "import toolyard"

toolyard-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,57 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*.*.*"]
+  workflow_dispatch:   # manual TestPyPI dry run; see publish-testpypi below
+
+permissions:
+  id-token: write   # required for PyPI Trusted Publishing
+  contents: write   # required to create the GitHub release
+
+jobs:
+  release:
+    # Tag pushes only. Without this, clicking "Run workflow" for the TestPyPI dry run below would
+    # also fire this job and publish to real PyPI — the exact opposite of a dry run.
+    if: github.event_name == 'push'
+    runs-on: ubuntu-latest
+    environment: pypi   # must match the Environment name set on the PyPI trusted publisher
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      # Byte-for-byte the dry run's build chain below. A real release that resolved `build` and
+      # `hatchling` fresh from PyPI would not be the artifact the dry run proved.
+      - run: pip install --require-hashes -r requirements/release.lock
+      - run: python -m build --no-isolation
+      - run: twine check dist/*
+      - run: pip install "dist/$(ls dist | grep .whl)[dev]"
+      - run: pytest -m "not live and not performance"
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true
+          files: dist/*
+
+  publish-testpypi:
+    # Manual only, via Actions -> Release -> Run workflow. Packaging and Release Standards §6
+    # requires a successful TestPyPI publish ahead of a package's first real release; 0.1.0 is
+    # this package's first published version, so run this once before tagging v0.1.0. Later
+    # releases may skip it, or use it again as a dry run.
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/release.lock
+      - run: python -m build --no-isolation
+      - run: twine check dist/*
+      - run: pip install "dist/$(ls dist | grep .whl)[dev]"
+      - run: pytest -m "not live and not performance"
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/

toolyard-0.1.0/.gitignore

@@ -0,0 +1,104 @@
+# ---- Python ----
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# ---- Packaging / build backends ----
+pip-wheel-metadata/
+share/python-wheels/
+
+# ---- Testing / coverage ----
+.pytest_cache/
+.cache
+.coverage
+.coverage.*
+coverage.xml
+*.cover
+*.py,cover
+htmlcov/
+nosetests.xml
+.hypothesis/
+
+# ---- Type checking / linting ----
+.mypy_cache/
+.dmypy.json
+dmypy.json
+.ruff_cache/
+.pytype/
+
+# ---- Virtual environments ----
+.venv/
+venv/
+ENV/
+env/
+env.bak/
+venv.bak/
+.python-version
+
+# ---- Distribution / dependency locking ----
+# requirements/*.lock is deliberately NOT ignored. The lock files are committed
+# inputs: CI and release jobs install from them with --require-hashes (Packaging
+# and Release Standards §4, Security Standards §11), so an ignored lock file
+# means a checkout that cannot build.
+
+# ---- Editors / OS ----
+.vscode/
+.idea/
+*.swp
+*.swo
+.DS_Store
+Thumbs.db
+
+# ---- Suite runtime state (this component's local data) ----
+# The application writes to XDG paths at runtime (~/.config, ~/.local/share,
+# ~/.local/state per Master Architecture §1.2), never inside the repository.
+# These entries only guard against a developer pointing XDG_* at the repo
+# during local testing.
+.local/
+.config/
+*.sqlite3
+*.sqlite3-journal
+*.sqlite3-wal
+*.sqlite3-shm
+/data/
+/logs/
+/backups/
+/artifacts/
+/exports/
+
+# ---- Secrets ----
+# Per Security Standards §8: secrets are never committed. Config files may
+# only name where a secret comes from (*_env / *_file), never the value.
+.env
+.env.*
+*.key
+*.pem
+secrets.toml
+
+# ---- Node-free JS assets (MirrorWall consumers may still use a local tool) ----
+node_modules/
+
+# ---- Build artifacts from docs generation ----
+docs/api/openapi-v1.json.tmp
+
+# ---- import-linter cache ----
+# `lint-imports` writes this on every gate run; it is a cache, never an input.
+.import_linter_cache/

toolyard-0.1.0/.importlinter

@@ -0,0 +1,132 @@
+[importlinter]
+root_package = toolyard
+include_external_packages = True
+
+[importlinter:contract:no-application-imports]
+# Master architecture §2: packages never import applications. Never weakened, never extended —
+# a package that "needs" an application type has been handed application responsibility.
+name = ToolYard must not import applications
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    freeweight
+    loadcoach
+    ideapress
+    promptcadence
+
+[importlinter:contract:no-sibling-packages]
+# Spec §5: "Nothing else — in particular not `setspec` (records are in-process values;
+# applications serialize them) and no sibling capability package." Never weakened, never extended.
+name = ToolYard must not import sibling capability packages
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    setspec
+    modelrack
+    sweatmeter
+    weightsdb
+    mirrorwall
+    cutctx
+    loadledger
+    commissioner
+    spotcheck
+
+[importlinter:contract:no-model-access]
+# Spec §3: "No model access and no provider JSON." ToolYard exports a neutral wire definition and
+# the caller adapts it; there is no client here to repurpose. Never weakened, never extended.
+#
+# allow_indirect_imports: these contracts describe what *this package's own modules* import. A
+# chain through a dependency would be that dependency's budget to answer for.
+name = ToolYard must hold no path to a model
+allow_indirect_imports = True
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    openai
+    anthropic
+    ollama
+    litellm
+    transformers
+    torch
+    huggingface_hub
+
+[importlinter:contract:no-persistence]
+# Spec §10: "Data ownership: none." The application persists records through its own
+# `ToolCallStore`; ToolYard defines the protocol and an in-memory implementation for tests.
+# Never weakened, never extended.
+name = ToolYard must touch no database
+allow_indirect_imports = True
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    sqlalchemy
+    alembic
+    sqlite3
+
+[importlinter:contract:subprocess-only-in-the-sandbox]
+# LAYERED, and written for the module that does not exist yet. ADR-0053 decision 5 and ADR-0018
+# put every process launch behind one door: the container → bwrap → refuse ladder. Phase 2 (row D1)
+# writes `toolyard.sandbox` and *that module alone* may import `subprocess`; the exemption below is
+# already here so D1 adds a module rather than editing a boundary rule.
+#
+# `unmatched_ignore_imports_alerting = none` is what lets an exemption name an import that does not
+# exist yet. It is not a weakening: any *other* module importing `subprocess` still fails.
+name = Only the sandbox may import subprocess
+allow_indirect_imports = True
+unmatched_ignore_imports_alerting = none
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    subprocess
+    multiprocessing
+    pty
+ignore_imports =
+    toolyard.sandbox -> subprocess
+
+[importlinter:contract:http-only-in-the-fetch-tool]
+# LAYERED, same shape. ADR-0053 decision 6 puts the ADR-0026 §3 checks where the socket is opened.
+# Phase 3 (row E2) writes `toolyard.tools.fetch` and *that module alone* may import `httpx`; every
+# other HTTP client stays forbidden outright, in every module, forever — a second client is a
+# second chance to omit the redirect check.
+name = Only the fetch tool may hold an HTTP client
+allow_indirect_imports = True
+unmatched_ignore_imports_alerting = none
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    httpx
+    requests
+    aiohttp
+    urllib3
+    urllib
+    http
+    socket
+    ssl
+ignore_imports =
+    toolyard.tools.fetch -> httpx
+
+[importlinter:contract:filesystem-only-where-containment-lives]
+# LAYERED. Spec §14: no argument is ever interpolated into a path. The way that is kept true is
+# that path handling exists in one place — `toolyard.containment` — which resolves before it
+# compares. Phase 2's `toolyard.sandbox` and Phase 3's `toolyard.tools.files` are the two modules
+# that join it; their exemptions are already written.
+name = Filesystem access lives only where containment does
+allow_indirect_imports = True
+unmatched_ignore_imports_alerting = none
+type = forbidden
+source_modules = toolyard
+forbidden_modules =
+    os
+    pathlib
+    shutil
+    tempfile
+    glob
+    fnmatch
+ignore_imports =
+    toolyard.containment -> pathlib
+    toolyard.containment -> os
+    toolyard.sandbox -> pathlib
+    toolyard.sandbox -> os
+    toolyard.sandbox -> shutil
+    toolyard.sandbox -> tempfile
+    toolyard.tools.files -> pathlib

toolyard-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,22 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.6.9
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-toml
+      - id: check-json
+      - id: check-added-large-files
+      - id: check-merge-conflict
+      - id: mixed-line-ending
+        args: [--fix=lf]
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.18.4
+    hooks:
+      - id: gitleaks