ai2rules-harness 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -3,18 +3,22 @@
|
|
|
3
3
|
**Govern a local coding agent in one command.**
|
|
4
4
|
|
|
5
5
|
```bash
|
|
6
|
-
|
|
6
|
+
npm install -g ai2rules-harness
|
|
7
|
+
harness init
|
|
7
8
|
```
|
|
8
9
|
|
|
9
10
|
That writes a governance manifest, a `PreToolUse` shim, and the host settings entry
|
|
10
11
|
into the current project. It is safe to run twice, it never replaces a manifest you
|
|
11
12
|
have tuned, and turning it off is one file.
|
|
12
13
|
|
|
13
|
-
> **
|
|
14
|
-
>
|
|
15
|
-
>
|
|
16
|
-
> `
|
|
17
|
-
>
|
|
14
|
+
> **Try it without installing:** `npx ai2rules-harness init` works and is the
|
|
15
|
+
> fastest way to see a verdict — but **prefer the global install for real use.**
|
|
16
|
+
> The shim records the absolute path of the binary that ran `init`, and under
|
|
17
|
+
> `npx` that path is inside npm's transient `_npx` cache. When the cache is
|
|
18
|
+
> cleaned or evicted the binary disappears, and the shim **fails open** — your
|
|
19
|
+
> tool calls go back to the host's normal permissions with no error. That is the
|
|
20
|
+
> correct behaviour for a missing kernel and the wrong place to be surprised by
|
|
21
|
+
> it. After a global install, re-run `harness init` to re-bake the stable path.
|
|
18
22
|
|
|
19
23
|
## What it does
|
|
20
24
|
|
|
@@ -54,10 +58,12 @@ looks like.
|
|
|
54
58
|
Effective on the very next tool call, no restart:
|
|
55
59
|
|
|
56
60
|
```bash
|
|
57
|
-
touch
|
|
58
|
-
touch ~/.claude/gate-off
|
|
61
|
+
touch ~/.claude/ai2rules/off/<your-project> # this project
|
|
62
|
+
touch ~/.claude/gate-off # everywhere
|
|
59
63
|
```
|
|
60
64
|
|
|
65
|
+
`harness init` prints the exact per-project path. Both live **outside** the
|
|
66
|
+
governed project on purpose: a switch inside it is one the agent can throw itself.
|
|
61
67
|
Delete the file to re-enable. The shim runs per call, so the toggle is immediate.
|
|
62
68
|
|
|
63
69
|
## Honest boundaries
|
package/package.json
CHANGED