@mrciphersmith/keryx 0.3.111 → 0.3.113

package/README.md

@@ -40,7 +40,7 @@ the completion itself signed.
 
 ## Quick start
 
-**Requirements:** `git` and `bun` (>= 1.3.14 — older Bun can close the terminal input of `keryx shell`; see [onboarding](docs/docs/onboarding.md#bun-version)).
+**Requirements:** `git` (>= 2.24) and `bun` (>= 1.3.14 — older Bun can close the terminal input of `keryx shell`; see [onboarding](docs/docs/onboarding.md#bun-version)).
 
 ```bash
 npm install -g @mrciphersmith/keryx
@@ -491,7 +491,17 @@ What is in it today:
   inside a running session, decide whether that approval is asked for at all
   — `ask` (default), `trust` (safe calls run, a destructive one still asks),
   `auto` (nothing asks except a credentials-touching command, which no mode
-  ever auto-approves). A session-level layer only: `harness run`/`exec`,
+  ever auto-approves; it also answers the agent's own questions by picking the
+  recommended option and saying so, while questions about irreversible or
+  untrusted actions still ask you). The mode also sets how many model rounds one turn may
+  run: 40 in `ask`, 200 in `trust` (asks at the limit) and 200 in `auto`, where
+  reaching the limit extends the turn without asking and the turn stops at 200
+  (`KERYX_AGENT_MAX_ROUNDS` overrides all three, up to 200). A turn that
+  belongs to an **automatic review** (named in the request; the package is
+  created with `keryx review start --automatic`) gets the 200 limit in any
+  mode, runs that review's own commands without a prompt and asks only in a
+  closed list of emergencies; `review complete` and its gate are unchanged.
+  A session-level layer only: `harness run`/`exec`,
   `keryx serve`, and MCP keep the unconditional policy engine above,
   untouched. See the [permission modes guide](docs/docs/guides/permission-modes.md).
 - **Kernel-enforced containment underneath.** The OS sandbox sits *below* the
@@ -848,7 +858,7 @@ next.
 | Requirement | Status |
 |-------------|--------|
 | Bun | >= 1.3.14 |
-| Git | Required for hooks, `--changed` scopes and the managed installer; the core runs without it |
+| Git | >= 2.24 (`--end-of-options`, used wherever a typed revision reaches git). Required for hooks, `--changed` scopes and the managed installer; the core runs without it |
 | ripgrep | Required only for `keryx ctx rg` and the agent's `search_code` tool |
 | Model provider credential | Required only for the optional AI commands below |
 | macOS | Full support, including the complete policy sandbox |
@@ -1134,6 +1144,10 @@ 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).
 
+### Layers and coverage in a review
+
+Every managed review start, attach or ingest (and any `dispatch-check` or `blast-radius` given `--package`) refreshes the graph, the wiki and the memory index for the PR head and writes `layers.json`, with **no model call**; `wiki enrich` is the only model step and is never automatic (`keryx review layers refresh --package <dir> [--write-wiki]`). Blast-radius files beyond the 40-file cap are reviewed in chunks (`keryx review chunks estimate|next|record|merge`; the ceiling is 25 passes of 40 files, `reviewChunks.maxPasses` in `routing.config.json`), `keryx review coverage` counts what is covered, omitted by name, and uncovered, and `keryx review complete` refuses while a file is uncovered unless you pass `--waive-coverage "<your words>"`. `/reviews` and `/review layers` in the shell show it.
+
 ### Review bot on pull requests
 
 A GitHub Action reviews each same-repository pull request, has a second model

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,56 @@
+# Third-party notices
+
+Keryx adapts a small number of techniques from third-party works. This file
+carries the notices their licenses require. Everything else in this
+repository is covered by [LICENSE](LICENSE).
+
+## agent-skills (MIT)
+
+Source: https://github.com/addyosmani/agent-skills
+
+Techniques adapted from this skills library and re-expressed in Keryx's own
+words and mechanisms:
+
+- `src/gdskills/bundled/skills/quality/root-cause` — carrying a debugging skill.
+- `src/gdskills/bundled/skills/quality/fresh-eyes` — the in-flight doubt pass
+  (a reader gets the artifact and the contract, never the author's reasoning).
+- `src/gdskills/bundled/skills/quality/api-truth` — checking a dependency before
+  calling it and marking what went out unchecked.
+- `src/gdskills/bundled/skills/quality/deprecation-path` — carrying a
+  deprecation skill.
+- `src/gdskills/bundled/skills/quality/perf-check` — "neutral is a revert" and
+  the ledger of reverted attempts.
+- `src/gdskills/bundled/skills/planning/interviewer` — a hedged agreement is not
+  approval.
+- `src/gdskills/bundled/skills/orchestration/task-implementer` — the
+  noticed-but-not-touching / assumptions / not-touched result fields.
+- `src/review/floor.ts` — the catalogue of four test-weakening edits.
+- `src/gdskills/bundled-eval.ts` — the required skill anatomy, the length budget
+  and description discipline, made executable.
+- `src/commands/routing-corpus.ts` — the routing corpus shape (positive prompts
+  per skill, negatives naming the owner that must outrank them).
+- `docs/skills/rejected-skill-changes.md` — the rejected-change ledger.
+
+```
+MIT License
+
+Copyright (c) 2025 Addy Osmani
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```