grudge-cli 0.1.1__tar.gz → 0.1.3__tar.gz

{grudge_cli-0.1.1 → grudge_cli-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: grudge-cli
-Version: 0.1.1
+Version: 0.1.3
 Summary: Deterministic regression scars for agent mistakes.
 Author: Grudge contributors
 License: MIT
@@ -29,14 +29,21 @@ Agent failures are often buried in long, provider-dependent transcripts that are
 
 ## 30-second quickstart
 
-Use Python 3.14.0 or another interpreter supported by `pyproject.toml`, then run
-the complete offline demo from the repository root:
+Install the local Guard in a repository, then verify it:
+
+```powershell
+npx grudge-cli@latest setup
+npx grudge-cli@latest doctor
+```
+
+For the complete Python offline demo, use Python 3.14.0 or another interpreter
+supported by `pyproject.toml`, then run:
 
 ```bash
 pip install -e . && grudge demo
 ```
 
-The command opens the local viewer and plays the five-beat story: capture the
+The demo opens the local viewer and plays the five-beat story: capture the
 vulnerable run, shrink its world, synthesize a predicate, prove red-on-bad and
 green-on-fixed admission, then reintroduce the bug and block it. The demo is
 offline and deterministic: it uses checked-in fake tools, scripted policies,
@@ -45,6 +52,42 @@ the public network. For a headless smoke run, use
 `python -m grudge demo --no-browser --fast --json`. For the two-session
 Claude-style hook proof, use `python -m grudge demo --guard --json`.
 
+## Published packages
+
+Grudge CLI `0.1.1` is published in both public package registries. Release
+`0.1.2` is prepared locally but has not been published yet:
+
+- **npm:** [`grudge-cli`](https://www.npmjs.com/package/grudge-cli)
+- **PyPI:** [`grudge-cli`](https://pypi.org/project/grudge-cli/)
+
+Install the Python CLI with:
+
+```bash
+python -m pip install grudge-cli
+grudge --help
+```
+
+Both packages install a command named `grudge`. The Python package exposes the
+full engine (`capture`, `compile`, `shrink`, `admit`, `run`, and `demo`); the npm
+package exposes the local Node Guard (`setup`, `doctor`, `hook`, `propose`,
+`scars`, `stats`, `report`, and `statusline`).
+
+Install the Node.js setup wizard with:
+
+```bash
+npx grudge-cli@latest setup
+```
+
+The setup wizard detects supported agent tools, lets you select agents with
+arrow keys and Space, and asks whether to configure the current repository,
+personal settings, or all projects.
+
+When PowerShell strips DSL quotes, pass the rule on stdin instead:
+
+```powershell
+'never call shell where command ~ "GRUDGE_TEST"' | grudge propose --rule-stdin --why "harmless test rule" --preventive
+```
+
 ### Install the local guard
 
 These commands exercise the checkout's Node package from the repository root;
@@ -316,5 +359,6 @@ docker run --rm grudge:latest
 - [Documentation index](docs/INDEX.md) — every documentation file and owner phase.
 - [Roadmap](docs/roadmap.md) — every deferred stub and its design notes.
 - [Demo guide](docs/demo-guide.md) — presenter, server, JSON, and shell operation.
+- [Walkthrough test](TEST.md) — scratch-directory Guard walkthrough and release checks.
 - [Pitch artifacts](pitch/one_liner.md) — one-liner, 90-second script, and slides.
 - [Progress tracker](Progress.md) — canonical phase status.

grudge_cli-0.1.1/grudge_cli.egg-info/PKG-INFO → grudge_cli-0.1.3/README.md

@@ -1,24 +1,3 @@
-Metadata-Version: 2.2
-Name: grudge-cli
-Version: 0.1.1
-Summary: Deterministic regression scars for agent mistakes.
-Author: Grudge contributors
-License: MIT
-Requires-Python: <3.15,>=3.11
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: pydantic==2.12.5
-Requires-Dist: typer==0.15.1
-Requires-Dist: click==8.1.8
-Requires-Dist: rich==13.9.4
-Requires-Dist: httpx==0.28.1
-Provides-Extra: dev
-Requires-Dist: pytest==8.3.4; extra == "dev"
-Requires-Dist: pytest-cov==6.0.0; extra == "dev"
-Requires-Dist: hypothesis==6.123.10; extra == "dev"
-Requires-Dist: ruff==0.14.14; extra == "dev"
-Requires-Dist: mypy==1.18.2; extra == "dev"
-
 # Grudge
 
 **Agents repeat mistakes. Grudge makes each one happen exactly once.**
@@ -27,49 +6,92 @@ Requires-Dist: mypy==1.18.2; extra == "dev"
 
 Agent failures are often buried in long, provider-dependent transcripts that are difficult to reproduce. A copied transcript can show what happened, but it cannot show whether the live policy would make the same decision when the world changes. Grudge turns one failure into a small, reviewable regression Scar that can run offline and block the same behavior from returning.
 
-## 30-second quickstart
-
-Use Python 3.14.0 or another interpreter supported by `pyproject.toml`, then run
-the complete offline demo from the repository root:
-
-```bash
-pip install -e . && grudge demo
-```
-
-The command opens the local viewer and plays the five-beat story: capture the
-vulnerable run, shrink its world, synthesize a predicate, prove red-on-bad and
-green-on-fixed admission, then reintroduce the bug and block it. The demo is
-offline and deterministic: it uses checked-in fake tools, scripted policies,
-the checked-in Scar, and the fallback predicate; it does not call a provider or
-the public network. For a headless smoke run, use
-`python -m grudge demo --no-browser --fast --json`. For the two-session
-Claude-style hook proof, use `python -m grudge demo --guard --json`.
-
-### Install the local guard
-
-These commands exercise the checkout's Node package from the repository root;
-they do not resolve a package from the npm registry:
-
-```bash
-npm --prefix packages/grudge run build
-npm --prefix packages/grudge run setup:repo
-npm --prefix packages/grudge run doctor:repo
-```
-
-If `grudge` has been published, run the interactive registry setup with
-`npx grudge-cli setup`. Use the arrow keys to move, Space to select agents, and
-Enter to confirm the agent and scope choices. When working from `packages/grudge`, use `node dist/grudge.mjs`
-and add `--cwd ../..` when the hooks should target the repository root. The
-short package-directory commands are `npm run setup:repo` and
-`npm run doctor:repo`. Do not combine `cd packages/grudge` with the
-root-relative path `packages/grudge/dist/grudge.mjs`, or it resolves to
-`packages/grudge/packages/grudge/dist/grudge.mjs`.
+## 30-second quickstart
+
+Install the local Guard in a repository, then verify it:
+
+```powershell
+npx grudge-cli@latest setup
+npx grudge-cli@latest doctor
+```
+
+For the complete Python offline demo, use Python 3.14.0 or another interpreter
+supported by `pyproject.toml`, then run:
+
+```bash
+pip install -e . && grudge demo
+```
+
+The demo opens the local viewer and plays the five-beat story: capture the
+vulnerable run, shrink its world, synthesize a predicate, prove red-on-bad and
+green-on-fixed admission, then reintroduce the bug and block it. The demo is
+offline and deterministic: it uses checked-in fake tools, scripted policies,
+the checked-in Scar, and the fallback predicate; it does not call a provider or
+the public network. For a headless smoke run, use
+`python -m grudge demo --no-browser --fast --json`. For the two-session
+Claude-style hook proof, use `python -m grudge demo --guard --json`.
+
+## Published packages
+
+Grudge CLI `0.1.1` is published in both public package registries. Release
+`0.1.2` is prepared locally but has not been published yet:
+
+- **npm:** [`grudge-cli`](https://www.npmjs.com/package/grudge-cli)
+- **PyPI:** [`grudge-cli`](https://pypi.org/project/grudge-cli/)
+
+Install the Python CLI with:
+
+```bash
+python -m pip install grudge-cli
+grudge --help
+```
+
+Both packages install a command named `grudge`. The Python package exposes the
+full engine (`capture`, `compile`, `shrink`, `admit`, `run`, and `demo`); the npm
+package exposes the local Node Guard (`setup`, `doctor`, `hook`, `propose`,
+`scars`, `stats`, `report`, and `statusline`).
+
+Install the Node.js setup wizard with:
+
+```bash
+npx grudge-cli@latest setup
+```
+
+The setup wizard detects supported agent tools, lets you select agents with
+arrow keys and Space, and asks whether to configure the current repository,
+personal settings, or all projects.
+
+When PowerShell strips DSL quotes, pass the rule on stdin instead:
+
+```powershell
+'never call shell where command ~ "GRUDGE_TEST"' | grudge propose --rule-stdin --why "harmless test rule" --preventive
+```
+
+### Install the local guard
+
+These commands exercise the checkout's Node package from the repository root;
+they do not resolve a package from the npm registry:
+
+```bash
+npm --prefix packages/grudge run build
+npm --prefix packages/grudge run setup:repo
+npm --prefix packages/grudge run doctor:repo
+```
+
+If `grudge` has been published, run the interactive registry setup with
+`npx grudge-cli setup`. Use the arrow keys to move, Space to select agents, and
+Enter to confirm the agent and scope choices. When working from `packages/grudge`, use `node dist/grudge.mjs`
+and add `--cwd ../..` when the hooks should target the repository root. The
+short package-directory commands are `npm run setup:repo` and
+`npm run doctor:repo`. Do not combine `cd packages/grudge` with the
+root-relative path `packages/grudge/dist/grudge.mjs`, or it resolves to
+`packages/grudge/packages/grudge/dist/grudge.mjs`.
 
 Claude Code is the verified **Guard** tier. Codex, Gemini CLI, GitHub Copilot,
 OpenCode, and Windsurf are **Advisory** integrations; Cursor is unverified and
 the installer writes no Cursor files. See [the integration matrix](docs/integrations.md).
-Use `node packages/grudge/dist/grudge.mjs setup --dry-run` to inspect a plan and
-`node packages/grudge/dist/grudge.mjs uninstall` to remove Grudge-managed files.
+Use `node packages/grudge/dist/grudge.mjs setup --dry-run` to inspect a plan and
+`node packages/grudge/dist/grudge.mjs uninstall` to remove Grudge-managed files.
 
 ## What the shrink shows
 
@@ -258,63 +280,64 @@ python scripts/generate_trace.py --steps 40 --output artifacts/phase12/trace.jso
 It does not time shrinking or aggregate measurements automatically; benchmark
 rows must be captured from a clean run and recorded with their environment.
 
-## Checks and reproducibility
-
-The default supported runtime is Python 3.14.0, recorded in `.python-version`.
-The package supports Python 3.11 through 3.14, and the lockfile is
-`requirements.lock`. The project Makefile keeps dependencies in a local virtual
-environment:
+## Checks and reproducibility
+
+The default supported runtime is Python 3.14.0, recorded in `.python-version`.
+The package supports Python 3.11 through 3.14, and the lockfile is
+`requirements.lock`. The project Makefile keeps dependencies in a local virtual
+environment:
 
 ```bash
 make install
-make test
-make lint
-make typecheck
-make docs-check
-make all
-```
-
-### Clean Linux commands
-
-From a fresh checkout, the shortest reproducible workflow is:
-
-```bash
-git clone https://github.com/harshithKumar12/Grudge.git
-cd Grudge
-# Debian/Ubuntu only, if Python reports that ensurepip is unavailable:
-# sudo apt-get install python3.14-venv
-python3.14 --version
-make PYTHON=python3.14 install
-make test
-make demo
-```
-
-The host prerequisites are Python 3.14 with its `venv` module and GNU Make.
-Node.js 18+ is optional for the JavaScript package tests; the Python tests and
-demo do not require Node.js.
-
-`make test` runs the Python suite and the Node package suite when Node.js 18+
-is installed; it remains usable on a Python-only machine. The headless proof
-is useful in CI:
-
-```bash
-.venv/bin/python -m grudge demo --guard --json
-```
-
-The offline path needs no API keys or real personal data. Copy `.env.example`
-only when experimenting with the optional provider boundary; never commit a
-key. Docker remains an optional reproducibility path:
-
-```bash
-docker build -t grudge:latest .
-docker run --rm grudge:latest
-```
+make test
+make lint
+make typecheck
+make docs-check
+make all
+```
+
+### Clean Linux commands
+
+From a fresh checkout, the shortest reproducible workflow is:
+
+```bash
+git clone https://github.com/harshithKumar12/Grudge.git
+cd Grudge
+# Debian/Ubuntu only, if Python reports that ensurepip is unavailable:
+# sudo apt-get install python3.14-venv
+python3.14 --version
+make PYTHON=python3.14 install
+make test
+make demo
+```
+
+The host prerequisites are Python 3.14 with its `venv` module and GNU Make.
+Node.js 18+ is optional for the JavaScript package tests; the Python tests and
+demo do not require Node.js.
+
+`make test` runs the Python suite and the Node package suite when Node.js 18+
+is installed; it remains usable on a Python-only machine. The headless proof
+is useful in CI:
+
+```bash
+.venv/bin/python -m grudge demo --guard --json
+```
+
+The offline path needs no API keys or real personal data. Copy `.env.example`
+only when experimenting with the optional provider boundary; never commit a
+key. Docker remains an optional reproducibility path:
+
+```bash
+docker build -t grudge:latest .
+docker run --rm grudge:latest
+```
 
 ## Repository guide
 
 - [Architecture](docs/architecture.md) — contracts and pipeline boundaries.
 - [Documentation index](docs/INDEX.md) — every documentation file and owner phase.
 - [Roadmap](docs/roadmap.md) — every deferred stub and its design notes.
-- [Demo guide](docs/demo-guide.md) — presenter, server, JSON, and shell operation.
+- [Demo guide](docs/demo-guide.md) — presenter, server, JSON, and shell operation.
+- [Walkthrough test](TEST.md) — scratch-directory Guard walkthrough and release checks.
 - [Pitch artifacts](pitch/one_liner.md) — one-liner, 90-second script, and slides.
 - [Progress tracker](Progress.md) — canonical phase status.

grudge_cli-0.1.1/README.md → grudge_cli-0.1.3/grudge_cli.egg-info/PKG-INFO

@@ -1,3 +1,24 @@
+Metadata-Version: 2.2
+Name: grudge-cli
+Version: 0.1.3
+Summary: Deterministic regression scars for agent mistakes.
+Author: Grudge contributors
+License: MIT
+Requires-Python: <3.15,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic==2.12.5
+Requires-Dist: typer==0.15.1
+Requires-Dist: click==8.1.8
+Requires-Dist: rich==13.9.4
+Requires-Dist: httpx==0.28.1
+Provides-Extra: dev
+Requires-Dist: pytest==8.3.4; extra == "dev"
+Requires-Dist: pytest-cov==6.0.0; extra == "dev"
+Requires-Dist: hypothesis==6.123.10; extra == "dev"
+Requires-Dist: ruff==0.14.14; extra == "dev"
+Requires-Dist: mypy==1.18.2; extra == "dev"
+
 # Grudge
 
 **Agents repeat mistakes. Grudge makes each one happen exactly once.**
@@ -8,47 +29,90 @@ Agent failures are often buried in long, provider-dependent transcripts that are
 
 ## 30-second quickstart
 
-Use Python 3.14.0 or another interpreter supported by `pyproject.toml`, then run
-the complete offline demo from the repository root:
+Install the local Guard in a repository, then verify it:
+
+```powershell
+npx grudge-cli@latest setup
+npx grudge-cli@latest doctor
+```
+
+For the complete Python offline demo, use Python 3.14.0 or another interpreter
+supported by `pyproject.toml`, then run:
 
 ```bash
 pip install -e . && grudge demo
 ```
 
-The command opens the local viewer and plays the five-beat story: capture the
+The demo opens the local viewer and plays the five-beat story: capture the
 vulnerable run, shrink its world, synthesize a predicate, prove red-on-bad and
 green-on-fixed admission, then reintroduce the bug and block it. The demo is
 offline and deterministic: it uses checked-in fake tools, scripted policies,
 the checked-in Scar, and the fallback predicate; it does not call a provider or
-the public network. For a headless smoke run, use
-`python -m grudge demo --no-browser --fast --json`. For the two-session
-Claude-style hook proof, use `python -m grudge demo --guard --json`.
+the public network. For a headless smoke run, use
+`python -m grudge demo --no-browser --fast --json`. For the two-session
+Claude-style hook proof, use `python -m grudge demo --guard --json`.
+
+## Published packages
+
+Grudge CLI `0.1.1` is published in both public package registries. Release
+`0.1.2` is prepared locally but has not been published yet:
+
+- **npm:** [`grudge-cli`](https://www.npmjs.com/package/grudge-cli)
+- **PyPI:** [`grudge-cli`](https://pypi.org/project/grudge-cli/)
+
+Install the Python CLI with:
+
+```bash
+python -m pip install grudge-cli
+grudge --help
+```
+
+Both packages install a command named `grudge`. The Python package exposes the
+full engine (`capture`, `compile`, `shrink`, `admit`, `run`, and `demo`); the npm
+package exposes the local Node Guard (`setup`, `doctor`, `hook`, `propose`,
+`scars`, `stats`, `report`, and `statusline`).
+
+Install the Node.js setup wizard with:
+
+```bash
+npx grudge-cli@latest setup
+```
+
+The setup wizard detects supported agent tools, lets you select agents with
+arrow keys and Space, and asks whether to configure the current repository,
+personal settings, or all projects.
+
+When PowerShell strips DSL quotes, pass the rule on stdin instead:
+
+```powershell
+'never call shell where command ~ "GRUDGE_TEST"' | grudge propose --rule-stdin --why "harmless test rule" --preventive
+```
 
 ### Install the local guard
 
-These commands exercise the checkout's Node package from the repository root;
-they do not resolve a package from the npm registry:
-
-```bash
-npm --prefix packages/grudge run build
-npm --prefix packages/grudge run setup:repo
-npm --prefix packages/grudge run doctor:repo
-```
-
-If `grudge` has been published, run the interactive registry setup with
-`npx grudge-cli setup`. Use the arrow keys to move, Space to select agents, and
-Enter to confirm the agent and scope choices. When working from `packages/grudge`, use `node dist/grudge.mjs`
-and add `--cwd ../..` when the hooks should target the repository root. The
-short package-directory commands are `npm run setup:repo` and
-`npm run doctor:repo`. Do not combine `cd packages/grudge` with the
-root-relative path `packages/grudge/dist/grudge.mjs`, or it resolves to
-`packages/grudge/packages/grudge/dist/grudge.mjs`.
+These commands exercise the checkout's Node package from the repository root;
+they do not resolve a package from the npm registry:
+
+```bash
+npm --prefix packages/grudge run build
+npm --prefix packages/grudge run setup:repo
+npm --prefix packages/grudge run doctor:repo
+```
+
+If `grudge` has been published, run the interactive registry setup with
+`npx grudge-cli setup`. Use the arrow keys to move, Space to select agents, and
+Enter to confirm the agent and scope choices. When working from `packages/grudge`, use `node dist/grudge.mjs`
+and add `--cwd ../..` when the hooks should target the repository root. The
+short package-directory commands are `npm run setup:repo` and
+`npm run doctor:repo`. Do not combine `cd packages/grudge` with the
+root-relative path `packages/grudge/dist/grudge.mjs`, or it resolves to
+`packages/grudge/packages/grudge/dist/grudge.mjs`.
 
 Claude Code is the verified **Guard** tier. Codex, Gemini CLI, GitHub Copilot,
 OpenCode, and Windsurf are **Advisory** integrations; Cursor is unverified and
 the installer writes no Cursor files. See [the integration matrix](docs/integrations.md).
-Use `node packages/grudge/dist/grudge.mjs setup --dry-run` to inspect a plan and
-`node packages/grudge/dist/grudge.mjs uninstall` to remove Grudge-managed files.
+Use `node packages/grudge/dist/grudge.mjs setup --dry-run` to inspect a plan and
+`node packages/grudge/dist/grudge.mjs uninstall` to remove Grudge-managed files.
 
 ## What the shrink shows
 
@@ -237,57 +301,57 @@ python scripts/generate_trace.py --steps 40 --output artifacts/phase12/trace.jso
 It does not time shrinking or aggregate measurements automatically; benchmark
 rows must be captured from a clean run and recorded with their environment.
 
-## Checks and reproducibility
-
-The default supported runtime is Python 3.14.0, recorded in `.python-version`.
-The package supports Python 3.11 through 3.14, and the lockfile is
-`requirements.lock`. The project Makefile keeps dependencies in a local virtual
-environment:
+## Checks and reproducibility
+
+The default supported runtime is Python 3.14.0, recorded in `.python-version`.
+The package supports Python 3.11 through 3.14, and the lockfile is
+`requirements.lock`. The project Makefile keeps dependencies in a local virtual
+environment:
 
 ```bash
 make install
-make test
-make lint
-make typecheck
-make docs-check
-make all
-```
-
-### Clean Linux commands
-
-From a fresh checkout, the shortest reproducible workflow is:
-
-```bash
-git clone https://github.com/harshithKumar12/Grudge.git
-cd Grudge
-# Debian/Ubuntu only, if Python reports that ensurepip is unavailable:
-# sudo apt-get install python3.14-venv
-python3.14 --version
-make PYTHON=python3.14 install
-make test
-make demo
-```
-
-The host prerequisites are Python 3.14 with its `venv` module and GNU Make.
-Node.js 18+ is optional for the JavaScript package tests; the Python tests and
-demo do not require Node.js.
-
-`make test` runs the Python suite and the Node package suite when Node.js 18+
-is installed; it remains usable on a Python-only machine. The headless proof
-is useful in CI:
-
-```bash
-.venv/bin/python -m grudge demo --guard --json
-```
-
-The offline path needs no API keys or real personal data. Copy `.env.example`
-only when experimenting with the optional provider boundary; never commit a
-key. Docker remains an optional reproducibility path:
-
-```bash
-docker build -t grudge:latest .
-docker run --rm grudge:latest
-```
+make test
+make lint
+make typecheck
+make docs-check
+make all
+```
+
+### Clean Linux commands
+
+From a fresh checkout, the shortest reproducible workflow is:
+
+```bash
+git clone https://github.com/harshithKumar12/Grudge.git
+cd Grudge
+# Debian/Ubuntu only, if Python reports that ensurepip is unavailable:
+# sudo apt-get install python3.14-venv
+python3.14 --version
+make PYTHON=python3.14 install
+make test
+make demo
+```
+
+The host prerequisites are Python 3.14 with its `venv` module and GNU Make.
+Node.js 18+ is optional for the JavaScript package tests; the Python tests and
+demo do not require Node.js.
+
+`make test` runs the Python suite and the Node package suite when Node.js 18+
+is installed; it remains usable on a Python-only machine. The headless proof
+is useful in CI:
+
+```bash
+.venv/bin/python -m grudge demo --guard --json
+```
+
+The offline path needs no API keys or real personal data. Copy `.env.example`
+only when experimenting with the optional provider boundary; never commit a
+key. Docker remains an optional reproducibility path:
+
+```bash
+docker build -t grudge:latest .
+docker run --rm grudge:latest
+```
 
 ## Repository guide
 
@@ -295,5 +359,6 @@ docker run --rm grudge:latest
 - [Documentation index](docs/INDEX.md) — every documentation file and owner phase.
 - [Roadmap](docs/roadmap.md) — every deferred stub and its design notes.
 - [Demo guide](docs/demo-guide.md) — presenter, server, JSON, and shell operation.
+- [Walkthrough test](TEST.md) — scratch-directory Guard walkthrough and release checks.
 - [Pitch artifacts](pitch/one_liner.md) — one-liner, 90-second script, and slides.
 - [Progress tracker](Progress.md) — canonical phase status.

{grudge_cli-0.1.1 → grudge_cli-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "grudge-cli"
-version = "0.1.1"
+version = "0.1.3"
 description = "Deterministic regression scars for agent mistakes."
 readme = "README.md"
 requires-python = ">=3.11,<3.15"