studio-baton 0.1.0__tar.gz

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

@@ -0,0 +1,85 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_call:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: test (py${{ matrix.python }} on ${{ matrix.os }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest]
+        # 3.11 is what the openclaw gateway container runs (Debian bookworm)
+        # and 3.14 is the studio's own machine. Both are production runtimes, so
+        # neither may be left to chance.
+        python: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+        include:
+          # macOS is the other platform a studio might run this from by hand.
+          # Windows is not tested because it is not supported: the job layer is
+          # built on POSIX signals and file locking, and its first honest CI run
+          # said so out loud. See "Supported platforms" in the README.
+          - os: macos-latest
+            python: "3.12"
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+
+      - name: Install
+        run: python -m pip install --upgrade pip && pip install -e ".[dev]"
+
+      - name: Test
+        run: python -m pytest --cov=baton --cov-report=term-missing
+
+  quality:
+    name: lint and types
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install
+        run: python -m pip install --upgrade pip && pip install -e ".[dev]"
+
+      - name: Lint
+        run: python -m ruff check .
+
+      - name: Format check
+        run: python -m ruff format --check .
+
+      - name: Types
+        run: python -m mypy
+
+  leaks:
+    name: no leaked paths, secrets, or personal data
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Scan
+        run: python tools/check_leaks.py
+
+      - name: Scan history for secrets
+        uses: gitleaks/gitleaks-action@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

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

@@ -0,0 +1,77 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  # The full suite runs again against the tag. A release that ships code the
+  # tests never saw is exactly the release that breaks someone's studio.
+  verify:
+    uses: ./.github/workflows/ci.yml
+
+  build:
+    needs: verify
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build
+        run: |
+          python -m pip install --upgrade pip build
+          python -m build
+
+      - name: Check the wheel carries its data files
+        run: |
+          python -m pip install dist/*.whl
+          python - <<'PY'
+          from pathlib import Path
+          import baton
+
+          # `__file__` is None when the wheel shipped no `__init__.py` and the
+          # import resolved to a namespace package instead — which is what a
+          # mis-scoped `include` in pyproject produces: a wheel of data files
+          # with no code. Say that, rather than raising TypeError on None.
+          assert baton.__file__, "the wheel carries no Python code (namespace package)"
+          root = Path(baton.__file__).parent
+          for name in ("cli/app.py", "defaults.yaml", "locale/th.yaml",
+                       "migrations/sqlite.sql", "contracts/lesson_summary.schema.json"):
+              assert (root / name).is_file(), f"{name} missing from the wheel"
+          print("wheel contents ok")
+          PY
+
+      - name: Check the installed console script actually runs
+        run: |
+          baton --version
+          baton --help > /dev/null
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    # Off until the PyPI trusted publisher exists. Set the repository variable
+    # PUBLISH_TO_PYPI to `true` to turn it on — until then a tag still gets a
+    # verified, built artefact, and the release run stays green instead of
+    # failing on an upload nobody has authorised yet.
+    if: vars.PUBLISH_TO_PYPI == 'true'
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write        # trusted publishing; no API token to leak
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - uses: pypa/gh-action-pypi-publish@release/v1

studio_baton-0.1.0/.gitignore

@@ -0,0 +1,43 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.venv/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.coverage
+htmlcov/
+
+# Secrets and per-installation state. A profile's baton.yaml is meant to be
+# committed (to a *private* repo); the credentials beside it never are.
+.env
+*.env
+!.env.example
+secrets/
+state/
+data/
+*.db
+
+# Editor / OS
+.DS_Store
+*.swp
+.idea/
+.vscode/
+
+# Never commit these: they are what made the original workspace impossible to
+# open-source without a scrubbing pass.
+*.bak
+*.bak.*
+*.orig
+tmp/
+
+# Sidecar lock files from the atomic-write layer. They are transient and
+# occasionally survive a killed process; they must never be committed.
+*.lock
+
+# Local-only review workspace. This repo is public; the review notes track
+# known defects before they are fixed and stay on the machine.
+/review/

studio_baton-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Studio Baton 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.