@lumoai/cli 1.10.0 → 1.15.0

package/assets/skill.md

@@ -1,6 +1,6 @@
 ---
 name: lumo
-description: 'Use the Lumo CLI to load task context, manage session bindings, inspect projects and milestones, and create/update/list/show/comment on tasks from the terminal. Activate when: user mentions a Lumo task identifier (LUM-42, LUM-12, etc.), asks to load task background or context, wants to bind, check, or detach a Claude Code session''s task binding, is about to start development work on a specific task, wants to create a new task, list their tasks, view a task, comment on a task, list projects, list milestones, attach a task to a milestone, or update a task''s status/title/description/priority/assignee/milestone. Triggers on: "LUM-", "task context", "load context", "session start", "session attach", "session status", "session detach", "bind session", "unbind session", "which task", "what task am I on", "work on LUM", "create task", "new task", "add task", "file a task", "log a task", "list tasks", "my tasks", "show task", "view task", "comment on task", "leave a comment", "list projects", "what projects", "update task", "change task status", "rename task", "reassign task", "mark task as done", "milestone", "里程碑", "list milestones", "set milestone", "挂到 milestone", "attach milestone", "unbind milestone", "create milestone", "new milestone", "update milestone", "change milestone status", "delete milestone", "show milestone", "view milestone", "tasks in milestone", "milestone tasks", "新建里程碑", "更新里程碑", "删除里程碑", "查看里程碑", "milestone summary", "milestone retro", "summarize milestone", "里程碑总结", "里程碑复盘", "milestone add", "milestone remove", "add tasks to milestone", "remove tasks from milestone", "batch milestone", "bulk milestone", "挂任务到里程碑", "批量挂里程碑", "从里程碑移除任务", "auth login", "log in", "login", "auth logout", "log out", "logout", "sign out", "switch account", "switch identity", "whoami", "who am I", "current identity", "current user", "current workspace", "登录", "登出", "切换账号", "当前身份", "create doc", "new doc", "new document", "write doc", "写文档", "新建文档", "update doc", "edit doc", "修改文档", "更新文档", "list docs", "my docs", "我的文档", "show doc", "view doc", "查看文档", "delete doc", "删除文档", "bind doc", "attach doc to task", "把文档关联到任务", "文档绑定到任务", "unbind doc", "解绑文档", "personal doc", "workspace doc", "个人文档", "workspace 文档", "doc scope", "tag", "add tag", "remove tag", "标签", "添加标签", "移除标签", "doc tag", "task tag", "share doc", "doc share", "share document", "分享文档", "文档分享", "unshare doc", "remove share", "取消分享", "share list", "list doc shares", "who has access", "viewer", "editor", "manager", "shared with", "doc tree", "doc move", "move doc", "reparent doc", "文档树", "移动文档", "sprint", "start sprint", "close sprint", "add to sprint", "active sprints", "冲刺", "迭代", "开始冲刺", "关闭冲刺", "create sprint", "new sprint", "list sprints", "show sprint", "update sprint", "delete sprint", "sprint summary", "sprint retro", "把任务挂到冲刺", "冲刺里有什么", "lumo update", "update cli", "upgrade lumo", "update lumo", "upgrade cli", "升级 lumo", "更新 cli", "new lumo version", "是否有新版本", "lumo setup", "install lumo skill", "install lumo hooks", "wire up lumo", "set up lumo", "onboard lumo", "npx @lumoai/cli", "安装 lumo", "配置 lumo", "lumo 初始化", "task artifact", "artifact add", "artifact list", "artifact show", "artifact rm", "artifact delete", "artifact update", "update artifact", "edit artifact", "change artifact kind", "change artifact source", "remove artifact", "delete artifact", "spec artifact", "record spec", "attach spec", "attach plan", "记录 spec", "挂 spec", "查看 artifact", "编辑 artifact", "修改 artifact", "删除 artifact", figma, attach figma, figma link, 关联 figma, 设计稿, figma design, "memory", "记忆", "remember", "record a memory", "记一条", "promote memory", "promote to project", "沉淀", "task memory", "project memory", "lumo memory", "retrieval", "取全文", "load full content", "拉全文", "task slack show", "看 thread", "看 slack thread", "show slack thread", "slack 全文", "task web show", "show web link body", "web 正文", "抓网页正文", "task figma context", "figma metadata", "figma 元数据", "figma 设计上下文", "task comments list", "list comments", "看评论", "评论流", "task pr show", "查看 PR", "show pr", "PR 详情", "pr metadata", "import google doc", "sync google doc", "google drive", "doc import-gdoc", "doc sync", "导入 google 文档", "同步 google 文档", "session wrap", "wrap up session", "收尾", "post progress", "把进度发出去", "progress comment", "进度评论".'
+description: 'Use the Lumo CLI to load task context, manage session bindings, inspect projects and milestones, and create/update/list/show/comment on tasks from the terminal. Activate when: user mentions a Lumo task identifier (LUM-42, LUM-12, etc.), asks to load task background or context, wants to bind, check, or detach a Claude Code session''s task binding, is about to start development work on a specific task, wants to create a new task, list their tasks, view a task, comment on a task, list projects, list milestones, attach a task to a milestone, or update a task''s status/title/description/priority/assignee/milestone. Triggers on: "LUM-", "task context", "load context", "session start", "session attach", "session status", "session detach", "bind session", "unbind session", "which task", "what task am I on", "work on LUM", "create task", "new task", "add task", "file a task", "log a task", "list tasks", "my tasks", "show task", "view task", "comment on task", "leave a comment", "list projects", "what projects", "update task", "change task status", "rename task", "reassign task", "mark task as done", "milestone", "里程碑", "list milestones", "set milestone", "挂到 milestone", "attach milestone", "unbind milestone", "create milestone", "new milestone", "update milestone", "change milestone status", "delete milestone", "show milestone", "view milestone", "tasks in milestone", "milestone tasks", "search milestones", "find milestone", "filter milestones", "milestone search", "搜索里程碑", "查找里程碑", "milestone health", "milestone risk", "risk light", "on-track", "at-risk", "overdue", "里程碑健康度", "健康度", "风险灯", "延期风险", "新建里程碑", "更新里程碑", "删除里程碑", "查看里程碑", "archive milestone", "unarchive milestone", "restore milestone", "archived milestones", "归档里程碑", "恢复里程碑", "取消归档", "milestone summary", "milestone retro", "summarize milestone", "里程碑总结", "里程碑复盘", "milestone reorder", "milestone move", "reorder milestones", "move milestone", "排序里程碑", "调整里程碑顺序", "里程碑调序", "move milestone before", "move milestone after", "milestone add", "milestone remove", "add tasks to milestone", "remove tasks from milestone", "batch milestone", "bulk milestone", "挂任务到里程碑", "批量挂里程碑", "从里程碑移除任务", "auth login", "log in", "login", "auth logout", "log out", "logout", "sign out", "switch account", "switch identity", "whoami", "who am I", "current identity", "current user", "current workspace", "登录", "登出", "切换账号", "当前身份", "create doc", "new doc", "new document", "write doc", "写文档", "新建文档", "update doc", "edit doc", "修改文档", "更新文档", "list docs", "my docs", "我的文档", "show doc", "view doc", "查看文档", "delete doc", "删除文档", "bind doc", "attach doc to task", "把文档关联到任务", "文档绑定到任务", "unbind doc", "解绑文档", "personal doc", "workspace doc", "个人文档", "workspace 文档", "doc scope", "tag", "add tag", "remove tag", "标签", "添加标签", "移除标签", "doc tag", "task tag", "share doc", "doc share", "share document", "分享文档", "文档分享", "unshare doc", "remove share", "取消分享", "share list", "list doc shares", "who has access", "viewer", "editor", "manager", "shared with", "doc tree", "doc move", "move doc", "reparent doc", "文档树", "移动文档", "sprint", "start sprint", "close sprint", "add to sprint", "active sprints", "冲刺", "迭代", "开始冲刺", "关闭冲刺", "create sprint", "new sprint", "list sprints", "show sprint", "update sprint", "delete sprint", "sprint summary", "sprint retro", "把任务挂到冲刺", "冲刺里有什么", "lumo update", "update cli", "upgrade lumo", "update lumo", "upgrade cli", "升级 lumo", "更新 cli", "new lumo version", "是否有新版本", "lumo setup", "install lumo skill", "install lumo hooks", "wire up lumo", "set up lumo", "onboard lumo", "npx @lumoai/cli", "安装 lumo", "配置 lumo", "lumo 初始化", "task artifact", "artifact add", "artifact list", "artifact show", "artifact rm", "artifact delete", "artifact update", "update artifact", "edit artifact", "change artifact kind", "change artifact source", "remove artifact", "delete artifact", "spec artifact", "record spec", "attach spec", "attach plan", "记录 spec", "挂 spec", "查看 artifact", "编辑 artifact", "修改 artifact", "删除 artifact", figma, attach figma, figma link, 关联 figma, 设计稿, figma design, "memory", "记忆", "remember", "record a memory", "记一条", "promote memory", "promote to project", "沉淀", "task memory", "project memory", "lumo memory", "retrieval", "取全文", "load full content", "拉全文", "task slack show", "看 thread", "看 slack thread", "show slack thread", "slack 全文", "task web show", "show web link body", "web 正文", "抓网页正文", "task figma context", "figma metadata", "figma 元数据", "figma 设计上下文", "task comments list", "list comments", "看评论", "评论流", "task pr show", "查看 PR", "show pr", "PR 详情", "pr metadata", "import google doc", "sync google doc", "google drive", "doc import-gdoc", "doc sync", "导入 google 文档", "同步 google 文档", "session wrap", "wrap up session", "收尾", "post progress", "把进度发出去", "progress comment", "进度评论", "mark blocked", "blocked tag", "标 blocked", "标记 blocked", "卡住检测", "反复失败", "stuck", "repeatedly failing", "lumo next", "next task", "what''s next", "what should I work on", "recommend a task", "推荐下一个任务", "pick my next task".'
 ---
 
 ## Prerequisites
@@ -343,7 +343,7 @@ Task LUM-48 has no sprint binding   # noop (already unbound)
 
 The CLI does **not** currently update due date or parent task. Those need to be edited in the web UI.
 
-Milestone updates (`--milestone`) and sprint binding (`--sprint`) both work. Full milestone CRUD is available via `lumo milestone create / show / update / delete`, and tasks can be bound/unbound in bulk via `lumo milestone add / remove <identifier> <task...>` (see below). Full sprint CRUD is available via `lumo sprint create / show / update / delete / start / close / add / remove` (see below).
+Milestone updates (`--milestone`) and sprint binding (`--sprint`) both work. Full milestone CRUD is available via `lumo milestone create / show / update / delete`, tasks can be bound/unbound in bulk via `lumo milestone add / remove <identifier> <task...>`, and milestones can be manually reordered via `lumo milestone reorder <ref...>` / `lumo milestone move <ref> --before|--after <ref>` (see below). Full sprint CRUD is available via `lumo sprint create / show / update / delete / start / close / add / remove` (see below).
 
 ### `lumo task list [flags]` — list tasks assigned to you
 
@@ -370,6 +370,44 @@ Filtering is currently client-side — the server returns the full "my tasks" se
 - The user asks "what am I working on", "what tasks do I have", "list my tasks", "show me my queue".
 - Before suggesting a status change ("mark something as done"), if no task ID is in context — run `task list` first to surface candidates.
 
+### `lumo next [--count <N>]` — recommend the next task to work on
+
+Ranks the tasks assigned to you and prints the top N (default 3), each with a
+one-line reason. Read-only — it does **not** bind or load context. Pick one from
+the list, then run `lumo session attach <LUM-N>` + `lumo task context <LUM-N>`.
+
+Ranking is lexicographic: **priority** (URGENT→LOW) first, then **active-sprint
+membership**, then **due date** (earlier first), then in-flight status
+(IN_PROGRESS / IN_REVIEW ahead of TODO). DONE tasks are excluded. The active
+sprint lookup is best-effort — if it fails the command still recommends, just
+without the sprint boost.
+
+| Flag              | Type    | Notes                                                                   |
+| ----------------- | ------- | ----------------------------------------------------------------------- |
+| `-n, --count <N>` | integer | How many tasks to recommend. Defaults to 3. Must be a positive integer. |
+
+```bash
+lumo next
+lumo next --count 1
+```
+
+Output:
+
+```
+Top 3 recommended tasks (of 12 open):
+
+1. LUM-42  IN_PROGRESS  URGENT  Fix Slack OAuth redirect
+     ↳ URGENT · active sprint · due 2026-06-03 (overdue) · in progress
+2. LUM-48  TODO         HIGH    Investigate slow query
+     ↳ HIGH · active sprint
+3. LUM-12  TODO         MEDIUM  Add rate limiting
+     ↳ MEDIUM · due 2026-06-10
+
+Next: lumo session attach LUM-42 && lumo task context LUM-42
+```
+
+When to suggest: the user asks "what should I work on", "what's next", "推荐下一个任务", "pick my next task", or starts a session without a task in mind. After they choose, run `session attach` + `task context` for the picked task.
+
 ### `lumo task show <identifier>` — print one task's detail
 
 Returns a key:value block for a single task — title, status, priority, project, assignee (with display name from Clerk), URL, and the full description below. Lighter than `task context` because it does not load prior session summaries or memory.
@@ -521,13 +559,35 @@ Prints `<slug>  <Display Name>` lines. The slug column matches the `--project <r
 lumo project list
 ```
 
-### `lumo milestone list [--project <ref>]` — list milestones in a project
+### `lumo milestone list [--project <ref>] [--archived] [--all] [--search <text>]` — list milestones in a project
+
+Prints fixed-width rows: `<STATUS>  <HEALTH>  <target-date or ->  <name>`, sorted by target date asc (nulls last) then created asc.
 
-Prints fixed-width rows: `<STATUS>  <target-date or ->  <name>`, sorted by target date asc (nulls last) then created asc.
+By default, only **non-archived** milestones are listed. Use `--archived` to show **only** archived milestones, or `--all` to show **both** archived and non-archived. Archived rows are marked with a ` (archived)` suffix on the name.
+
+Use `--search <text>` to filter to milestones whose **name or description** contains the text (case-insensitive substring match). It applies **on top of** the archive filter (e.g. `--all --search q3`). A blank/whitespace-only value is ignored (no filtering). The matched text is bounded to 120 chars server-side.
+
+| Flag              | Type    | Notes                                                                                  |
+| ----------------- | ------- | -------------------------------------------------------------------------------------- |
+| `--project <ref>` | string  | Required when the workspace has more than one project. Name or slug, case-insensitive. |
+| `--archived`      | boolean | Show **only** archived milestones (instead of the default non-archived set).           |
+| `--all`           | boolean | Show **both** archived and non-archived milestones.                                    |
+| `--search <text>` | string  | Filter by **name/description** case-insensitive substring. Combines with the archive filter; blank value ignored. |
+
+`HEALTH` is the target-date risk light, server-computed from the milestone's target date + task progress:
+
+- `ON-TRACK` — on schedule (or all tasks done)
+- `AT-RISK` — completion lags elapsed time, or (no start date) the target is within ~7 days with work remaining
+- `OVERDUE` — past the target date with tasks still open
+- `-` — no light applies (status `COMPLETED`/`CANCELLED`, or no target date)
 
 ```bash
-lumo milestone list                  # one-project workspace
+lumo milestone list                  # one-project workspace (non-archived only)
 lumo milestone list --project lumo   # multi-project workspace
+lumo milestone list --archived       # only archived milestones
+lumo milestone list --all            # archived + non-archived (archived marked "(archived)")
+lumo milestone list --search q3      # name/description contains "q3" (case-insensitive)
+lumo milestone list --all --search launch   # search across archived + non-archived
 ```
 
 `--project <ref>` is required when the workspace has more than one project (consistent with `task create --project`). Match is by project name or slug, case-insensitive.
@@ -536,6 +596,7 @@ lumo milestone list --project lumo   # multi-project workspace
 
 - Before suggesting `task create --milestone <ref>` or `task update --milestone <ref>` to confirm the milestone exists under the expected name.
 - When the user asks "what milestones do we have", "what's on v1.0", or similar.
+- When the user wants to **find/search milestones by keyword** ("find the launch milestone", "搜索里程碑", "which milestones mention X") — use `--search <text>` rather than listing all and eyeballing.
 
 When to suggest: before `task create --project <ref>` when the workspace has more than one project and the user hasn't specified which one.
 
@@ -561,7 +622,7 @@ On success: `Created milestone "Q3 Launch"  <id>`.
 
 Accepts UUID or name. With a name, `--project <ref>` is required when the workspace has >1 project.
 
-Prints a key:value header (name, status, dates, project, description), task counts, and the full task table under the milestone.
+Prints a key:value header (name, status, **health**, dates, project, description), task counts, and the full task table under the milestone. The `Health:` line shows the same target-date risk light as `milestone list` (`ON-TRACK` / `AT-RISK` / `OVERDUE`, or `-` when none applies).
 
 ```bash
 lumo milestone show "Q3 Launch"
@@ -595,6 +656,23 @@ Requires `--yes`. No interactive prompt — CLI is agent-friendly. Tasks under t
 lumo milestone delete "Q3 Launch" --yes
 ```
 
+### `lumo milestone archive <identifier>` — soft-archive a milestone
+
+Soft-archives a milestone by setting `archivedAt`. The milestone is **hidden from `milestone list` by default** (use `--archived` or `--all` to see it), but its **history and task links are preserved**, and the action is **reversible** via `milestone unarchive`. This is distinct from `milestone delete`, which is a **hard delete**. While archived, the milestone **rejects edits** (`milestone update`) and **new task bindings** (`task --milestone`, `milestone add`) with a 409 until it is restored. `<identifier>` accepts a UUID or name; `--project <ref>` is required when the identifier is a name and the workspace has >1 project.
+
+```bash
+lumo milestone archive "Q3 Launch"
+lumo milestone archive 11111111-2222-3333-4444-555555555555
+```
+
+### `lumo milestone unarchive <identifier>` — restore an archived milestone
+
+Restores an archived milestone by clearing `archivedAt`. It reappears in `milestone list` and can be edited and bound to tasks again. Idempotent — unarchiving an already-active milestone is a no-op. Same identifier / `--project` rules as `milestone archive`: `<identifier>` accepts a UUID or name; `--project <ref>` is required when the identifier is a name and the workspace has >1 project.
+
+```bash
+lumo milestone unarchive "Q3 Launch"
+```
+
 ### `lumo milestone add <identifier> <task...>` — bind tasks to a milestone (batch)
 
 Binds **one or more** tasks to a milestone in a single call — the batch counterpart of `task update --milestone <ref>` (which only takes one task at a time). `<identifier>` accepts a milestone name or UUID; each `<task>` accepts `LUM-N` or a task UUID. `--project <ref>` is required when the identifier is a name and the workspace has >1 project.
@@ -643,9 +721,9 @@ Prints the AI-generated retrospective summary for a milestone (mirrors `sprint s
 
 A summary is generated automatically when a milestone transitions to `COMPLETED` (e.g. via `lumo milestone update <id> --status completed`). The generated report has sections `## Summary`, `## Delivered`, `## Outstanding` plus a one-line `tldr`. Use `--retry` to queue regeneration (e.g. after a failed generation) before fetching — regeneration is async, so the printed result may still be the previous summary or `(no summary generated yet)`.
 
-| Flag              | Type    | Notes                                                            |
-| ----------------- | ------- | ---------------------------------------------------------------- |
-| `--project <ref>` | string  | Project name or slug. Required when identifier is a name and the workspace has >1 project. |
+| Flag              | Type    | Notes                                                                                                  |
+| ----------------- | ------- | ------------------------------------------------------------------------------------------------------ |
+| `--project <ref>` | string  | Project name or slug. Required when identifier is a name and the workspace has >1 project.             |
 | `--retry`         | boolean | Queue a regeneration (async, server returns 202) before fetching. Only valid on a COMPLETED milestone. |
 
 ```bash
@@ -656,6 +734,50 @@ lumo milestone summary 11111111-2222-3333-4444-555555555555
 
 When to suggest: user asks "summarize the milestone", "milestone retro", "give me a summary of the Q3 milestone", "里程碑总结", "里程碑复盘".
 
+### `lumo milestone reorder <ref...> [--project <ref>]` — set the full milestone order
+
+Reorders a project's milestones. Pass **every** milestone in the project (by name, case-insensitive, or its cuid) in the desired order — the command rewrites each milestone's `sortOrder` to match. An incomplete list (not every milestone named), an unknown ref, or a duplicate is rejected **before any network mutation**, with a message naming the offending / missing milestones.
+
+```bash
+lumo milestone reorder "Q3 Launch" "Beta" "Alpha"
+lumo milestone reorder "Q3 Launch" "Beta" "Alpha" --project backend
+```
+
+`--project <ref>` is required when the workspace has more than one project.
+
+Output:
+
+```
+Reordered 3 milestones:
+  1. Q3 Launch
+  2. Beta
+  3. Alpha
+```
+
+### `lumo milestone move <ref> --before <ref> | --after <ref> [--project <ref>]` — move one milestone
+
+Moves a single milestone immediately before or after a target milestone, leaving the rest in their current relative order. `--before` and `--after` are **mutually exclusive and exactly one is required** (the CLI errors before any network call if both or neither is given). Refs resolve by cuid or case-insensitive name.
+
+```bash
+lumo milestone move "Alpha" --before "Q3 Launch"
+lumo milestone move "Alpha" --after "Beta" --project backend
+```
+
+Output:
+
+```
+Moved "Alpha" before "Q3 Launch". New order:
+  1. Alpha
+  2. Q3 Launch
+  3. Beta
+```
+
+Both commands resolve to a full ordered list client-side and call the same `PATCH /api/projects/<id>/milestones/reorder` endpoint (which requires the list to name every milestone exactly once). New milestones created via `milestone create` are appended to the bottom of the order.
+
+**Ambiguous names:** milestone names are not unique within a project (only the slug is). A ref whose name matches more than one milestone is **rejected** with an `ambiguous milestone name … re-run with the id` error listing the candidate cuids — pass the cuid instead. This applies to every name-based milestone ref (`reorder`, `move`, and also `show` / `update` / `delete` / `summary` / `add` / `remove`).
+
+When to suggest: user asks to "reorder milestones", "排序里程碑", "调整里程碑顺序", "move milestone X before/after Y", "把里程碑 X 移到 Y 前面/后面", "put this milestone first".
+
 ## Document Management
 
 ### `lumo doc create [title] [flags]` — create a new document
@@ -1195,6 +1317,16 @@ auto-bind line, run `lumo session detach` to clear the binding (then `session
 attach <LUM-N>` if they name the right one). No detach is needed when the
 auto-bound task is correct.
 
+### Layer 2 project-memory review at session start
+
+When the session is bound, session-start may inject a **"🆕 待核对：上次会话自动合并的项目级记忆"** section alongside the memory / PR-review blocks (LUM-165). It lists the **PROJECT-scope** memories that the member's **immediately-preceding session** auto-consolidated (Layer 2 runs asynchronously when a task is marked `done`). Each item shows its `id`.
+
+- **Why it's here:** Layer 2 promotions land async, so they can't be reviewed in the synchronous `session wrap` panel — they're surfaced at the _next_ session-start instead, when they've definitely landed.
+- **Show-once:** the section appears only at the session that immediately follows the one that produced the memories. It does **not** re-nag on later sessions, so act on it now or it scrolls off.
+- **Agent guidance:** briefly sanity-check each listed memory against the codebase/context. If one is wrong or over-generalized, remove it with `lumo memory rm <id> --yes` (ideally confirm with the user first). If they all look right, ignore the section and continue.
+
+Attribution requires the CC session id to reach the server: `lumo task update <id> --status done` automatically sends `CLAUDE_CODE_SESSION_ID` (via an `X-Lumo-Session-Id` header) so the resulting Layer 2 memories are attributed to the session. Marking a task done from the **web UI** leaves them unattributed (they won't surface for review) — that's expected.
+
 ### `lumo session attach <identifier>` — bind the current session to a task
 
 Use this whenever the user mentions a task ID. The command is the only way to bind a session to a task.
@@ -1235,27 +1367,64 @@ lumo session detach
 
 When to suggest: the user wants to stop tagging the current session with the active task (e.g., switching to unrelated exploratory work without binding to a different task).
 
-### `lumo session wrap [--yes] [--dry-run]` — draft + post a progress comment at wrap-up
+### `lumo session wrap [--yes] [--dry-run]` — wrap-up panel: progress comment + memory review + blocked-tag prompt
+
+Session-end wrap-up panel with **three sections, run in order**:
 
-Session-end wrap-up panel. Reads back the current Claude Code session's per-turn
+**1. 进度评论** — reads back the current Claude Code session's per-turn
 `turnSummary` rows (the one-line Chinese summaries written each STOP), aggregates
 every turn **since the last progress comment** into one bulleted body, and — after
 a `[y] 发送 / [e] 编辑 / [s] 跳过` confirmation — posts it as a comment on the
 session's bound task. A server-side watermark (`Session.lastProgressCommentAt`)
 means re-running never re-posts the same turns.
 
+**2. 记忆审阅** — lists the Layer1 memories this session sedimented since the
+last review (deduped by a per-session watermark `Session.lastMemoryReviewAt`).
+Each new memory is shown as `[SCOPE] CATEGORY  headline`, numbered from 1. You
+curate with a single line: `d 1,3` deletes rows 1 and 3, `p 2` promotes row 2 to
+project scope, and they combine (`d 1,3 p 2`). **回车 (empty) keeps all**; `s`
+skips the section. Keeping all (回车 or `--yes`) still **advances the watermark**
+so the next wrap won't re-list reviewed memories; `s` leaves them for next time.
+Out-of-range indices are ignored. Deletes/promotes run server-side, scoped to
+memories this session created (you can't touch other sessions' memories through
+this panel). With no new memories the section prints "(无内容)" and does nothing.
+
+**3. 卡住检测 (blocked-tag prompt, LUM-153)** — if the **same kind of failure
+recurred ≥ 3 times** in this session (server-aggregated from
+`POST_TOOL_USE_FAILURE` events grouped by tool name, plus `STOP_FAILURE`
+turn-level failures), the section surfaces the dominant failure (`卡在 <tool>
+(N 次失败)` + last error summary) and prompts `[y] 标记 / [s] 跳过` whether to
+flag the bound task with a **`blocked` tag**. **Prompt-only — never auto-flips
+status.** It uses a plain tag (no `TaskStatus` enum, no board column, **no
+schema migration**). The prompt is **suppressed** when: there's no bound task,
+the threshold isn't met, or the task **already** carries a `blocked` tag (the
+idempotent gate — there's no watermark, the existing tag is what prevents
+re-nagging). The default on empty input / `s` is **do nothing** (tagging is
+opt-in), so a stray Enter never tags the task. Confirming with an explicit `y`
+attaches the tag idempotently. **`--yes` does NOT auto-tag** — tagging the
+shared board requires an interactive `y`, so `--yes` (and non-TTY) prints the
+suggestion and moves on rather than silently flipping board state. When there's
+nothing to prompt, the section prints "(无内容)".
+
 ```bash
-lumo session wrap            # interactive: preview draft, choose y / e / s
-lumo session wrap --yes      # post the drafted body without prompting (agent-friendly)
-lumo session wrap --dry-run  # print the draft only; never posts, never advances watermark
+lumo session wrap            # interactive: preview each section, choose per-section
+lumo session wrap --yes      # progress posted + memories kept; blocked tag NOT auto-applied (needs interactive y)
+lumo session wrap --dry-run  # print all drafts only; never posts, never mutates, never advances watermarks
 ```
 
 - Requires `$CLAUDE_CODE_SESSION_ID` (must run inside Claude Code) and a bound
   task (`lumo session attach <LUM-N>` first). With no bound task or no new turn
-  summaries, the panel prints "(无内容)" and posts nothing.
-- `[e] 编辑` opens `$EDITOR` (fallback vi/nano) on the drafted body; the edited
-  text is posted and the watermark still advances to the turns the draft covered.
-- Non-TTY without `--yes`: prints the draft and does **not** post (safe default).
+  summaries, the 进度评论 section prints "(无内容)" and posts nothing.
+- `[e] 编辑` (进度评论) opens `$EDITOR` (fallback vi/nano) on the drafted body;
+  the edited text is posted and the watermark still advances to the turns the
+  draft covered.
+- `--yes` posts the progress comment AND keeps all memories (no
+  deletes/promotes) while advancing the memory-review watermark; for the
+  blocked-tag section it prints the suggestion but does **not** apply the tag.
+- `--dry-run` prints all drafts; never posts, never mutates memories/tags, never
+  advances either watermark.
+- Non-TTY without `--yes`: prints the drafts and does **not** post, mutate, or
+  tag (safe default).
 
 When to suggest: at the end of a working session on a bound task, to record what
 was done as a progress comment — offer `lumo session wrap` rather than composing

package/dist/cli/src/commands/milestone-archive.js

@@ -0,0 +1,60 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.formatArchiveResult = formatArchiveResult;
+exports.milestoneArchive = milestoneArchive;
+const config_1 = require("../lib/config");
+const api_1 = require("../lib/api");
+const resolve_1 = require("../lib/resolve");
+const sanitize_1 = require("../lib/sanitize");
+function formatArchiveResult(name) {
+    return `Archived "${(0, sanitize_1.sanitizeField)(name)}"`;
+}
+async function milestoneArchive(identifier, opts) {
+    const creds = (0, config_1.readCredentials)();
+    if (!creds) {
+        console.error('Error: not logged in. Run `lumo auth login` first.');
+        return 1;
+    }
+    const apiUrl = (0, api_1.resolveAuthedApiUrl)(creds.apiUrl);
+    const base = (0, api_1.trimTrailingSlash)(apiUrl);
+    let milestoneId;
+    try {
+        const resolved = await (0, resolve_1.resolveMilestoneId)(base, creds.token, identifier, opts.project);
+        milestoneId = resolved.id;
+    }
+    catch (err) {
+        console.error(`Error: ${err instanceof Error ? err.message : String(err)}`);
+        return 1;
+    }
+    let res;
+    try {
+        res = await fetch(`${base}/api/milestones/${milestoneId}/archive`, {
+            method: 'POST',
+            headers: { Authorization: `Bearer ${creds.token}` },
+        });
+    }
+    catch (err) {
+        const msg = err instanceof Error ? err.message : String(err);
+        console.error(`Error: could not reach Lumo API at ${apiUrl} (${msg})`);
+        return 1;
+    }
+    if (res.status === 401) {
+        console.error('Error: API key invalid or revoked. Run `lumo auth login`.');
+        return 1;
+    }
+    if (!res.ok) {
+        let errMsg = `milestone archive failed (HTTP ${res.status})`;
+        try {
+            const body = (await res.json());
+            if (body.error)
+                errMsg = body.error;
+        }
+        catch {
+            // non-JSON body; keep the status-only message
+        }
+        console.error(`Error: ${(0, sanitize_1.sanitizeField)(errMsg)}`);
+        return 1;
+    }
+    const { milestone } = (await res.json());
+    process.stdout.write(formatArchiveResult(milestone.name) + '\n');
+}

package/dist/cli/src/commands/milestone-list.js

@@ -6,6 +6,14 @@ const config_1 = require("../lib/config");
 const api_1 = require("../lib/api");
 const resolve_1 = require("../lib/resolve");
 const sanitize_1 = require("../lib/sanitize");
+const HEALTH_LABEL = {
+    'on-track': 'ON-TRACK',
+    'at-risk': 'AT-RISK',
+    overdue: 'OVERDUE',
+};
+function formatHealth(health) {
+    return health ? HEALTH_LABEL[health] : '-';
+}
 function formatDate(iso) {
     if (!iso)
         return '-';
@@ -13,7 +21,10 @@ function formatDate(iso) {
 }
 /**
  * Render milestones as fixed-width rows:
- *   <STATUS>  <target-date or ->  <name>
+ *   <STATUS>  <HEALTH>  <target-date or ->  <name>
+ *
+ * HEALTH is the target-date risk light (ON-TRACK / AT-RISK / OVERDUE), or `-`
+ * when no light applies (terminal status or no target date).
  *
  * Sorted server-side by targetDate asc nulls last, createdAt asc.
  */
@@ -21,9 +32,10 @@ function formatMilestoneList(rows) {
     if (rows.length === 0)
         return 'No milestones.';
     const statusW = Math.max(...rows.map(r => r.status.length));
+    const healthW = Math.max(...rows.map(r => formatHealth(r.health).length));
     const dateW = Math.max(...rows.map(r => formatDate(r.targetDate).length));
     return rows
-        .map(r => `${r.status.padEnd(statusW)}  ${formatDate(r.targetDate).padEnd(dateW)}  ${(0, sanitize_1.sanitizeField)(r.name)}`)
+        .map(r => `${r.status.padEnd(statusW)}  ${formatHealth(r.health).padEnd(healthW)}  ${formatDate(r.targetDate).padEnd(dateW)}  ${r.archivedAt ? `${(0, sanitize_1.sanitizeField)(r.name)} (archived)` : (0, sanitize_1.sanitizeField)(r.name)}`)
         .join('\n');
 }
 async function milestoneList(options) {
@@ -43,9 +55,16 @@ async function milestoneList(options) {
         console.error(`Error: ${msg}`);
         return 1;
     }
-    const res = await fetch(`${base}/api/projects/${projectId}/milestones`, {
-        headers: { Authorization: `Bearer ${creds.token}` },
-    });
+    if (options.archived && options.all) {
+        console.error('Error: --archived and --all are mutually exclusive.');
+        return 1;
+    }
+    const filter = options.all ? 'all' : options.archived ? 'archived' : 'active';
+    const query = new URLSearchParams({ filter });
+    const term = options.search?.trim();
+    if (term)
+        query.set('search', term);
+    const res = await fetch(`${base}/api/projects/${projectId}/milestones?${query.toString()}`, { headers: { Authorization: `Bearer ${creds.token}` } });
     if (!res.ok) {
         console.error(`Error: milestone list failed (HTTP ${res.status})`);
         return 1;

package/dist/cli/src/commands/milestone-move.js

@@ -0,0 +1,84 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.milestoneMove = milestoneMove;
+const config_1 = require("../lib/config");
+const api_1 = require("../lib/api");
+const resolve_1 = require("../lib/resolve");
+const sanitize_1 = require("../lib/sanitize");
+const milestone_reorder_1 = require("../lib/milestone-reorder");
+async function milestoneMove(reference, opts) {
+    if (!reference) {
+        console.error('Error: usage: lumo milestone move <ref> --before <ref> | --after <ref>');
+        return 1;
+    }
+    const hasBefore = typeof opts.before === 'string' && opts.before.length > 0;
+    const hasAfter = typeof opts.after === 'string' && opts.after.length > 0;
+    if (hasBefore && hasAfter) {
+        console.error('Error: --before and --after are mutually exclusive');
+        return 1;
+    }
+    if (!hasBefore && !hasAfter) {
+        console.error('Error: specify --before <ref> or --after <ref>');
+        return 1;
+    }
+    const creds = (0, config_1.readCredentials)();
+    if (!creds) {
+        console.error('Error: not logged in. Run `lumo auth login` first.');
+        return 1;
+    }
+    const apiUrl = (0, api_1.resolveAuthedApiUrl)(creds.apiUrl);
+    const base = (0, api_1.trimTrailingSlash)(apiUrl);
+    let projectId;
+    try {
+        projectId = await (0, resolve_1.resolveProjectId)(base, creds.token, opts.project);
+    }
+    catch (err) {
+        console.error(`Error: ${err instanceof Error ? err.message : String(err)}`);
+        return 1;
+    }
+    const listRes = await fetch(`${base}/api/projects/${projectId}/milestones`, {
+        headers: { Authorization: `Bearer ${creds.token}` },
+    });
+    if (!listRes.ok) {
+        console.error(`Error: milestone list failed (HTTP ${listRes.status})`);
+        return 1;
+    }
+    const { milestones } = (await listRes.json());
+    const refRows = milestones.map(m => ({
+        id: m.id,
+        name: m.name,
+        sortOrder: m.sortOrder,
+    }));
+    const position = hasBefore ? 'before' : 'after';
+    const targetRef = (hasBefore ? opts.before : opts.after);
+    const resolved = (0, milestone_reorder_1.computeMoveOrder)(reference, targetRef, position, refRows);
+    if (!resolved.ok) {
+        console.error(`Error: ${resolved.error}`);
+        return 1;
+    }
+    const patchRes = await fetch(`${base}/api/projects/${projectId}/milestones/reorder`, {
+        method: 'PATCH',
+        headers: {
+            Authorization: `Bearer ${creds.token}`,
+            'Content-Type': 'application/json',
+        },
+        body: JSON.stringify({ orderedIds: resolved.orderedIds }),
+    });
+    if (!patchRes.ok) {
+        const text = await patchRes.text();
+        let msg = text;
+        try {
+            const json = JSON.parse(text);
+            if (json.error)
+                msg = json.error;
+        }
+        catch { }
+        console.error(`Error: ${patchRes.status} ${patchRes.statusText}: ${(0, sanitize_1.sanitizeField)(msg)}`);
+        return 1;
+    }
+    const byId = new Map(refRows.map(m => [m.id, m.name]));
+    console.log(`Moved "${(0, sanitize_1.sanitizeField)(reference)}" ${position} "${(0, sanitize_1.sanitizeField)(targetRef)}". New order:`);
+    resolved.orderedIds.forEach((id, i) => {
+        console.log(`  ${i + 1}. ${(0, sanitize_1.sanitizeField)(byId.get(id) ?? id)}`);
+    });
+}

package/dist/cli/src/commands/milestone-reorder.js

@@ -0,0 +1,72 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.milestoneReorder = milestoneReorder;
+const config_1 = require("../lib/config");
+const api_1 = require("../lib/api");
+const resolve_1 = require("../lib/resolve");
+const sanitize_1 = require("../lib/sanitize");
+const milestone_reorder_1 = require("../lib/milestone-reorder");
+async function milestoneReorder(refs, opts) {
+    if (!refs || refs.length === 0) {
+        console.error('Error: usage: lumo milestone reorder <ref...> [--project <ref>]');
+        return 1;
+    }
+    const creds = (0, config_1.readCredentials)();
+    if (!creds) {
+        console.error('Error: not logged in. Run `lumo auth login` first.');
+        return 1;
+    }
+    const apiUrl = (0, api_1.resolveAuthedApiUrl)(creds.apiUrl);
+    const base = (0, api_1.trimTrailingSlash)(apiUrl);
+    let projectId;
+    try {
+        projectId = await (0, resolve_1.resolveProjectId)(base, creds.token, opts.project);
+    }
+    catch (err) {
+        console.error(`Error: ${err instanceof Error ? err.message : String(err)}`);
+        return 1;
+    }
+    const listRes = await fetch(`${base}/api/projects/${projectId}/milestones`, {
+        headers: { Authorization: `Bearer ${creds.token}` },
+    });
+    if (!listRes.ok) {
+        console.error(`Error: milestone list failed (HTTP ${listRes.status})`);
+        return 1;
+    }
+    const { milestones } = (await listRes.json());
+    const refRows = milestones.map(m => ({
+        id: m.id,
+        name: m.name,
+        sortOrder: m.sortOrder,
+    }));
+    const resolved = (0, milestone_reorder_1.resolveOrderedIds)(refs, refRows);
+    if (!resolved.ok) {
+        console.error(`Error: ${resolved.error}`);
+        return 1;
+    }
+    const patchRes = await fetch(`${base}/api/projects/${projectId}/milestones/reorder`, {
+        method: 'PATCH',
+        headers: {
+            Authorization: `Bearer ${creds.token}`,
+            'Content-Type': 'application/json',
+        },
+        body: JSON.stringify({ orderedIds: resolved.orderedIds }),
+    });
+    if (!patchRes.ok) {
+        const text = await patchRes.text();
+        let msg = text;
+        try {
+            const json = JSON.parse(text);
+            if (json.error)
+                msg = json.error;
+        }
+        catch { }
+        console.error(`Error: ${patchRes.status} ${patchRes.statusText}: ${(0, sanitize_1.sanitizeField)(msg)}`);
+        return 1;
+    }
+    const byId = new Map(refRows.map(m => [m.id, m.name]));
+    console.log(`Reordered ${resolved.orderedIds.length} milestones:`);
+    resolved.orderedIds.forEach((id, i) => {
+        console.log(`  ${i + 1}. ${(0, sanitize_1.sanitizeField)(byId.get(id) ?? id)}`);
+    });
+}

package/dist/cli/src/commands/milestone-show.js

@@ -7,9 +7,17 @@ const api_1 = require("../lib/api");
 const resolve_1 = require("../lib/resolve");
 const format_1 = require("../lib/format");
 const sanitize_1 = require("../lib/sanitize");
+const HEALTH_LABEL = {
+    'on-track': 'ON-TRACK',
+    'at-risk': 'AT-RISK',
+    overdue: 'OVERDUE',
+};
 function fmtDate(iso) {
     return iso ? iso.slice(0, 10) : '-';
 }
+function fmtHealth(health) {
+    return health ? HEALTH_LABEL[health] : '-';
+}
 function formatMilestoneShow(m, tasks) {
     const total = m.taskCounts.TODO +
         m.taskCounts.IN_PROGRESS +
@@ -18,6 +26,8 @@ function formatMilestoneShow(m, tasks) {
     const lines = [
         `Milestone:    ${(0, sanitize_1.sanitizeField)(m.name)}`,
         `Status:       ${m.status}`,
+        `Archived:     ${m.archivedAt ? m.archivedAt.slice(0, 10) : 'no'}`,
+        `Health:       ${fmtHealth(m.health)}`,
         `Start:        ${fmtDate(m.startDate)}`,
         `Target:       ${fmtDate(m.targetDate)}`,
         `Project:      ${(0, sanitize_1.sanitizeField)(m.projectName)}`,
@@ -99,8 +109,10 @@ async function milestoneShow(identifier, opts) {
         status: milestone.status,
         startDate: milestone.startDate,
         targetDate: milestone.targetDate,
+        archivedAt: milestone.archivedAt,
         description: milestone.description,
         projectName,
         taskCounts: milestone.taskCounts,
+        health: milestone.health,
     }, tasks) + '\n');
 }