harness-detect 0.2.0__tar.gz

harness_detect-0.2.0/.gitignore

@@ -0,0 +1,287 @@
+# BEGIN genignore
+# Generated by genignore. Do not edit between these markers.
+# Providers: macos,python
+# Provenance: github/gitignore@3780fff86c705155792fb3e1787cebd6281ba8cf [macos,python]
+# General
+.DS_Store
+.localized
+__MACOSX/
+.AppleDouble
+.LSOverride
+Icon[
+
+# Resource forks
+._*
+
+# Files and directories that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+.com.apple.timemachine.supported
+.PKInstallSandboxManager
+.PKInstallSandboxManager-SystemSoftware
+.hotfiles.btree
+.vol
+.file
+.disk_label*
+lost+found
+.HFS+ Private Directory Data[
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+# Mac OS 6 to 9
+Desktop DB
+Desktop DF
+TheFindByContentFolder
+TheVolumeSettingsFolder
+.FBCIndex
+.FBCSemaphoreFile
+.FBCLockFolder
+
+# Quota system
+.quota.group
+.quota.user
+.quota.ops.group
+.quota.ops.user
+
+# TimeMachine
+Backups.backupdb
+.MobileBackups
+.MobileBackups.trash
+MobileBackups.trash
+tmbootpicker.efi
+
+# 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
+*.lcov
+.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/*
+!.pixi/config.toml
+
+# 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
+.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
+
+.env
+.env.*
+!.env.example
+!.env.ci
+.envrc
+# END genignore

harness_detect-0.2.0/AGENTS.md

@@ -0,0 +1,113 @@
+# AGENTS.md
+
+## Project Overview
+
+`harness-detect` is a Python port of the `@auron-labs/harness-detect` Node package,
+the Go package at `github.com/auron/harness-detect/packages/golang/harnessdetect`, and the
+`harness-detect` Rust crate. It detects installed LLM harnesses and resolves
+their config/state paths from a bundled JSON registry.
+
+- Package entrypoint: `src/harness_detect/__init__.py`
+- Canonical registry: `packages/data/harnesses.json`
+- Bundled registry copy: `src/harness_detect/data/harnesses.json`
+- Tests: `tests/test_behavior.py`
+- Package metadata: `pyproject.toml`
+
+## Source-Of-Truth Files
+
+- Package code and exported API: `src/harness_detect/__init__.py`
+- Canonical harness matrix data: `packages/data/harnesses.json`
+- Bundled harness matrix copy: `src/harness_detect/data/harnesses.json`
+- TypeScript harness matrix copy: `packages/typescript/data/harnesses.json`
+- Go embedded harness matrix copy: `packages/golang/harnessdetect/data/harnesses.json`
+- Rust embedded harness matrix copy: `packages/rust/data/harnesses.json`
+- Behavior checks: `tests/test_behavior.py`
+- Package metadata: `pyproject.toml`
+
+## Commands
+
+See [../../docs/maintainers.md](../../docs/maintainers.md) for the full
+command reference, the registry editing procedure, and change-aware
+validation. Package-specific commands (run from `packages/python`):
+
+| Purpose | Command |
+|---|---|
+| Install dev deps | `uv sync --dev` |
+| Run tests | `uv run pytest` |
+| Lint | `uv run ruff check .` |
+| Format check | `uv run ruff format --check .` |
+| Format apply | `uv run ruff format .` |
+| Build wheel | `uv build` |
+
+There is no root `pyproject.toml`; always `cd` into `packages/python` first.
+
+## Working Rules
+
+- Keep the package dependency-free at runtime. The only runtime dependency is
+  the Python standard library (`json`, `os`, `pathlib`, `re`, `importlib`).
+  Do not add runtime dependencies without a clear reason.
+- Prefer editing `packages/data/harnesses.json` over adding harness-specific
+  code paths in `__init__.py`.
+- `__init__.py` should stay generic: compute effective roots, expand
+  templates, check executables, return results. No `if key == "codex"`
+  branches.
+- Preserve the current API unless the user asks for a breaking change:
+  - `get_raw_harness_data()`
+  - `get_harness_matrix()`
+  - `list_harnesses()`
+  - `get_harness_support(input)`
+  - `list_harness_support()`
+  - `check_harness(input, options=None)`
+  - `detect_harnesses(options=None)`
+  - `detect_installed_harnesses(options=None)`
+- Raw-registry APIs, `list_harnesses()`, and detection results that embed a
+  full harness definition now expose required `support` metadata wherever they
+  expose registry harness entries.
+- `support` is descriptive only. Detection still depends on executable matches
+  and existing resolved `paths[]` entries.
+- The repo is still unpublished, so prefer a clean aligned API/schema over
+  compatibility-only layers. Keep registry `version: 1` unless internal
+  tooling truly requires a bump.
+
+## Matrix Editing
+
+See [../../docs/maintainers.md](../../docs/maintainers.md) for the
+registry editing rules and post-edit verification. Package-specific
+notes:
+
+- `paths[].template` supports `${...}` placeholders resolved by
+  `_with_defaults()` + `_resolve_harness_roots()` in `__init__.py`.
+- Use derived roots like `${CODEX_ROOT}` or `${GEMINI_ROOT}` when overrides
+  affect default locations; avoid hardcoding `${HOME}/...` when the harness
+  has a documented root override.
+- After editing the canonical registry, run `mise run registry:sync`, then
+  `mise run registry:check`. Do not hand-edit or manually copy derived package
+  registries.
+
+## Testing
+
+- The tests in `tests/test_behavior.py` mirror the TypeScript, Go, and Rust
+  suites: matrix readability, byte-for-byte sync with the canonical registry,
+  alias lookup, env overrides, derived roots, project (`${CWD}`) resolution,
+  executable detection (including Windows `PATHEXT`), unresolved-placeholder
+  semantics, platform gating, and basic registry schema validation.
+- Registry sync changes should also be validated with `bun test` in
+  `packages/typescript`, `go test ./...` in `packages/golang`, and
+  `cargo test` in `packages/rust` because all package copies must stay
+  aligned with `packages/data/harnesses.json`.
+
+## Known Pitfalls
+
+- `packages/data/harnesses.json` is the canonical registry, but the Python
+  package bundles `src/harness_detect/data/harnesses.json` and reads it at
+  load time via `importlib.resources`; keep that copy, plus the TypeScript,
+  Go, and Rust copies, byte-for-byte aligned after registry edits. The
+  `test_bundled_data_matches_shared_file` test asserts this.
+- The registry uses Node.js platform names (`darwin`, `linux`, `win32`).
+  `_current_platform()` in `__init__.py` maps `sys.platform` to this
+  convention.
+- The package uses `importlib.resources` to locate the bundled JSON, so the
+  `data/harnesses.json` file must be included in the wheel build (handled by
+  the `force-include` config in `pyproject.toml`).
+- Detection is intentionally evidence-based: a harness can count as installed
+  from either an executable match or existing config/state paths.

harness_detect-0.2.0/CHANGELOG.md

@@ -0,0 +1,8 @@
+# Changelog
+
+## [0.2.0](https://github.com/auron-labs/harness-detect/compare/python-v0.1.0...python-v0.2.0) (2026-07-16)
+
+
+### Features
+
+* init ([76f30f3](https://github.com/auron-labs/harness-detect/commit/76f30f31a2d4940e6e075c5974e03dc167d75619))

harness_detect-0.2.0/PKG-INFO

@@ -0,0 +1,66 @@
+Metadata-Version: 2.4
+Name: harness-detect
+Version: 0.2.0
+Summary: Detect installed LLM harnesses and resolve their config/state paths from a JSON registry.
+Project-URL: Repository, https://github.com/auron/harness-detect
+Project-URL: Issues, https://github.com/auron/harness-detect/issues
+Author: Auron
+License-Expression: MIT
+Keywords: claude,codex,detect,gemini,harness,llm
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: System :: Filesystems
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# harness-detect (Python)
+
+Detect installed LLM harnesses (Codex, Claude Code, Gemini CLI, Cursor, and many
+others) and resolve their config/state/install paths from a shared JSON
+registry.
+
+This is the Python port of `@auron-labs/harness-detect`. It shares the same harness
+registry as the TypeScript, Go, and Rust packages and exposes the same API
+surface, adapted to idiomatic Python naming.
+
+## Installation
+
+```sh
+pip install harness-detect
+```
+
+Supported distribution targets are npm (`@auron-labs/harness-detect`), Go modules (`github.com/auron/harness-detect/packages/golang/harnessdetect`, released by `packages/golang/vX.Y.Z` tags), crates.io (`harness-detect`), and PyPI (`harness-detect`). Before the first public release for an ecosystem, these install commands are the intended consumer coordinates and may not resolve yet.
+
+## Usage
+
+```python
+from harness_detect import detect_installed_harnesses, CheckOptions
+
+for r in detect_installed_harnesses(CheckOptions()):
+    print(r.key, r.reasons)
+```
+
+Support metadata is also available:
+
+```python
+from harness_detect import get_harness_support, list_harness_support
+
+codex = get_harness_support("codex")
+print(codex.support.config.global_.status)
+print(len(list_harness_support()))
+```
+
+## Exported API
+
+- `get_raw_harness_data()` returns the full registry object.
+- `get_harness_matrix()` returns the full registry object.
+- `list_harnesses()` returns the registry's harness definitions.
+- `get_harness_support(input)` returns support metadata for one harness key or alias.
+- `list_harness_support()` returns support metadata for every harness.
+- `check_harness(input, options=None)` checks one harness key or alias.
+- `detect_harnesses(options=None)` checks every registry entry.
+- `detect_installed_harnesses(options=None)` returns only installed harnesses.
+
+See the [package docs](https://github.com/auron/harness-detect) for the full
+API reference.

harness_detect-0.2.0/README.md

@@ -0,0 +1,50 @@
+# harness-detect (Python)
+
+Detect installed LLM harnesses (Codex, Claude Code, Gemini CLI, Cursor, and many
+others) and resolve their config/state/install paths from a shared JSON
+registry.
+
+This is the Python port of `@auron-labs/harness-detect`. It shares the same harness
+registry as the TypeScript, Go, and Rust packages and exposes the same API
+surface, adapted to idiomatic Python naming.
+
+## Installation
+
+```sh
+pip install harness-detect
+```
+
+Supported distribution targets are npm (`@auron-labs/harness-detect`), Go modules (`github.com/auron/harness-detect/packages/golang/harnessdetect`, released by `packages/golang/vX.Y.Z` tags), crates.io (`harness-detect`), and PyPI (`harness-detect`). Before the first public release for an ecosystem, these install commands are the intended consumer coordinates and may not resolve yet.
+
+## Usage
+
+```python
+from harness_detect import detect_installed_harnesses, CheckOptions
+
+for r in detect_installed_harnesses(CheckOptions()):
+    print(r.key, r.reasons)
+```
+
+Support metadata is also available:
+
+```python
+from harness_detect import get_harness_support, list_harness_support
+
+codex = get_harness_support("codex")
+print(codex.support.config.global_.status)
+print(len(list_harness_support()))
+```
+
+## Exported API
+
+- `get_raw_harness_data()` returns the full registry object.
+- `get_harness_matrix()` returns the full registry object.
+- `list_harnesses()` returns the registry's harness definitions.
+- `get_harness_support(input)` returns support metadata for one harness key or alias.
+- `list_harness_support()` returns support metadata for every harness.
+- `check_harness(input, options=None)` checks one harness key or alias.
+- `detect_harnesses(options=None)` checks every registry entry.
+- `detect_installed_harnesses(options=None)` returns only installed harnesses.
+
+See the [package docs](https://github.com/auron/harness-detect) for the full
+API reference.

harness_detect-0.2.0/pyproject.toml

@@ -0,0 +1,37 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "harness-detect"
+version = "0.2.0"
+description = "Detect installed LLM harnesses and resolve their config/state paths from a JSON registry."
+readme = "README.md"
+license = "MIT"
+requires-python = ">=3.10"
+authors = [
+    { name = "Auron" },
+]
+keywords = ["llm", "harness", "detect", "codex", "claude", "gemini"]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: OS Independent",
+    "Topic :: System :: Filesystems",
+]
+
+[project.urls]
+Repository = "https://github.com/auron/harness-detect"
+Issues = "https://github.com/auron/harness-detect/issues"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/harness_detect"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"src/harness_detect/data/harnesses.json" = "harness_detect/data/harnesses.json"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0",
+    "ruff>=0.6",
+]