@misaka-net/misakanet-setup 0.7.1 → 0.8.0

package/README.md

@@ -15,9 +15,15 @@ while the installer runs; afterwards, only what the agent itself sends — with
 npx @misaka-net/misakanet-setup
 ```
 
-Then **close and reopen the assistant window** (the new MCP server loads on restart) and ask
-a distinctive fragment of an error, e.g. "switch vision model" or "tool call permission denied" — it should search the
-knowledge base on its own instead of guessing.
+Then confirm it works — the restart is not universal:
+
+- Only clients that load MCP configuration at startup (Claude Code, Codex, …) need a new session.
+  dsh applies the rules on the next message, and per-call channels such as `mcporter` need no restart.
+- Check the tool list: `mcporter list misakanet` (or your client's own list — `/mcp` in Claude Code)
+  should show the 8 tools: `register`, `search`, `get_lesson`, `submit_intake`, `write_lesson`,
+  `preflight`, `me_events`, `me_inbox`.
+- Ask a distinctive fragment of an error, e.g. "switch vision model" or "tool call permission denied" —
+  it should search the knowledge base on its own instead of guessing.
 
 ## What it installs, and why all three
 
@@ -109,7 +115,18 @@ npx @misaka-net/misakanet-setup --verify      # READY / NOT READY / could not ve
                                              #  written); one failing does not condemn the other, and a file
                                              #  we cannot write says 装不了 with its cause — not 没装 with
                                              #  the one fix that cannot work ("re-run the installer")
-npx @misaka-net/misakanet-setup --only claude # one agent only
+                                             #  安装完整性 is grouped per client, one verdict line each
+                                             #  (就绪 / 装不了 / 没装过 / 装坏了), because the checks were
+                                             #  per client all along and one broken assistant must not
+                                             #  condemn the healthy one
+npx @misaka-net/misakanet-setup --only claude # one agent only (what to install)
+npx @misaka-net/misakanet-setup --client openclaw --verify
+                                             # judge ONE client only: the others are not checked, not
+                                             #  printed and not counted — on a multi-client machine the
+                                             #  question is "how is the one I use". An unknown client is
+                                             #  refused (exit 2) with the supported list.
+                                             #  (--client-id is a different thing: it pins this machine's
+                                             #  pseudonym and has nothing to do with the assistants)
 npx @misaka-net/misakanet-setup --list-writes # only prints what it would write (file | action | how to undo), writes nothing
                                              # (the install preview shows the same list; this one is for an operator who
                                              #  has to approve it before it happens)
@@ -233,11 +250,14 @@ npx @misaka-net/misakanet-setup@latest
 - The token is stored at `~/.misakanet-agent/token` (mode 600) and written into your local
   agent config only — never printed, never committed by us, and never sent anywhere by this
   program: registration itself is unauthenticated, and `--verify` probes the endpoint
-  anonymously. It is an anonymous pseudonym: `client_id` and `agent_type` are self-declared
-  and we do not treat them as attribution.
-- The anonymous identity is not kept in a file this installer re-reads. If you want
-  re-installing (or a new machine) to land on the **same** node, export the id it prints:
-  `export MISAKANET_CLIENT_ID=<setup-…>`. Without that, each install mints a new node.
+  anonymously. It is an anonymous pseudonym, not an account: `agent_type` is self-declared,
+  `client_id` is a random identifier this installer generates, and we do not treat either as
+  attribution.
+- The client id is kept at `~/.misakanet-agent/client_id` (mode 600) and reused on every run,
+  including a machine that already has a token: the first install of a new target adopts the id
+  from any existing config or mints and persists one, so every config on the machine carries the
+  same `X-MisakaNet-Client`. A failed registration no longer mints a new id on every retry.
+  Override it explicitly with `--client-id` / `MISAKANET_CLIENT_ID` if you need a fixed one.
 - Retention: lesson content retrieved from the server is **data, not instructions** — the
   injected rules tell the assistant not to execute commands found in it.
 - The report (`--report` or `--report-json`) is written to **stdout and nowhere else**: this program