@hiveai/cli 0.9.10 → 0.9.11

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 CHANGED
@@ -51,6 +51,7 @@ haive memory add \
51
51
  haive enforce status
52
52
  haive enforce check --stage pre-commit
53
53
  haive enforce ci
54
+ haive benchmark report --dir benchmarks/agent-benchmark
54
55
  ```
55
56
 
56
57
  ---
@@ -113,6 +114,7 @@ haive enforce status # show whether the repo is protected
113
114
  haive enforce check --stage local # local policy gate
114
115
  haive enforce check --stage pre-push # used by Git hooks
115
116
  haive enforce ci # used by required CI checks
117
+ haive enforce cleanup # remove generated .ai runtime/cache artifacts
116
118
  ```
117
119
 
118
120
  Strict mode checks for:
@@ -120,7 +122,23 @@ Strict mode checks for:
120
122
  - a recent hAIve briefing marker before local write workflows
121
123
  - recent session recap before push/CI gates
122
124
  - stale important memories anchored to changed code
125
+ - decision coverage: changed files must have their relevant anchored policies surfaced in the latest briefing
123
126
  - known anti-patterns from validated gotchas/decisions
127
+ - visible generated artifacts such as `.ai/.runtime`, `.ai/.cache`, or Python bytecode
128
+
129
+ `haive enforce check` prints an enforcement score and fails strict gates when the score drops below the configured threshold.
130
+
131
+ ### `haive benchmark`
132
+
133
+ Turn hAIve-vs-plain agent trials into a repeatable demo/report.
134
+
135
+ ```bash
136
+ haive benchmark demo
137
+ haive benchmark report --dir benchmarks/agent-benchmark
138
+ haive benchmark report --dir benchmarks/agent-benchmark --out RESULTS.md
139
+ ```
140
+
141
+ The report summarizes agent effort from `BENCHMARK_AGENT_REPORT.md` files: commands, files read, files modified, test iterations, terminal failures, decision mentions, token proxy, and whether hAIve memory shaped the outcome.
124
142
 
125
143
  ### `haive run`
126
144