stablemate 0.1.1__tar.gz

stablemate-0.1.1/.gitignore

@@ -0,0 +1,271 @@
+# 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
+
+.playwright-mcp
+
+.agents/*
+
+
+# A benchmark round's built repo, its run artifacts and its scorecard. Untracked for
+# three separate reasons, any one of which is sufficient — it is large (a whole app per
+# round), it is derived (re-runnable from the task module), and the built repo is its OWN
+# git repo, which is the whole point: nesting one working tree inside another is only safe
+# while the outer one cannot see it. Paddock's work and result roots live outside the tree
+# entirely (`~/.local/share/stablemate/paddock`) for the same reason; this entry stays as
+# the backstop for a round pointed at the repo by hand.
+/data/
+
+
+# Internal planning notes: maintainer paths, private-project references and
+# retired-engine prose live here by nature. The directory stays (kept by .gitkeep)
+# but its contents never ship.
+docs/plans/*
+!docs/plans/.gitkeep
+progress.md
+docs/specs
+.opencode/opencode-loop
+
+docs/backload.md
+
+# >>> farrier: QA evidence (generated) >>>
+**/qa/**/steps/
+**/qa/**/asserts/
+**/qa/**/traces/
+**/qa/**/videos/
+**/qa/**/screenshots/
+**/qa/qa-run.ndjson
+**/qa/run-manifest.json
+**/qa/qa-session.json
+# <<< farrier: QA evidence <<<
+
+# A QA round's output inside a paddock fixture app. The `docs/specs` entry above carries a
+# slash, so git anchors it to this file's own directory and it never reached the copy a round
+# writes under a fixture — the plan module, the rendered Maestro flows and the evidence are all
+# re-derivable from the task module, and the generated plan trips ruff, so an untracked round
+# fails `make lint` for everyone.
+paddock/data/apps/*/docs/specs/
+
+.agents/runs/
+.agents/worktrees/
+.agents/workflows/
+.agents/operator/
+.agents/local.compose.yaml
+.agents/agents-context.json
+.agents/agents-context.*.json
+.agents/agents.mk

stablemate-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Gabriel Côté
+
+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.

stablemate-0.1.1/PKG-INFO

@@ -0,0 +1,70 @@
+Metadata-Version: 2.5
+Name: stablemate
+Version: 0.1.1
+Summary: One install for the stablemate agent tools: the workhorse workflows, farrier and groom, at versions that work together.
+Project-URL: Homepage, https://github.com/GabrielCpp/stablemate
+Project-URL: Repository, https://github.com/GabrielCpp/stablemate
+Project-URL: Issues, https://github.com/GabrielCpp/stablemate/issues
+Author: Gabriel Côté
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agent,automation,claude,dashboard,llm,workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Utilities
+Requires-Python: >=3.12
+Requires-Dist: farrier<4,>=3
+Requires-Dist: stablemate-groom<2,>=1
+Requires-Dist: workhorse-workflows<4,>=3
+Provides-Extra: test
+Requires-Dist: packaging>=24; extra == 'test'
+Requires-Dist: pytest>=8.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+# stablemate
+
+This package installs the stablemate agent tools in one step, at versions that work together.
+It has no code and no command of its own. It depends on three distributions:
+
+| Distribution          | What you get                                                          |
+| --------------------- | --------------------------------------------------------------------- |
+| `workhorse-workflows` | The agent workflows, one command each: `workhorse-loop-runner`, `workhorse-coder` and the rest. |
+| `farrier`             | The `farrier` command, which renders the prompt library into a repository. |
+| `stablemate-groom`    | The `groom` dashboard and telemetry collector, plus `groom-sidecar`.  |
+
+## Install
+
+```bash
+uv tool install workhorse-workflows --with stablemate --with-executables-from farrier,stablemate-groom
+```
+
+You need [uv](https://docs.astral.sh/uv/) and Python 3.12 or newer.
+
+The line names `workhorse-workflows` first because uv refuses to install a package with no
+commands as a tool, and this package has none. `--with stablemate` holds all three tools to
+the major versions this package allows. `--with-executables-from` puts the `farrier` and `groom`
+commands on your PATH next to the workflow commands.
+
+Check the install:
+
+```bash
+workhorse-loop-runner run --dry-run
+farrier --help
+groom --help
+```
+
+## Versions
+
+Each release of this package allows one major version of each tool. To move all three to
+their newest release within it, run:
+
+```bash
+uv tool upgrade workhorse-workflows
+```
+
+The tools, their docs and their changelogs live in the
+[stablemate repository](https://github.com/GabrielCpp/stablemate).

stablemate-0.1.1/README.md

@@ -0,0 +1,43 @@
+# stablemate
+
+This package installs the stablemate agent tools in one step, at versions that work together.
+It has no code and no command of its own. It depends on three distributions:
+
+| Distribution          | What you get                                                          |
+| --------------------- | --------------------------------------------------------------------- |
+| `workhorse-workflows` | The agent workflows, one command each: `workhorse-loop-runner`, `workhorse-coder` and the rest. |
+| `farrier`             | The `farrier` command, which renders the prompt library into a repository. |
+| `stablemate-groom`    | The `groom` dashboard and telemetry collector, plus `groom-sidecar`.  |
+
+## Install
+
+```bash
+uv tool install workhorse-workflows --with stablemate --with-executables-from farrier,stablemate-groom
+```
+
+You need [uv](https://docs.astral.sh/uv/) and Python 3.12 or newer.
+
+The line names `workhorse-workflows` first because uv refuses to install a package with no
+commands as a tool, and this package has none. `--with stablemate` holds all three tools to
+the major versions this package allows. `--with-executables-from` puts the `farrier` and `groom`
+commands on your PATH next to the workflow commands.
+
+Check the install:
+
+```bash
+workhorse-loop-runner run --dry-run
+farrier --help
+groom --help
+```
+
+## Versions
+
+Each release of this package allows one major version of each tool. To move all three to
+their newest release within it, run:
+
+```bash
+uv tool upgrade workhorse-workflows
+```
+
+The tools, their docs and their changelogs live in the
+[stablemate repository](https://github.com/GabrielCpp/stablemate).

stablemate-0.1.1/pyproject.toml

@@ -0,0 +1,53 @@
+[project]
+name = "stablemate"
+version = "0.1.1"
+description = "One install for the stablemate agent tools: the workhorse workflows, farrier and groom, at versions that work together."
+readme = "README.md"
+requires-python = ">=3.12"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "Gabriel Côté" }]
+keywords = ["agent", "workflow", "claude", "llm", "automation", "dashboard"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Software Development :: Build Tools",
+  "Topic :: Utilities",
+]
+dependencies = [
+  "workhorse-workflows>=3,<4",
+  "farrier>=3,<4",
+  "stablemate-groom>=1,<2",
+]
+
+[project.optional-dependencies]
+test = ["pytest>=8.0", "packaging>=24"]
+
+[project.urls]
+Homepage = "https://github.com/GabrielCpp/stablemate"
+Repository = "https://github.com/GabrielCpp/stablemate"
+Issues = "https://github.com/GabrielCpp/stablemate/issues"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+bypass-selection = true
+
+[tool.hatch.build.targets.sdist]
+include = ["README.md", "LICENSE"]
+
+[tool.uv.sources]
+workhorse-workflows = { workspace = true }
+farrier = { workspace = true }
+stablemate-groom = { workspace = true }
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+filterwarnings = [
+  "error",
+]