ooodc a7883dbed9 refactor(todo): 重构待办事项管理逻辑及更新状态规则

- 移除 TodoItem 中的 priority、created_at 和 updated_at 字段
- 强制每个任务都必须有唯一 id，且由用户负责生成
- 修改合并模式逻辑，merge=true 下保留未提及的旧任务
- 支持已完成和已取消任务重新激活（状态改回 pending 或 in_progress）
- 禁止 in_progress 状态退回到 pending，必须标记为 completed 或 cancelled
- 优化状态转换校验，允许特定状态间合法切换
- 简化任务变更消息，移除详细的新增/更新/移除统计
- 更新文档和示例，明确 id 必须由用户生成和使用
- 修复和补充测试，增强状态转换和合并模式验证
- 调整任务时间戳生成逻辑，统一使用当前时间及索引
- 该变更提供更合理的任务状态机械及管理模式，提升稳定性和易用性

2026-06-13 09:22:33 +08:00

2.9 KiB

Raw Blame History

im +flag-cancel

Prerequisite: Read ../lark-shared/SKILL.md for authentication, global parameters, and security rules.

This skill maps to shortcut: lark-cli im +flag-cancel. Underlying API: POST /open-apis/im/v1/flags/cancel.

Double-Cancel Behavior (Important)

A message can have flags on both layers simultaneously:

Message layer: (default, message)
Feed layer: (thread, feed) or (msg_thread, feed) depending on chat type

When no --flag-type is specified, the shortcut performs best-effort double-cancel: the message-layer flag is always removed; the feed-layer flag is also removed when the chat type can be determined (otherwise a warning is printed on stderr and the feed layer is skipped). The server handles cancel requests for non-existent flags idempotently, so this is safe.

Feed layer item_type is determined by chat_mode:

Topic-style chat (chat_mode=topic) → item_type=thread
Regular chat (chat_mode=group) → item_type=msg_thread

Commands

# Double-cancel both layers (recommended default)
lark-cli im +flag-cancel --as user --message-id om_xxx

# Only cancel message layer
lark-cli im +flag-cancel --as user --message-id om_xxx --flag-type message

# Only cancel feed layer (need to specify item-type)
lark-cli im +flag-cancel --as user --message-id om_xxx --item-type thread --flag-type feed

# Preview request
lark-cli im +flag-cancel --as user --message-id om_xxx --dry-run

Parameters

Parameter	Required	Description
`--message-id <om_xxx>`	Required	Message ID
`--flag-type <name>`	No	`message` or `feed`; when omitted, best-effort double-cancel of both layers
`--item-type <name>`	No	`default\|thread\|msg_thread`; required when `--flag-type feed`
`--as user`	Required	Currently only supports user identity

Idempotency

The server doesn't return an error for cancel requests when the flag doesn't exist, so repeated +cancel calls are idempotent.

Permissions

Required scopes: im:feed.flag:write, im:message.group_msg:get_as_user, im:message.p2p_msg:get_as_user, im:chat:read
The message/chat read scopes are used by the default double-cancel path to auto-detect the feed-layer item type.

Note

Do not call +flag-list for verification: If the cancel API returns success, the flag is removed. Calling +flag-list to verify is expensive (requires full pagination) and unnecessary.

Finding Message ID Efficiently

If you have message content but not the message ID:

Use +messages-search to find the message by content, then extract message_id from the result
Do NOT use +flag-list to find the message — it requires full pagination and is very inefficient

# Search by message content to find message_id
lark-cli im +messages-search --as user --query "message content here" -q '.data.items[0].message_id'

2.9 KiB Raw Blame History