@mrciphersmith/keryx 0.3.37 → 0.3.39

package/README.md

@@ -502,7 +502,7 @@ What is in it today:
   run that cannot produce the evidence its flow requires does not get to claim
   it finished.
 - **Four doors.** The CLI (`keryx harness run|exec|extension|wave|replay`), JSONL/RPC
-  and the loopback HTTP entry (`keryx serve`) share one execution loop; the
+  and the loopback HTTP entry (`keryx serve`, whose `ask` decisions become approvals answered once over `/v1/approvals` or `keryx approvals`) share one execution loop; the
   interactive TUI runs its own on the same tool registry and the same policy.
 - **A record you can check.** `keryx harness run --record` writes a run's
   recomputable hash surface and `keryx harness replay` validates a fixture
@@ -920,7 +920,7 @@ untouched.
 
 | Limitation | Impact | Alternative |
 |------------|--------|-------------|
-| No remote approval transport | A remote turn whose policy decision is `ask` ends in a recorded denial | Run approval-requiring turns locally |
+| Remote approvals need a tool registry | The stock `keryx serve` registers no tools, so it raises no approvals; with a registry an `ask` becomes a pending approval answered over `/v1/approvals` or `keryx approvals` | Run tool-using turns locally |
 | Domain allowlist is macOS-only | Domain-level egress policy, credential masking and TLS termination refuse to run on Linux rather than silently doing less | Filesystem containment and network on/off work on both |
 | No bundled embedding runtime | No semantic ranking in memory search | Lexical memory search remains fully available |
 | ripgrep is external | `keryx ctx rg` needs `rg` on `PATH` | Install ripgrep, or let the agent read files directly |
@@ -977,6 +977,29 @@ repository checkout, since the evaluation corpus is not shipped in the npm
 package. See
 [run keryx in CI](docs/docs/guides/run-in-ci.md).
 
+### Review bot on pull requests
+
+A GitHub Action reviews each same-repository pull request, has a second model
+turn try to refute every finding, and posts one review with inline comments:
+
+```yaml
+- uses: MrCipherSmith/keryx@main
+  with:
+    model-api-key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+Set up the secret and copy [`docs/examples/review-bot.yml`](docs/examples/review-bot.yml)
+(`permissions: contents: read, pull-requests: write`, trigger `pull_request`, never
+`pull_request_target`). Fork pull requests are refused before any model call.
+`keryx review bot post` is a dry run until you pass `--post`; the action's
+`post: "false"` does the same. A run reviews at most `max-diff-bytes` of the diff
+(default 200,000 bytes) with one reviewer turn plus one verifier turn per finding.
+`keryx review metrics` (and `/reviews` in the shell) reports findings acted on,
+dismissed, precision and resolved-before-merge; a ratio with no data prints
+`n/a`. Metrics need the managed review packages on the machine where you run
+`keryx review complete`; the Action's runner keeps them only for the job and
+nothing uploads them. See [review as a pull request bot](docs/docs/guides/review-as-a-pr-bot.md).
+
 ## Documentation
 
 Full documentation site: **<https://mrciphersmith.github.io/keryx/>**
@@ -990,6 +1013,7 @@ Full documentation site: **<https://mrciphersmith.github.io/keryx/>**
 - **[Workspace & lifecycle](docs/docs/workspace-and-lifecycle.md)** — the `.metaproject/` contract and `init`/`update` lifecycle.
 - **[Limitations](docs/docs/limitations.md)** — known gaps, platform caveats, and what to do instead.
 - **[Shared Agent Context](docs/docs/guides/shared-agent-context.md)** *(experimental)* — local-first work-context layer: FWK overview, proposals, runtime policy guard.
+- **[Review as a pull request bot](docs/docs/guides/review-as-a-pr-bot.md)** — the GitHub Action, secrets, the same-repository rule, dry run, cost, and the precision and resolved-before-merge metrics.
 - **[Permission modes](docs/docs/guides/permission-modes.md)** — `ask`/`trust`/`auto` for the interactive shell: how to set them and exactly where the per-project default is stored.
 - **[Changelog](CHANGELOG.md)** — what has landed since `v0.1.0`.