@mrciphersmith/keryx 0.3.52 → 0.3.53

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mrciphersmith/keryx",
-  "version": "0.3.52",
+  "version": "0.3.53",
   "description": "Version-controlled project context for AI coding agents: code graph, architecture wiki, project memory, relevant tests, quality signals, and task flows.",
   "private": false,
   "publishConfig": {

package/src/gdskills/bundled/skills/core/reviewer-skill-creator/SKILL.detail.md

@@ -203,14 +203,14 @@ imported: 3 overwritten: 0 updated: 0 skipped: 1 would-import: 0 would-overwrite
 
 A reviewer that cites `<dir>/<name>.mdc` reads `.metaproject/rules/project/<dir>/<name>.mdc` when that file exists,
 and `.metaproject/rules/<dir>/<name>.mdc` otherwise. `keryx init`, `keryx update` and `keryx skills install` overwrite
-rules/core with keryx's own rules and leave rules/project alone. `keryx review reviewers` lists each such reference
-under `shadowedRules`.
+rules/core with keryx's own rules (the manifest form of `skills install` skips files it has no record of) and leave
+rules/project alone. `keryx review reviewers` lists each such reference under `shadowedRules`.
 
 Reviewers: `keryx review reviewers` must list every imported review/* name. That is the same call review-orchestrator makes.
 ```
 
-The note's "`keryx skills install` overwrite rules/core" is true of one of its
-two forms. **`keryx init`, `keryx update` and the legacy-profile form of
+The note's "`keryx skills install` overwrite rules/core" is true of the legacy
+profile form; the manifest form skips files it has no record of (below). **`keryx init`, `keryx update` and the legacy-profile form of
 `keryx skills install`** (`--profile minimal|recommended|full|custom` with no
 manifest flag) copy keryx's rules over `rules/core`. The manifest form with
 `--target keryx-shell` also writes `rules/core`, but skips an existing file its
@@ -281,7 +281,8 @@ reports one status:
   and the project has no file for yet; the overlay's goes to
   `.metaproject/rules/project/core/<name>.mdc` rather than to `rules/core`,
   because `keryx init`, `keryx update` and the legacy-profile
-  `keryx skills install` overwrite `rules/core` with keryx's own rules.
+  `keryx skills install` overwrite `rules/core` with keryx's own rules (the
+  manifest form skips files it has no record of).
 - `unresolved` — no `rules/` directory beside the source has it. Add the file by
   hand, or the reviewer keeps citing a rule the project lacks.
 
@@ -674,10 +675,11 @@ $ keryx review reviewers
 - review-acme-api: `vendor/acme-overlay/skills/review-acme-api/SKILL.md` changed since 2026-09-30T15:49:48.204Z
 …
 $ keryx skills update review/review-acme-api --dry-run
+# skills update
 …
-## would import (1) — dry run, nothing written
+## would update (1) — dry run, nothing written
 
-- review/review-acme-api (overwrites the existing one)
+- review/review-acme-api
 …
 $ keryx skills update review/review-acme-api
 …

package/src/gdskills/bundled/skills/core/reviewer-skill-creator/SKILL.md

@@ -17,7 +17,6 @@ triggers:
   - "make a reviewer from this profile"
   - "создай ревьюера"
   - "создай нового ревьюера на основании"
-  - "import vantage reviewers"
   - "import overlay reviewers"
 metadata:
   author: "MrCipherSmith"

package/src/gdskills/bundled/skills/orchestration/flow-orchestrator/SKILL.md

@@ -631,7 +631,7 @@ keryx flow complete <id>
 
 Completion is allowed only after the PR merge has been confirmed. The merge
 target must be the base branch captured when the flow was created; do not
-silently retarget or close against another branch. Flows created since the owner gate fail completion while no owner is set (`keryx flow owner set <id> --owner "<name>" --reason "<why>"`); `ac confirm` and `flow complete` append a signature — `--signed-by "<name>"` names the signer, otherwise `KERYX_ACTOR` or the local git identity is recorded, as a claim. A flow created with `--require-confirmation` needs one more gate — `--confirm-token <token>` from `keryx flow confirm <id>`, a short-lived single-use token minted by a typed challenge in a terminal; it proves an interactive step ran outside the agent's tool roster, not that a human ran it. A flow left stuck in `completing` by a crash or interrupted attempt (never a normal gate failure) recovers with `keryx flow recover <id> --reason "<why>"`.
+silently retarget or close against another branch. The flow folder is committed in the same PR as the code; the commit at closing is a rule to follow, not one the gate checks. `flow complete` fails the `folder-committed` gate while the flow's `flow.json` is not in `HEAD` (flows created from 0.3.53 on; commit it with `git add .metaproject/flows/<dir> && git commit`, then run `flow complete` again). `flow init` and `flow renumber` avoid numbers used on known remote branches, and `keryx flow check` reports a clash with a remote branch (repair with `keryx flow renumber <dir> --to <free id> --reason "<why>"`) and warns about a folder that is not committed. Flows created since the owner gate fail completion while no owner is set (`keryx flow owner set <id> --owner "<name>" --reason "<why>"`); `ac confirm` and `flow complete` append a signature — `--signed-by "<name>"` names the signer, otherwise `KERYX_ACTOR` or the local git identity is recorded, as a claim. A flow created with `--require-confirmation` needs one more gate — `--confirm-token <token>` from `keryx flow confirm <id>`, a short-lived single-use token minted by a typed challenge in a terminal; it proves an interactive step ran outside the agent's tool roster, not that a human ran it. A flow left stuck in `completing` by a crash or interrupted attempt (never a normal gate failure) recovers with `keryx flow recover <id> --reason "<why>"`.
 
 If gates fail, the CLI returns the flow to `in-progress`. Add a journal note,
 create fix tasks, and repeat Phase 2.

package/src/gdskills/bundled/skills/review/review-orchestrator/SKILL.detail.md

@@ -240,10 +240,9 @@ What to expect from the exit code:
   skills catalog and gdskills module manifest for the `full` profile. It sets
   exit 1 only when `.metaproject/` is absent; a destination it will not write
   through (a symlink, a non-directory) is listed under `Warnings` with exit 0.
-- **The dry-run's `Apply this plan:` hint is not the whole command.** It prints
-  only `--profile` and `--target`, so after a dry-run with
-  `--with capability:mobx` the hinted command installs the profile without
-  `code-mobx-store-review`. Re-type the command you dry-ran, minus `--dry-run`.
+- **The dry-run's `Apply this plan:` hint is the whole command.** It repeats
+  every plan-shaping flag (`--with`, `--without`, `--include-deprecated`,
+  `--target`, `--profile`), so run it as printed.
 
 Run `keryx review reviewers --json` again afterwards and dispatch from what it
 returns.