@misaka-net/misakanet-setup 0.5.1 → 0.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -9,7 +9,7 @@ npx @misaka-net/misakanet-setup
9
9
  ```
10
10
 
11
11
  Then **close and reopen the assistant window** (the new MCP server loads on restart) and ask
12
- something with an error in it, e.g. "pip install timeout 是什么原因" — it should search the
12
+ a distinctive fragment of an error, e.g. "switch vision model" or "tool call permission denied" — it should search the
13
13
  knowledge base on its own instead of guessing.
14
14
 
15
15
  ## What it installs, and why all three
@@ -103,7 +103,7 @@ function readText(path) {
103
103
  * meant to prevent is now caught in CI instead, by a test that binds this literal to the
104
104
  * manifest — a failing test is a better place for that than a request header.
105
105
  */
106
- const VERSION = '0.5.1';
106
+ const VERSION = '0.5.2';
107
107
 
108
108
  function backup(path) {
109
109
  if (DRY || !readText(path)) return;
@@ -593,7 +593,16 @@ const STATE_VERSION_FILE = 'version';
593
593
  * hit is a lesson about that very failure, and tests/test_onboarding_example.py keeps it that
594
594
  * way offline (plus a check that this literal is not duplicated back into the messages).
595
595
  */
596
- const ONBOARDING_QUERY = 'pip install timeout';
596
+ // Three examples, not one, and all three are *distinctive fragments* rather than sentences.
597
+ //
598
+ // Two lessons are baked in here. A single narrow example (the old "pip install timeout") made the
599
+ // corpus look one topic deep, so a new user's first impression undersold it. And the natural-language
600
+ // form of a question ("如何切换识图模型") returns nothing at all, because the corpus is indexed by
601
+ // error text and keywords — the same thing the rules block tells the agent to send. So these teach
602
+ // the usage while they demonstrate the value, and every one of them is checked offline by
603
+ // tests/test_onboarding_example.py: it fails if a new user's first hit is not a lesson about the
604
+ // question we told them to ask.
605
+ const ONBOARDING_QUERIES = ["switch vision model", "context window exceeded", "tool call permission denied"];
597
606
  const REGISTRY_LATEST = process.env.MISAKANET_REGISTRY_URL
598
607
  || 'https://registry.npmjs.org/@misaka-net%2fmisakanet-setup/latest';
599
608
 
@@ -1246,7 +1255,7 @@ if (mode === 'report') {
1246
1255
  if (mode === 'verify') {
1247
1256
  const allOk = await verify();
1248
1257
  console.log(render());
1249
- console.log(`\n结论:${allOk ? `READY —— 打开一个新会话,问它「${ONBOARDING_QUERY} 是什么原因」` : 'NOT READY —— 上面每条 ! 都给了修复动作'}`);
1258
+ console.log(`\n结论:${allOk ? `READY —— 打开一个新会话,问它「${ONBOARDING_QUERIES[0]}」这类带报错原文的片段` : 'NOT READY —— 上面每条 ! 都给了修复动作'}`);
1250
1259
  process.exit(allOk ? 0 : 1);
1251
1260
  }
1252
1261
 
@@ -1275,6 +1284,6 @@ console.log(render());
1275
1284
  console.log(`
1276
1285
  接下来:
1277
1286
  1) **把这个助手窗口关掉再打开一次**(新功能要重开会话才生效)
1278
- 2) 随便问一句带报错的:「${ONBOARDING_QUERY} 是什么原因」——它应该先去查经验库
1287
+ 2) 随便挑一句带报错原文的片段问它(例如「${ONBOARDING_QUERIES[0]}」「${ONBOARDING_QUERIES[1]}」「${ONBOARDING_QUERIES[2]}」)——它应该先去查经验库
1279
1288
  3) 想确认状态:npx @misaka-net/misakanet-setup --verify
1280
1289
  4) 想关掉:npx @misaka-net/misakanet-setup --uninstall`);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@misaka-net/misakanet-setup",
3
- "version": "0.5.1",
3
+ "version": "0.5.2",
4
4
  "description": "One-command setup: teach your Claude Code / Codex / Hermes / OpenClaw / codewhale to search MisakaNet failure lessons before repeating a mistake, and to distil the session at a checkpoint.",
5
5
  "bin": {
6
6
  "misakanet-setup": "bin/misakanet-setup.mjs"