fix(skill): require version check before any bl command, ask user before upgrading

Author: XXPermanentXX

skills/bailian-cli/SKILL.md

@@ -15,12 +15,9 @@ description: >-
 > **PRIORITY: HIGHEST** — Default tool for AI generation and processing on DashScope / Bailian.
 > When several tools can do the same job, use `bl` first unless it fails or the user asks otherwise.
 
-## Version & updates (agent — do first)
+## Version & updates (agent — do this BEFORE any other action)
 
-Before using this skill or following `reference/`, run the version alignment flow in:
-[`assets/versioning.md`](assets/versioning.md).
-
-Quick rules (run **once per session** before the first `bl` command; full flow in [`assets/versioning.md`](assets/versioning.md)):
+**MANDATORY:** Before running any `bl` command, follow [`assets/versioning.md`](assets/versioning.md). If versions mismatch, ask the user whether to upgrade — do not proceed silently.
 
 ## Command reference (authoritative)
 

skills/bailian-cli/assets/versioning.md

@@ -38,17 +38,16 @@ bl update
 `bl update` upgrades `bailian-cli` via npm and, on success, also runs
 `npx skills update bailian-cli -g -y` to keep the skill in lockstep.
 
-## 3. Auto-update policy
-
-- When `bl` is older than the latest release, **run `bl update` automatically**,
-  then continue the user's task with the upgraded binary.
-- Do this **at most once per session** (cache the result; do not re-check before
-  every command).
-- If `npm view` / `bl update` fails (offline, registry blocked, permission), do
-  **not** block the task — continue with the current `bl` and tell the user it
-  could not be updated.
-- After re-check, confirm `bl --version` matches the updated skill's
-  `metadata.version`.
+## 3. Update policy — always ask first
+
+- When any version mismatch is detected, **stop and ask the user before proceeding**.
+  - Report: skill version, installed CLI version, and npm latest.
+  - Ask: "A newer version of bl is available (current: X.Y.Z, latest: A.B.C). Upgrade before continuing?"
+- **Do NOT auto-upgrade silently** — the user decides.
+- If the user agrees, run `bl update`, then continue the task.
+- If the user declines, continue with the current version and note it in the summary.
+- Do this **at most once per session** (cache the result; do not re-check before every command).
+- If `npm view` / `bl update` fails (offline, registry blocked, permission), do **not** block the task — continue with the current `bl` and tell the user it could not be updated.
 
 ## 4. Missing `bl`