harnessweaver-cli 0.7.1__tar.gz

harnessweaver_cli-0.7.1/.gitignore

@@ -0,0 +1,40 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.pyright/
+.hypothesis/
+.coverage
+.coverage.*
+htmlcov/
+
+# TypeScript
+node_modules/
+typescript/**/dist/
+*.tsbuildinfo
+
+# Docs site
+site/
+
+# HarnessWeaver local run state (baselines under .harness/baselines are committed per example)
+.harness/state.db
+.harness/dev/
+*.db-journal
+
+# Editors and OS
+.DS_Store
+.idea/
+.vscode/
+
+# Claude Code local files
+.claude/
+
+# Secrets
+.env
+.env.*
+!.env.example

harnessweaver_cli-0.7.1/CHANGELOG.md

@@ -0,0 +1,82 @@
+# Changelog: harnessweaver-cli
+
+All notable changes to the `harnessweaver` command and its project templates. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this package uses [Semantic Versioning](https://semver.org/) on its own (RULES V1). Versions before 0.7.1 were never published; their Git tags (`harnessweaver-cli@<version>`) mark the commit where each one landed.
+
+## [Unreleased]
+
+## 0.7.1 - 2026-11-01
+
+The first version published to PyPI.
+
+### Added
+
+- The package ships the Apache-2.0 `LICENSE` in its wheel and sdist.
+
+## 0.7.0 - 2026-11-01
+
+### Added
+
+- `harnessweaver sidecar --max-body-bytes`: the largest request body harnessd reads, 10 MiB by default.
+
+## 0.6.2 - 2026-11-01
+
+### Security
+
+- `spec diff git:<ref>:<path>` read profiles from the working tree, so a pull request that weakened only a profile showed no difference. A `git:` side is now loaded from that ref's own tree, the ref can't be read as a git option, and the diff lists profile layers added and removed.
+
+## 0.6.1 - 2026-10-25
+
+### Fixed
+
+- The `chat` template's terminal app ends the chat at the end of input (Ctrl-D, or piped input running out) instead of raising `EOFError`.
+
+## 0.6.0 - 2026-10-20
+
+### Added
+
+- `harnessweaver gateway litellm` writes a LiteLLM Proxy config from the spec (gateway models, aliases, retries, a timeout from the longest deadline, message logging off, the `otel` callback, and a tool-permission guardrail that allows only tools whose manifests need no run), and `harnessweaver gateway mcp` writes the neutral `tool-allow-list` for an MCP gateway: each allowed tool's server, digest and scopes, and every withheld tool with its reason (ADR-0039).
+- `harnessweaver dev [--up]` writes a local Compose stack into `.harness/dev/` (LiteLLM, an OpenTelemetry collector, Langfuse and harnessd, digest-pinned and on 127.0.0.1 only) with local secrets generated once into `.env`, and starts it.
+
+## 0.5.0 - 2026-10-20
+
+### Added
+
+- `harnessweaver sidecar [SPEC]` runs harnessd.
+
+## 0.4.0 - 2026-10-20
+
+### Added
+
+- `harnessweaver add guard` adds a guard in shadow mode (`mode: log_only`, R8), and `harnessweaver add tool` writes a tool manifest from a function's signature and Google-style docstring and adds its directory to `tools.manifests`. Both edit `harness.yaml` with its comments kept (ruamel.yaml, ADR-0016), and a guard whose edit doesn't load is taken back out.
+- `harnessweaver tools pin` writes each manifest's `definition_digest` (S2); `--tool` pins one.
+- `harnessweaver plugin new <namespace>` scaffolds a standalone plugin package (entry point, `hw.Plugin`, a sample `<namespace>.banned_words` guard, and tests whose `pytest` run includes the conformance suite), and `harnessweaver plugin list` shows installed plugins with their versions, contract ranges and compatibility.
+- Project templates `rag`, `agent` (a Pydantic AI agent with governed tools and a red-team eval set), `workflow` and `chat`, each passing its own tests offline (T6).
+
+### Changed
+
+- `harnessweaver init` refuses template names starting with `_`, which are scaffolds for other commands.
+
+## 0.3.0 - 2026-10-20
+
+### Added
+
+- `harnessweaver eval run` (baselines in `.harness/baselines/<task>.<suite>.json`, `--update-baseline`, the shadow-guard report; exit 1 on a missed threshold or a regression, 2 when the suites can't run) and `harnessweaver eval report` (online samples).
+- `harnessweaver policy test` checks a table of calls against `Harness.authorize` (`policy_tests.yaml`; exit 1 on a mismatch, 2 when the tests can't run).
+- `harnessweaver replay <run_id>` runs a recorded run again against the current code and spec (exit 1 when the status or output changed).
+
+### Changed
+
+- The extraction template's offline overlay answers every golden case, so `harnessweaver eval run -e offline` passes on it, and it tests its golden set.
+
+## 0.2.0 - 2026-10-19
+
+### Added
+
+- `harnessweaver doctor` warns about tool manifests without a pinned digest (printing the digest to pin) and fails ones that changed since they were pinned.
+
+## 0.1.0 - 2026-10-18
+
+### Added
+
+- The `harnessweaver` command with `init` (built-in and plugin templates), `spec validate`, `spec explain`, `spec diff` (either side can be `git:<ref>:<path>`), `doctor` (level and next steps, reachable hooks, duplicate retry owners, unpinned profiles, shadow guards, content capture), `hooks`, `test` (offline, test mode on) and `contracts export`.
+- The `extraction` project template, whose output passes its own tests (T6).

harnessweaver_cli-0.7.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Muthu Kumaran R
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

harnessweaver_cli-0.7.1/PKG-INFO

@@ -0,0 +1,83 @@
+Metadata-Version: 2.5
+Name: harnessweaver-cli
+Version: 0.7.1
+Summary: Developer tooling for HarnessWeaver: the harnessweaver command.
+Author-email: Muthu Kumaran R <rsmk7new@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,ai,governance,guardrails,harness,llm,observability
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: harnessweaver>=0.1.0
+Requires-Dist: rich>=15
+Requires-Dist: ruamel-yaml>=0.18
+Requires-Dist: typer>=0.27
+Description-Content-Type: text/markdown
+
+# harnessweaver-cli
+
+Developer tooling for [HarnessWeaver](../../README.md). Installs the `harnessweaver` command. The full reference, with every option and exit code, is [docs/cli.md](../../docs/cli.md).
+
+```bash
+uv add --dev harnessweaver-cli
+harnessweaver --help
+```
+
+## Start a project
+
+```bash
+harnessweaver init invoice-bot              # the extraction template; -t picks another
+cd invoice-bot
+harnessweaver spec validate --env offline   # load it the way the app will
+harnessweaver test                          # its tests, offline
+```
+
+`init` copies a template and puts the project name in it; there is no template
+language. A plugin's templates are named `<namespace>.<template>`
+(`harnessweaver init -t acme.rag`). Every template's output passes its own tests
+(RULES T6).
+
+| Template | What you get |
+| --- | --- |
+| `extraction` (default) | Typed extraction with schema validation, one repair, PII and secrets guards, a golden set |
+| `rag` | A session flow that routes the question, retrieves ACL-checked passages and answers with citations the output guard checks |
+| `agent` | A Pydantic AI agent with two governed tools, one of them approval-gated, a policy rule and a red-team eval set |
+| `workflow` | A three-stage step graph: a parallel stage, then a reply in an evaluator-optimizer loop |
+| `chat` | A chat turn with memory, a topic guard and a streamed answer moderated chunk by chunk |
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `init [DIR] [-t TEMPLATE] [--name NAME] [--force]` | Start a project: `harness.yaml`, an offline overlay, code, a prompt, evals and tests. Never overwrites without `--force` |
+| `spec validate [SPEC] [-e ENV] [--format text\|json]` | Load the spec with every check the app runs: layers, locks, bounds, plugins, tasks, reachable hooks (R4). Prints the adoption level |
+| `spec explain [SPEC] [--path PREFIX]` | Every effective value, the layer it came from, and its locks and bounds |
+| `spec diff BEFORE AFTER [--exit-code]` | Compare two effective specs as Markdown, for PR comments. Either side can be `git:<ref>:<path>`, read with the profiles committed at that ref |
+| `doctor [SPEC] [--strict]` | Adoption level and what the next level needs, hooks each task's runner reaches, duplicate retry owners (R5), unpinned profiles, shadow guards (R8), content capture (R9), plugin installation problems. Exits 1 on a failure, or on a warning with `--strict` |
+| `hooks [SPEC] [--task TASK]` | The middleware on every hook point in the order it runs, with band, fail mode and timeout |
+| `test [-e ENV] [PYTEST ARGS...]` | Run the app's tests with `HARNESSWEAVER_TEST_MODE=1` and the `offline` overlay |
+| `contracts export [DIR] [--check]` | Write the JSON Schema of every contract, or report drift |
+| `eval run [SPEC] [--suite NAME] [--task TASK] [--update-baseline]` | Run the spec's eval suites, compare with `.harness/baselines`, print the shadow-guard report. Exits 1 on a missed threshold or a regression, 2 when the suites can't run |
+| `eval report [SPEC] [--task TASK]` | The production runs online evals sampled and graded |
+| `policy test [SPEC] [--cases FILE]` | Check a table of tool calls (`policy_tests.yaml`) against the governor's verdicts, as a dry run |
+| `replay RUN_ID [SPEC]` | Run a recorded run again against the current code and spec, and show what changed |
+| `add guard USE [SPEC] [--stage S] [--id ID] [--action A] [--set KEY=VALUE]` | Add a guard in shadow mode (`mode: log_only`, R8). Comments in `harness.yaml` are kept; an edit that doesn't load is taken back |
+| `add tool MODULE:FUNCTION [SPEC] [--dir tools] [--risk R] [--side-effect S]` | Write a tool manifest from the function's signature and docstring, and add its directory to `tools.manifests` |
+| `tools pin [SPEC] [--tool NAME]` | Write each manifest's `definition_digest`, so a tool that changes unreviewed is blocked (S2) |
+| `plugin new NAMESPACE [DIR]` | Scaffold a standalone plugin package with a sample guard and tests that run the conformance suite |
+| `plugin list [--format text\|json]` | Installed plugins: namespace, distribution, version, contract range, compatibility |
+| `sidecar [SPEC] [-e ENV] [--host H] [--port P] [--token-env VAR]` | Serve the spec to other languages: runs `harnessd` (needs `harnessweaver-sidecar` and a token, S6) |
+| `gateway litellm [SPEC] [-o FILE]` | A LiteLLM Proxy config from the spec: gateway models and aliases, retries, a timeout, no message logging, and a tool-permission guardrail from the manifests |
+| `gateway mcp [SPEC] [-o FILE]` | A neutral tool allow-list for an MCP gateway: each allowed tool's server, digest and scopes, and the withheld tools with the reason |
+| `dev [SPEC] [-e ENV] [--up]` | Write `.harness/dev/`: LiteLLM, an OTel collector, Langfuse and harnessd in a Compose file, wired to the spec, with local secrets in `.env`. `--up` starts it |
+
+Every command that takes `SPEC` defaults to `harness.yaml`, takes
+`--profile-dir` to find `org://` profiles, and makes the spec's directory
+importable, as it is when the app runs from there.

harnessweaver_cli-0.7.1/README.md

@@ -0,0 +1,60 @@
+# harnessweaver-cli
+
+Developer tooling for [HarnessWeaver](../../README.md). Installs the `harnessweaver` command. The full reference, with every option and exit code, is [docs/cli.md](../../docs/cli.md).
+
+```bash
+uv add --dev harnessweaver-cli
+harnessweaver --help
+```
+
+## Start a project
+
+```bash
+harnessweaver init invoice-bot              # the extraction template; -t picks another
+cd invoice-bot
+harnessweaver spec validate --env offline   # load it the way the app will
+harnessweaver test                          # its tests, offline
+```
+
+`init` copies a template and puts the project name in it; there is no template
+language. A plugin's templates are named `<namespace>.<template>`
+(`harnessweaver init -t acme.rag`). Every template's output passes its own tests
+(RULES T6).
+
+| Template | What you get |
+| --- | --- |
+| `extraction` (default) | Typed extraction with schema validation, one repair, PII and secrets guards, a golden set |
+| `rag` | A session flow that routes the question, retrieves ACL-checked passages and answers with citations the output guard checks |
+| `agent` | A Pydantic AI agent with two governed tools, one of them approval-gated, a policy rule and a red-team eval set |
+| `workflow` | A three-stage step graph: a parallel stage, then a reply in an evaluator-optimizer loop |
+| `chat` | A chat turn with memory, a topic guard and a streamed answer moderated chunk by chunk |
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `init [DIR] [-t TEMPLATE] [--name NAME] [--force]` | Start a project: `harness.yaml`, an offline overlay, code, a prompt, evals and tests. Never overwrites without `--force` |
+| `spec validate [SPEC] [-e ENV] [--format text\|json]` | Load the spec with every check the app runs: layers, locks, bounds, plugins, tasks, reachable hooks (R4). Prints the adoption level |
+| `spec explain [SPEC] [--path PREFIX]` | Every effective value, the layer it came from, and its locks and bounds |
+| `spec diff BEFORE AFTER [--exit-code]` | Compare two effective specs as Markdown, for PR comments. Either side can be `git:<ref>:<path>`, read with the profiles committed at that ref |
+| `doctor [SPEC] [--strict]` | Adoption level and what the next level needs, hooks each task's runner reaches, duplicate retry owners (R5), unpinned profiles, shadow guards (R8), content capture (R9), plugin installation problems. Exits 1 on a failure, or on a warning with `--strict` |
+| `hooks [SPEC] [--task TASK]` | The middleware on every hook point in the order it runs, with band, fail mode and timeout |
+| `test [-e ENV] [PYTEST ARGS...]` | Run the app's tests with `HARNESSWEAVER_TEST_MODE=1` and the `offline` overlay |
+| `contracts export [DIR] [--check]` | Write the JSON Schema of every contract, or report drift |
+| `eval run [SPEC] [--suite NAME] [--task TASK] [--update-baseline]` | Run the spec's eval suites, compare with `.harness/baselines`, print the shadow-guard report. Exits 1 on a missed threshold or a regression, 2 when the suites can't run |
+| `eval report [SPEC] [--task TASK]` | The production runs online evals sampled and graded |
+| `policy test [SPEC] [--cases FILE]` | Check a table of tool calls (`policy_tests.yaml`) against the governor's verdicts, as a dry run |
+| `replay RUN_ID [SPEC]` | Run a recorded run again against the current code and spec, and show what changed |
+| `add guard USE [SPEC] [--stage S] [--id ID] [--action A] [--set KEY=VALUE]` | Add a guard in shadow mode (`mode: log_only`, R8). Comments in `harness.yaml` are kept; an edit that doesn't load is taken back |
+| `add tool MODULE:FUNCTION [SPEC] [--dir tools] [--risk R] [--side-effect S]` | Write a tool manifest from the function's signature and docstring, and add its directory to `tools.manifests` |
+| `tools pin [SPEC] [--tool NAME]` | Write each manifest's `definition_digest`, so a tool that changes unreviewed is blocked (S2) |
+| `plugin new NAMESPACE [DIR]` | Scaffold a standalone plugin package with a sample guard and tests that run the conformance suite |
+| `plugin list [--format text\|json]` | Installed plugins: namespace, distribution, version, contract range, compatibility |
+| `sidecar [SPEC] [-e ENV] [--host H] [--port P] [--token-env VAR]` | Serve the spec to other languages: runs `harnessd` (needs `harnessweaver-sidecar` and a token, S6) |
+| `gateway litellm [SPEC] [-o FILE]` | A LiteLLM Proxy config from the spec: gateway models and aliases, retries, a timeout, no message logging, and a tool-permission guardrail from the manifests |
+| `gateway mcp [SPEC] [-o FILE]` | A neutral tool allow-list for an MCP gateway: each allowed tool's server, digest and scopes, and the withheld tools with the reason |
+| `dev [SPEC] [-e ENV] [--up]` | Write `.harness/dev/`: LiteLLM, an OTel collector, Langfuse and harnessd in a Compose file, wired to the spec, with local secrets in `.env`. `--up` starts it |
+
+Every command that takes `SPEC` defaults to `harness.yaml`, takes
+`--profile-dir` to find `org://` profiles, and makes the spec's directory
+importable, as it is when the app runs from there.

harnessweaver_cli-0.7.1/pyproject.toml

@@ -0,0 +1,35 @@
+[build-system]
+requires = ["hatchling>=1.32"]
+build-backend = "hatchling.build"
+
+[project]
+name = "harnessweaver-cli"
+version = "0.7.1"
+description = "Developer tooling for HarnessWeaver: the harnessweaver command."
+readme = "README.md"
+license = "Apache-2.0"
+authors = [{ name = "Muthu Kumaran R", email = "rsmk7new@gmail.com" }]
+requires-python = ">=3.12"
+keywords = ["ai", "llm", "harness", "guardrails", "agents", "governance", "observability"]
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Software Development :: Libraries :: Application Frameworks",
+    "Typing :: Typed",
+]
+dependencies = [
+    "harnessweaver>=0.1.0",
+    "typer>=0.27",
+    "rich>=15",
+    "ruamel-yaml>=0.18",
+]
+
+[project.scripts]
+harnessweaver = "harnessweaver_cli.main:app"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/harnessweaver_cli"]

harnessweaver_cli-0.7.1/src/harnessweaver_cli/__init__.py

@@ -0,0 +1,7 @@
+"""Developer tooling for HarnessWeaver: the ``harnessweaver`` command."""
+
+from importlib.metadata import version as _version
+
+__version__: str = _version("harnessweaver-cli")
+
+__all__ = ["__version__"]

harnessweaver_cli-0.7.1/src/harnessweaver_cli/_load.py

@@ -0,0 +1,119 @@
+"""Finding and loading specs for the CLI, including ``git:<ref>:<path>`` sources."""
+
+import io
+import subprocess
+import sys
+import tarfile
+import tempfile
+from pathlib import Path
+
+import typer
+
+from harnessweaver import Harness
+from harnessweaver.core.errors import HarnessError, SpecError
+from harnessweaver.core.ports import StateStore
+from harnessweaver.spec import EffectiveSpec, load_spec
+
+__all__ = ["fail", "load_effective", "load_harness", "spec_path"]
+
+DEFAULT_SPEC = Path("harness.yaml")
+
+
+def fail(error: HarnessError | str, code: int = 1) -> typer.Exit:
+    """Print an error the way every command does and return the exit to raise.
+
+    Commands that report checks (``eval run``, ``policy test``, ``replay``) exit 1
+    when a check fails and 2 when they can't run, so CI can tell the two apart.
+    """
+    message = error.message if isinstance(error, HarnessError) else error
+    typer.echo(f"error: {message}", err=True)
+    return typer.Exit(code=code)
+
+
+def spec_path(path: Path | None, code: int = 1) -> Path:
+    """The spec to load. Its directory becomes importable, as when the app runs from
+    there, so ``tasks.*.input`` and handler paths resolve."""
+    found = path or DEFAULT_SPEC
+    if not found.is_file():
+        raise fail(f"no spec at {found}; pass the path to harness.yaml", code)
+    directory = str(found.resolve().parent)
+    if directory not in sys.path:
+        sys.path.insert(0, directory)
+    return found
+
+
+def load_harness(
+    path: Path | None,
+    env: str | None,
+    profile_dirs: list[Path],
+    *,
+    state: StateStore | None = None,
+    code: int = 1,
+) -> Harness:
+    """Load and build the harness, the same way an app does (every check runs).
+    ``state`` replaces the spec's state store (evals keep their runs in memory)."""
+    try:
+        effective = load_spec(spec_path(path, code), env=env, profile_dirs=profile_dirs)
+        return Harness.from_spec(effective, state=state)
+    except HarnessError as exc:
+        raise fail(exc, code) from None
+
+
+def _git(*args: str) -> bytes | None:
+    """Run git and return its output, or ``None`` if it fails or isn't installed."""
+    try:
+        done = subprocess.run(["git", *args], capture_output=True, check=False)
+    except OSError:
+        return None
+    return done.stdout if done.returncode == 0 else None
+
+
+def _load_from_git(ref: str, raw_path: str, env: str | None, dirs: list[Path]) -> EffectiveSpec:
+    """Load a spec as it stands at ``ref``, with the profiles that were committed with it.
+
+    The whole tree at the ref is extracted, so ``.harness/profiles`` and file references come
+    from the ref and not the working tree: otherwise a pull request that weakens only a
+    profile would show no difference. A ``--profile-dir`` inside the repository is read from
+    the ref too. One outside it, like ``HARNESSWEAVER_PROFILE_PATH``, isn't in git, so both
+    sides of a diff see the same files.
+
+    Raises:
+        SpecError: If the ref or the path can't be read.
+    """
+    missing = SpecError(f"can't read {raw_path} at {ref} from git")
+    # --end-of-options keeps a ref from being read as an option of git's.
+    commit = _git("rev-parse", "--verify", "--quiet", "--end-of-options", f"{ref}^{{commit}}")
+    top = _git("rev-parse", "--show-toplevel")
+    if commit is None or top is None:
+        raise missing
+    root = Path(top.decode().strip()).resolve()
+    archive = _git("-C", str(root), "archive", "--format=tar", commit.decode().strip())
+    if archive is None:
+        raise missing
+
+    def inside(tree: Path, path: Path) -> Path | None:
+        """Where ``path`` is in the extracted tree, if it's in the repository at all."""
+        resolved = path.resolve()
+        return tree / resolved.relative_to(root) if resolved.is_relative_to(root) else None
+
+    with tempfile.TemporaryDirectory(prefix="harnessweaver-git-") as temporary:
+        tree = Path(temporary).resolve()
+        with tarfile.open(fileobj=io.BytesIO(archive)) as tar:
+            tar.extractall(tree, filter="data")  # the data filter refuses paths out of the tree
+        path = inside(tree, Path(raw_path))
+        if path is None or not path.is_file():
+            raise missing
+        return load_spec(path, env=env, profile_dirs=[inside(tree, d) or d for d in dirs])
+
+
+def load_effective(source: str, env: str | None, profile_dirs: list[Path]) -> EffectiveSpec:
+    """Load a spec from a file, or from git as ``git:<ref>:<path>`` (for ``spec diff`` in CI)."""
+    try:
+        if not source.startswith("git:"):
+            return load_spec(spec_path(Path(source)), env=env, profile_dirs=profile_dirs)
+        ref, _, raw_path = source.removeprefix("git:").partition(":")
+        if not ref or not raw_path:
+            raise SpecError(f"{source!r} must look like git:<ref>:<path>")
+        return _load_from_git(ref, raw_path, env, profile_dirs)
+    except HarnessError as exc:
+        raise fail(exc) from None