ooodc
a7883dbed9
- 移除 TodoItem 中的 priority、created_at 和 updated_at 字段 - 强制每个任务都必须有唯一 id，且由用户负责生成 - 修改合并模式逻辑，merge=true 下保留未提及的旧任务 - 支持已完成和已取消任务重新激活（状态改回 pending 或 in_progress） - 禁止 in_progress 状态退回到 pending，必须标记为 completed 或 cancelled - 优化状态转换校验，允许特定状态间合法切换 - 简化任务变更消息，移除详细的新增/更新/移除统计 - 更新文档和示例，明确 id 必须由用户生成和使用 - 修复和补充测试，增强状态转换和合并模式验证 - 调整任务时间戳生成逻辑，统一使用当前时间及索引 - 该变更提供更合理的任务状态机械及管理模式，提升稳定性和易用性
55 lines
2.3 KiB
Markdown
55 lines
2.3 KiB
Markdown
# Minutes Events
|
|
|
|
> **Prerequisite:** Read [`../SKILL.md`](../SKILL.md) first for the `event consume` essentials (commands, subprocess contract, jq usage).
|
|
|
|
## Key catalog (1)
|
|
|
|
| EventKey | Purpose |
|
|
|---|---|
|
|
| `minutes.minute.generated_v1` | A minute (妙记) has been generated |
|
|
|
|
This key uses a **Custom schema** (flat output at `.xxx`) and carries a **PreConsume hook** that auto-subscribes / unsubscribes via OAPI on first / last consumer.
|
|
|
|
## Scopes & auth
|
|
|
|
| EventKey | Scope | Auth |
|
|
|---|---|---|
|
|
| `minutes.minute.generated_v1` | `minutes:minutes.basic:read` | user |
|
|
|
|
Requires `--as user`.
|
|
|
|
## `minutes.minute.generated_v1`
|
|
|
|
### Output fields
|
|
|
|
| Field | Type | Description |
|
|
|---|---|---|
|
|
| `type` | string | Event type; always `minutes.minute.generated_v1` |
|
|
| `event_id` | string | Globally unique event ID; safe for deduplication |
|
|
| `timestamp` | string (timestamp_ms) | Event delivery time (ms timestamp string) |
|
|
| `minute_token` | string | Minute token |
|
|
| `title` | string | Minute title (enriched via detail API) |
|
|
| `minute_source` | object | Minute source metadata; only present when the source is a meeting |
|
|
| `minute_source.source_type` | string | Source type; only present when the source is a meeting (value: `meeting`) |
|
|
| `minute_source.source_entity_id` | string | Source entity ID (meeting ID); only present when the source is a meeting |
|
|
|
|
### Enrichment & degradation
|
|
|
|
The Process hook calls `GET /open-apis/minutes/v1/minutes/{minute_token}` to enrich `title`. If the detail API fails, this field is left empty — the base fields (`type`, `event_id`, `timestamp`, `minute_token`, `minute_source`) are always present.
|
|
|
|
`minute_source` is populated from the event payload directly (not the detail API), so it survives enrichment failures. Note: `minute_source` is only present when the minute originates from a meeting; for other sources (e.g. recording, local upload) this field is absent.
|
|
|
|
### Example
|
|
|
|
```bash
|
|
lark-cli event consume minutes.minute.generated_v1 --as user
|
|
|
|
# Project title and token only (skip events where enrichment failed)
|
|
lark-cli event consume minutes.minute.generated_v1 --as user \
|
|
--jq 'select(.title != "") | {minute_token, title}'
|
|
|
|
# Filter by source type
|
|
lark-cli event consume minutes.minute.generated_v1 --as user \
|
|
--jq 'select(.minute_source.source_type == "meeting") | {minute_token, title}'
|
|
```
|