@mkterswingman/5mghost-wonder 0.0.8 → 0.0.10

package/dist/cli.js

@@ -9,6 +9,32 @@ import { createWonderTelemetryRuntime } from "./telemetry/runtime.js";
 import { createWonderAuthSdk } from "./auth/runtime.js";
 import { resolveTelemetryCommand, classifyUnhandledCliError, } from "./telemetry/policy.js";
 import { buildCompletionTelemetry } from "./telemetry/events.js";
+// How long to wait for in-flight telemetry flushes before exiting. Long
+// enough to cover the SDK's full network roundtrip in the typical case
+// (~1s on a healthy connection), short enough to not block a stuck
+// upload behind the SDK's own 10s timeout. Events that miss the
+// deadline stay in the outbox and are picked up by the next
+// `wonder` invocation's startup flush.
+const TELEMETRY_DRAIN_MS = 5000;
+async function drainTelemetry(rt) {
+    if (!rt)
+        return;
+    const flightTask = rt.flushTask;
+    if (!flightTask)
+        return;
+    let timer;
+    const deadline = new Promise((resolve) => {
+        timer = setTimeout(resolve, TELEMETRY_DRAIN_MS);
+        timer.unref?.();
+    });
+    try {
+        await Promise.race([flightTask.catch(() => undefined), deadline]);
+    }
+    finally {
+        if (timer)
+            clearTimeout(timer);
+    }
+}
 // ── Global error handlers (catch errors outside async dispatch) ─────────────
 process.on("uncaughtException", (err) => {
     process.stderr.write(`Unhandled exception: ${String(err)}\n`);
@@ -51,6 +77,7 @@ try {
     // No arguments → show help, exit 0
     if (argv.length === 0) {
         const result = await runHelpCommand(io);
+        await drainTelemetry(telemetry);
         process.exit(result.exitCode);
     }
     const result = await dispatchWonderCommand(argv, context);
@@ -62,6 +89,7 @@ try {
             // Telemetry failure must never change the CLI exit code.
         }
     }
+    await drainTelemetry(telemetry);
     process.exit(result.exitCode);
 }
 catch (err) {
@@ -79,5 +107,6 @@ catch (err) {
         }
     }
     io.stderr(`Unhandled error: ${String(err)}`);
+    await drainTelemetry(telemetry);
     process.exit(1);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mkterswingman/5mghost-wonder",
-  "version": "0.0.8",
+  "version": "0.0.10",
   "description": "企微文档读取 CLI — WeCom document reader",
   "type": "module",
   "engines": {

package/scripts/postinstall.mjs

@@ -44,6 +44,12 @@ try {
   } else {
     console.log("[wonder] No skill targets updated.");
   }
+  // Always remind the user to restart their AI session — skill text loaded
+  // into a running session does not refresh after files on disk are replaced.
+  console.log("");
+  console.log("[wonder] ⚠️  IMPORTANT: Restart your AI session (Claude Code / Codex / Gemini / etc.)");
+  console.log("[wonder]     before invoking any wonder skill. Open a new chat, or run /exit and re-enter.");
+  console.log("[wonder]     The AI cannot pick up the newly installed skill text in this running session.");
 } catch (err) {
   // Skill install failure must never break npm install
   console.log(`[wonder] Skill install failed (non-fatal): ${String(err)}`);

package/skills/setup-5mghost-wonder/SKILL.md

@@ -5,6 +5,16 @@ description: Use this skill when the user wants to install or set up wonder, say
 
 # Setup wonder — 企微文档 CLI 安装向导
 
+## Skill version
+
+This skill matches **wonder 0.0.10**.
+
+Once the CLI is installed in Step 1, run `wonder --version`. If the output does not equal `0.0.10`, the CLI on disk has drifted from the skill text loaded in this session. Ask the user to run `/update-5mghost-wonder`, then **start a fresh AI session** (`/exit` and re-enter, or open a new chat) — skill text already loaded into a running session does not refresh after `wonder update`, even though the file on disk has been replaced.
+
+After a successful first install, also remind the user to start a fresh AI session before invoking `/use-5mghost-wonder` for the first time. The skill files were just written to disk; the current session never loaded them.
+
+---
+
 You are guiding the user through installing and configuring `wonder`, the WeCom document reader CLI.
 
 Execute each step in order using the Bash tool. Stop and ask for user interaction only when a step requires it (e.g., browser OAuth, QR code scan). After each detection step, only proceed to installation if the tool is missing.

package/skills/update-5mghost-wonder/SKILL.md

@@ -5,6 +5,12 @@ description: Use this skill when the user wants to update or upgrade wonder, say
 
 # Update wonder — 升级 5mghost-wonder CLI
 
+## Skill version
+
+This skill matches **wonder 0.0.10**.
+
+---
+
 Run the CLI's built-in updater. It reinstalls the latest published version globally via npm.
 
 ```bash
@@ -17,7 +23,7 @@ When the command completes, verify the new version is in place:
 wonder --version
 ```
 
-After updating, **the bundled skills (`setup-5mghost-wonder`, `use-5mghost-wonder`, `update-5mghost-wonder`) on disk are refreshed by the package's `postinstall`**, but the AI session's already-loaded skill text is the old version. Tell the user to start a new session if they need the latest skill text — open a fresh chat / restart the CLI / `/exit` and re-enter.
+After updating, **the bundled skills (`setup-5mghost-wonder`, `use-5mghost-wonder`, `update-5mghost-wonder`) on disk are refreshed by the package's `postinstall`**, but the AI session's already-loaded skill text is the old version. **Tell the user — clearly and proactively — that they must start a new AI session before the new skill text takes effect**: open a fresh chat, restart the CLI, or run `/exit` and re-enter. Until they do, the AI is still operating on the old skill regardless of what `wonder --version` reports.
 
 If `wonder update` exits non-zero, the most common cause is npm permission or registry issues. Re-run with the user's terminal so they can see the npm error directly:
 

package/skills/use-5mghost-wonder/SKILL.md

@@ -5,6 +5,12 @@ description: Use this skill when the user shares a URL containing "doc.weixin.qq
 
 # use-5mghost-wonder — 企微文档读取操作指南
 
+## Skill version
+
+This skill matches **wonder 0.0.10**.
+
+In the Session Initialization step below, after running `wonder --version`, compare the output to `0.0.10`. If they differ, the loaded skill text and the CLI on disk are out of sync. Stop, tell the user to run `/update-5mghost-wonder`, and then **start a fresh AI session** (`/exit` and re-enter, or open a new chat) before trying again. `wonder update` rewrites the skill files on disk, but skill text already loaded into the current session does not auto-refresh.
+
 ## Session Initialization (first use only per session)
 
 The **first time** you encounter a WeCom document URL in a session, run these checks before processing the document. Remember you have already done this — do not repeat in subsequent calls within the same session.
@@ -13,7 +19,10 @@ The **first time** you encounter a WeCom document URL in a session, run these ch
 # 1. Check for updates
 wonder update
 
-# 2. Check WeCom cookie status
+# 2. Confirm the CLI version matches this skill's expected version (0.0.10)
+wonder --version
+
+# 3. Check WeCom cookie status
 wonder wecom status
 ```