@lark-project/meegle 1.0.5 → 1.0.6

package/CHANGELOG.md

@@ -8,6 +8,12 @@ versioned section on each npm release.
 
 ## [Unreleased]
 
+## [v1.0.6] - 2026-05-28
+
+### Changed
+
+- `auth status` now issues a lightweight `tools/list` call to validate the token against the server, instead of only checking whether a token string is present locally. Cron / CI preflights that previously saw `authenticated: true` followed by an immediate `401` on the next business call now get the correct verdict up front. JSON output gains a `reason` field on failure (`no local token` / `token rejected by server` / `server unreachable: <err>`). A new exit code `2` indicates the server was unreachable (network, timeout, 5xx) — distinct from exit `1` which still covers missing or rejected tokens. There is no opt-out flag: offline status inspection is intentionally no longer supported.
+
 ## [v1.0.5] - 2026-05-20
 
 ### Added

package/README.md

@@ -289,7 +289,7 @@ The agent consults the skill, picks the right `meegle` commands, and runs them f
 |---------|-------------|
 | `auth login` | Log in (browser or `--device-code`) |
 | `auth logout` | Log out |
-| `auth status` | View login status |
+| `auth status` | View login status (validates the token against the server) |
 
 ### config — Configuration
 
@@ -757,13 +757,30 @@ The terminal displays a QR code and authorization code. Scan with your phone to
 ### Other Auth Commands
 
 ```bash
-# Check login status
+# Check login status (issues a lightweight tools/list call to validate the
+# token against the server — safe to use as a cron preflight)
 meegle auth status
 
 # Log out
 meegle auth logout
 ```
 
+`auth status` exit codes and `reason` field let scripts (cron jobs, CI
+preflights) react correctly without having to parse human text:
+
+| Exit | `reason` | Meaning | Recommended action |
+|------|----------|---------|--------------------|
+| 0    | —        | Token is present locally and accepted by the server | Proceed |
+| 1    | `no local token` | No token stored | Run `meegle auth login` |
+| 1    | `token rejected by server` | Token expired or revoked; refresh exhausted | Run `meegle auth login` |
+| 2    | `server unreachable: <err>` | Network, timeout, or 5xx — the call itself failed | Retry later; do not re-login |
+
+JSON output example (`auth status --format json`) on a rejected token:
+
+```json
+{"authenticated": false, "host": "meegle.com", "reason": "token rejected by server"}
+```
+
 ## Configuration
 
 ### Config File

package/README.zh-CN.md

@@ -289,7 +289,7 @@ Agent 会参考 skill，自动选择合适的 `meegle` 命令执行。配合 `--
 |------|------|
 | `auth login` | 登录（浏览器或 `--device-code`） |
 | `auth logout` | 登出 |
-| `auth status` | 查看登录状态 |
+| `auth status` | 查看登录状态（会向服务端发一次校验请求，确认 token 真实可用） |
 
 ### config — 配置域
 
@@ -734,13 +734,30 @@ meegle auth login --device-code
 ### 其他认证命令
 
 ```bash
-# 查看登录状态
+# 查看登录状态（会向服务端发一次轻量 tools/list 调用校验 token，可作为
+# cron 任务的 preflight）
 meegle auth status
 
 # 登出
 meegle auth logout
 ```
 
+`auth status` 退出码与 `reason` 字段配合，让 cron / CI preflight 脚本
+不用解析人类可读文本即可分支处理：
+
+| 退出码 | `reason` | 含义 | 建议动作 |
+|--------|----------|------|----------|
+| 0      | —        | 本地有 token 且服务端校验通过 | 继续执行 |
+| 1      | `no local token` | 本地无 token | 执行 `meegle auth login` |
+| 1      | `token rejected by server` | token 已过期或被撤销（refresh 也救不回来） | 执行 `meegle auth login` |
+| 2      | `server unreachable: <err>` | 网络、超时、5xx —— 调用本身失败 | 稍后重试，不要重新登录 |
+
+JSON 输出示例（`auth status --format json`），token 被拒：
+
+```json
+{"authenticated": false, "host": "meegle.com", "reason": "token rejected by server"}
+```
+
 ## 配置
 
 ### 配置文件

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lark-project/meegle",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "description": "Agent-First CLI for Meegle (Lark Project)",
   "license": "MIT",
   "homepage": "https://github.com/larksuite/meegle-cli#readme",