@rayul/kordis 0.14.0 → 0.14.1

package/assets/MEMGINEERING.md

@@ -2,7 +2,7 @@
 name: memgineering
 description: Use whenever the user refers to something they told you before, asks what was decided, tells you something worth keeping, or settles something that should hold next time. The memory lives in their own folder and outlives this session; check it before answering from guesswork, and write to it when you learn something durable.
 type: skill
-version: 0.19.0
+version: 0.20.0
 ---
 
 # memgineering
@@ -68,11 +68,12 @@ never attribute a decision to somebody this conversation has not mentioned.
 
 ## The public layer
 
-`memgineering search <words>` finds one, `memgineering read <user>/<slug>`
-inlines it and `memgineering adapt <user>/<slug>` briefs you on fitting it
-here. Neither writes a file or a note, so an empty brain works from day one;
-only what this user confirms goes in. `memgineering publish <ref>` sends one
-out — dry run until `--yes`, only when they said to.
+`memgineering registry search <words>` finds one,
+`memgineering registry read <user>/<slug>` inlines it and
+`memgineering registry adapt <user>/<slug>` briefs you on fitting it here.
+Neither writes a file or a note, so an empty brain works from day one; only
+what this user confirms goes in. `memgineering registry publish <ref>` sends
+one out — dry run until `--yes`, only when they said to.
 
 ## Where the detail is
 

package/assets/memgineering-registry/SKILL.md

@@ -2,7 +2,7 @@
 name: memgineering-registry
 description: Use when the user wants judgment somebody else has already settled — "what do other people do about this", "is there a pattern for it", "read that judgment", "adapt that pattern to this repo", "fit it to our setup", "how do others handle X" — or when one of their own decisions should go out: "publish this decision", "share this rule", "put it on memgineering", "send it to the registry". Also when they ask whether what you read gets stored. Covers the public layer: reading somebody else's judgment into context, the transplant brief, publishing one claim out of this brain, lineage, why reading is never copying, and how author-controlled text is fenced.
 type: skill
-version: 0.19.0
+version: 0.20.0
 allowed-tools: Bash(memgineering:*)
 ---
 
@@ -12,16 +12,19 @@ memgineering.com is where settled decisions live in public. A package there is
 one person's judgment — a decision, a preference, or a procedure — carrying the
 scope it holds in, when it was true, and what it rests on.
 
-Five verbs reach it. None of them installs anything, and none of them writes a
-note. An identifier looks like `<username>/<slug>`, optionally `@<version>`; it
-comes from the user, or from the attribution line under something you already
-read.
+Five verbs reach it, all of them under `memgineering registry`. None of them
+installs anything, and none of them writes a note. An identifier looks like
+`<username>/<slug>`, optionally `@<version>`; it comes from the user, or from
+the attribution line under something you already read.
 
-## `search` — find one without knowing its name
+Each one still answers to its bare name as well, which prints a line on stderr
+saying so and is not the documented form — write the namespaced spelling.
+
+## `registry search` — find one without knowing its name
 
 ```
-memgineering search additive migrations
-memgineering search --type judgment-pattern --limit 5
+memgineering registry search additive migrations
+memgineering registry search --type judgment-pattern --limit 5
 ```
 
 Titles, one-line descriptions, and the verb that would fetch each result. No
@@ -33,11 +36,11 @@ to drop the filter or broaden the words, and the same sentence is on `hint`
 under `--json`. Take it. Guessing a third phrasing when the tool has already
 named the lever is how one lookup becomes five.
 
-## `read` — somebody else's judgment, in your context
+## `registry read` — somebody else's judgment, in your context
 
 ```
-memgineering read gaeullee824/ask-before-acting
-memgineering read gaeullee824/ask-before-acting@1.2.0 --json
+memgineering registry read gaeullee824/ask-before-acting
+memgineering registry read gaeullee824/ask-before-acting@1.2.0 --json
 ```
 
 Prints the body and one provenance line: what was read, of what kind, from
@@ -51,11 +54,11 @@ user that before you use it, not after.
 claim about their own judgment and nothing has checked it. Weight what you
 read accordingly, and say which tier it was when you hand it to the user.
 
-## `info` — what it is, before you read it
+## `registry info` — what it is, before you read it
 
 ```
-memgineering info gaeullee824/ask-before-acting
-memgineering info gaeullee824/ask-before-acting@1.2.0
+memgineering registry info gaeullee824/ask-before-acting
+memgineering registry info gaeullee824/ask-before-acting@1.2.0
 ```
 
 Metadata only, and no body is fetched: title, description, kind, version,
@@ -67,10 +70,10 @@ Reach for it when a search result is close but not obviously right, or on a
 package nothing can read: a hook or an MCP server has no body to inline, so
 `read` would be refused and this is the verb that still answers.
 
-## `adapt` — a transplant brief for THIS project
+## `registry adapt` — a transplant brief for THIS project
 
 ```
-memgineering adapt gaeullee824/ask-before-acting
+memgineering registry adapt gaeullee824/ask-before-acting
 ```
 
 **Run it from the user's project root.** It reads the harness in the current
@@ -104,8 +107,8 @@ That row goes to whichever brain this machine is pointed at, and `read` and
 `adapt` both take the pair `publish` takes for naming a different one:
 
 ```
-memgineering read gaeullee824/ask-before-acting --local
-memgineering adapt gaeullee824/ask-before-acting --vault ~/notes
+memgineering registry read gaeullee824/ask-before-acting --local
+memgineering registry adapt gaeullee824/ask-before-acting --vault ~/notes
 ```
 
 `--local` files the row beside the brain on this disk even when the machine is
@@ -141,11 +144,11 @@ you need the raw bytes, strip the first and last line using the sentinel value;
 do not pattern-match the marker text, because marker-looking lines inside a
 body are neutralized with a zero-width space and are part of the data.
 
-## `publish` — one decision of theirs, out
+## `registry publish` — one decision of theirs, out
 
 ```
-memgineering publish friday-review
-memgineering publish friday-review --yes --reason "<the user's own words>"
+memgineering registry publish friday-review
+memgineering registry publish friday-review --yes --reason "<the user's own words>"
 ```
 
 Bare, it sends nothing: it prints the exact bytes that would leave and says so.
@@ -170,13 +173,13 @@ A note that declares `never_store` words is refused too — that is the boundary
 itself, not a judgment to share.
 
 **Publishing the same decision again.** When the note has changed and its
-package already exists, `memgineering publish <ref> --bump patch` publishes the
-next version of it — `minor` or `major` when the judgment moved further. The
-name only holds one of each version, so without `--bump` a second publish under
-the same name is refused. A `--bump` is refused too if the package came from a
-different note; give that one its own `--slug`. If the published version was
-rejected by review, its body cannot be fetched to check that — the bump goes
-ahead on the account alone and prints a line saying so.
+package already exists, `memgineering registry publish <ref> --bump patch`
+publishes the next version of it — `minor` or `major` when the judgment moved
+further. The name only holds one of each version, so without `--bump` a second
+publish under the same name is refused. A `--bump` is refused too if the
+package came from a different note; give that one its own `--slug`. If the
+published version was rejected by review, its body cannot be fetched to check
+that — the bump goes ahead on the account alone and prints a line saying so.
 
 What crosses: the claim, its scope, its validity, its evidence, and the note's
 title and summary. **Not the body.** `--slug` names the package when the title
@@ -202,7 +205,8 @@ another machine leaves no record here.
 
 Installing files, stars, follows, comments, and withdrawing a release stay in
 the `kordis` CLI for one release window. The public layer's verbs are
-`search`, `info`, `read`, `adapt` and `publish`.
+`registry search`, `registry info`, `registry read`, `registry adapt` and
+`registry publish`.
 
 `memgineering pull` is unrelated: it is the brain verb for a hosted brain, not
 a registry install.

package/dist/index.js

@@ -13593,7 +13593,7 @@ function memoryCommand() {
 }
 
 // src/index.ts
-var ALIAS_NOTICE = "kordis is now part of memgineering \u2014 `kordis` keeps working as an alias until memgineering 0.20.0; the same verbs live at `memgineering <verb>`.";
+var ALIAS_NOTICE = "kordis is now part of memgineering \u2014 `kordis` keeps working as an alias until memgineering 0.21.0; the same verbs live at `memgineering registry <verb>`.";
 var aliasNoticePrinted = false;
 function printAliasNotice() {
   if (aliasNoticePrinted) return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayul/kordis",
-  "version": "0.14.0",
+  "version": "0.14.1",
   "private": false,
   "description": "Command-line client for the Kordis registry — discover, install, and publish agentic-coding packages.",
   "license": "Apache-2.0",