@misaka-net/misakanet-setup 0.4.0 → 0.4.1

package/README.md

@@ -9,7 +9,7 @@ npx @misaka-net/misakanet-setup
 ```
 
 Then **close and reopen the assistant window** (the new MCP server loads on restart) and ask
-something with an error in it, e.g. "docker exit code 137 是什么原因" — it should search the
+something with an error in it, e.g. "pip install timeout 是什么原因" — it should search the
 knowledge base on its own instead of guessing.
 
 ## What it installs, and why all three
@@ -31,6 +31,8 @@ npx @misaka-net/misakanet-setup --verify      # READY / NOT READY, installed ver
 npx @misaka-net/misakanet-setup --only claude # one agent only
 npx @misaka-net/misakanet-setup --no-register # read-only, no anonymous token
 npx @misaka-net/misakanet-setup --upgrade     # same as installing the latest (the command is idempotent)
+                                             # re-running also *refreshes* an older hook (the previous copy
+                                             # is kept as ~/.misakanet-agent/hook.mjs.misakanet.bak)
 npx @misaka-net/misakanet-setup --uninstall   # remove exactly what it added
 ```
 

package/bin/misakanet-setup.mjs

@@ -103,7 +103,7 @@ function readText(path) {
  * meant to prevent is now caught in CI instead, by a test that binds this literal to the
  * manifest — a failing test is a better place for that than a request header.
  */
-const VERSION = '0.4.0';
+const VERSION = '0.4.1';
 
 function backup(path) {
   if (DRY || !readText(path)) return;
@@ -252,23 +252,44 @@ function locateHook() {
 
 async function installHook() {
   const hookPath = join(stateDir(), 'hook.mjs');
+  const bundled = locateHook();
+  let existing = null;
   try {
-    if (readFileSync(hookPath, 'utf8').includes('MisakaNet')) {
+    existing = readFileSync(hookPath, 'utf8');
+  } catch { /* not installed yet */ }
+  const isOurs = existing !== null && existing.includes('MisakaNet');
+
+  if (!bundled) {
+    if (isOurs) {
       ok(`自动沉淀的钩子已存在：${hookPath}`);
       return hookPath;
     }
-  } catch { /* not installed yet */ }
-  const bundled = locateHook();
-  if (!bundled) {
     need('自动沉淀那部分装不上：这个 npm 包里没有带钩子文件（安装不完整）→ '
       + '重新执行 npx 安装即可；其它功能不受影响');
     return null;
   }
+
+  if (isOurs && existing.trim() === bundled.trim()) {
+    ok(`自动沉淀的钩子已是最新：${hookPath}`);
+    return hookPath;
+  }
+
+  // Refresh a hook that is *ours* (marker) but older than the bundled copy, keeping the
+  // previous file beside it.
+  //
+  // This used to return early for any hook containing "MisakaNet", which made a hook fix
+  // unable to reach an existing install: the 14-day upgrade nudge (#1712) could not
+  // arrive, and re-running the installer — the very thing the nudge asks the user to do —
+  // changed nothing (found 2026-09-15: the machine's installed hook predated the nudge
+  // while `npx …@latest` reported success).
   if (!DRY) {
     mkdirSync(stateDir(), { recursive: true });
+    if (existing !== null) backup(hookPath);
     writeFileSync(hookPath, bundled);
   }
-  ok(`安装自动沉淀钩子 → ${hookPath}`);
+  ok(isOurs
+    ? `自动沉淀的钩子已更新（旧版备份为 ${hookPath}.misakanet.bak）→ ${hookPath}`
+    : `安装自动沉淀钩子 → ${hookPath}`);
   return hookPath;
 }
 
@@ -447,11 +468,30 @@ async function installCodex(hookPath, bearer) {
 
   const rules = join(HOME, '.codex', 'AGENTS.md');
   ok(`Codex：规则块 ${injectBlock(rules, PROMPT_BLOCK)} → ${rules}`);
-  need('Codex：用户级钩子的写法我没能确证 → "第 20 轮自动沉淀"靠规则自律；'
-    + '要硬保证就用 --verify 看状态，或把本会话放在 CC 里跑');
+  // Verified on codex-cli 0.154.0 (2026-09-15), so this is no longer a "could not
+  // confirm" note: `codex mcp list` shows misakanet enabled with the Bearer token,
+  // `codex doctor` reports config.toml parse ok + 1 streamable_http server + 0
+  // disabled, and `codex debug prompt-input` renders a `# AGENTS.md instructions`
+  // item carrying this rule block. What stays open is the *hook*: 0.154.0's lifecycle
+  // hooks are admin-managed (requirements.toml), so the round-20 distillation is
+  // rule-driven rather than hook-driven.
+  ok('Codex：注册已核对（`codex mcp list` / `codex doctor` / `codex debug prompt-input`）');
+  need('Codex：没有用户级 lifecycle hook → "第 20 轮自动沉淀"靠规则块自律；'
+    + '要硬保证就配外层 wrapper 每轮后跑 checkpoint_reminder');
 }
 
 const STATE_VERSION_FILE = 'version';
+
+/**
+ * The question the onboarding text tells a user to ask — and the reason it is a constant.
+ *
+ * It used to be "docker exit code 137 是什么原因", which the corpus answers with three only
+ * loosely-related lessons (top hit: kubernetes-crashloopbackoff-debugging) — so a new user's
+ * first question, the one we chose for them, landed on a near-miss. It is now a query whose top
+ * hit is a lesson about that very failure, and tests/test_onboarding_example.py keeps it that
+ * way offline (plus a check that this literal is not duplicated back into the messages).
+ */
+const ONBOARDING_QUERY = 'pip install timeout';
 const REGISTRY_LATEST = process.env.MISAKANET_REGISTRY_URL
   || 'https://registry.npmjs.org/@misaka-net%2fmisakanet-setup/latest';
 
@@ -913,7 +953,7 @@ if (mode === 'uninstall') {
 if (mode === 'verify') {
   const allOk = await verify();
   console.log(render());
-  console.log(`\n结论：${allOk ? 'READY —— 打开一个新会话，问它「docker exit code 137 是什么原因」' : 'NOT READY —— 上面每条 ! 都给了修复动作'}`);
+  console.log(`\n结论：${allOk ? `READY —— 打开一个新会话，问它「${ONBOARDING_QUERY} 是什么原因」` : 'NOT READY —— 上面每条 ! 都给了修复动作'}`);
   process.exit(allOk ? 0 : 1);
 }
 
@@ -941,6 +981,6 @@ console.log(render());
 console.log(`
 接下来：
   1) **把这个助手窗口关掉再打开一次**（新功能要重开会话才生效）
-  2) 随便问一句带报错的：「docker exit code 137 是什么原因」——它应该先去查经验库
+  2) 随便问一句带报错的：「${ONBOARDING_QUERY} 是什么原因」——它应该先去查经验库
   3) 想确认状态：npx @misaka-net/misakanet-setup --verify
   4) 想关掉：npx @misaka-net/misakanet-setup --uninstall`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@misaka-net/misakanet-setup",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "One-command setup: teach your Claude Code / Codex / Hermes / OpenClaw to search MisakaNet failure lessons before repeating a mistake, and to distil the session at a checkpoint.",
   "bin": {
     "misakanet-setup": "bin/misakanet-setup.mjs"