@loom-framework/core 0.1.0-alpha.180 → 0.1.0-alpha.181

package/builtin-skills/app-skill/references/process-builder.md

@@ -1,47 +1,47 @@
-# Process Builder Guide
+# Process 构建指南
 
-## Purpose
+## 目的
 
-This guide helps AI assistants create Processes for users. When a user says "I want to automate X" or "run Y every day", use this guide to build a process definition.
+本指南帮助 AI 助手为用户创建 Process。当用户说"我想自动化 X"或"每天运行 Y"时，使用本指南构建流程定义。
 
-## Lightweight vs Full Decision
+## 轻量模式 vs 完整模式选择
 
-### Use Lightweight (`--prompt`) when:
-- Single, simple task
-- No reference files needed
-- Prompt fits in a few sentences
-- No metrics dashboard needed
+### 使用轻量模式（`--prompt`）的场景：
+- 单一、简单的任务
+- 不需要引用文件
+- 提示词几句话就能描述清楚
+- 不需要指标仪表盘
 
-### Use Full (`--process`) when:
-- Multi-step workflow with decision points
-- Reference documentation needed (API docs, data schemas, style guides)
-- Metrics dashboard desired
-- Process may evolve over time (Evolution section)
+### 使用完整模式（`--process`）的场景：
+- 多步骤工作流，包含判断节点
+- 需要参考文档（API 文档、数据模型、样式指南）
+- 需要指标仪表盘
+- 流程可能随时间演进（Evolution 章节）
 
-## Step-by-Step Creation
+## 逐步创建
 
-### 1. Analyze the Request
+### 1. 分析需求
 
-Identify:
-- **What** the process should do
-- **When** it should run (schedule or event trigger)
-- **Who** owns it (username for service token)
-- **Which model** should run it (use `loom model list` to see available models; fast for simple tasks, max for complex reasoning; omit to use global default)
-- **Complexity** (lightweight vs full)
+明确：
+- **做什么** — 流程应该执行什么操作
+- **何时运行** — 定时调度还是事件触发
+- **谁负责** — 服务令牌对应的用户名（owner）
+- **用哪个模型** — 使用 `loom model list` 查看可用模型；简单任务用快速模型，复杂推理用最大模型；省略则使用全局默认
+- **复杂度** — 轻量还是完整
 
-### 2. Choose Trigger
+### 2. 选择触发方式
 
-| Need | Use | Example |
-|------|-----|---------|
-| Periodic schedule | `--cron` | `0 9 * * 1-5` (weekdays 9am) |
-| On data change | `--on-event` | `data:create:tasks` |
-| On user action | `--on-event` | `user:created` |
-| External data source | `--source` | `--source "bash feeders/my-feeder.sh"` |
-| Manual only | Neither | Just `loom process run` |
+| 需求 | 使用 | 示例 |
+|------|-----|------|
+| 定时调度 | `--cron` | `0 9 * * 1-5`（工作日每天9点） |
+| 数据变更时 | `--subscribe` | `data:create:tasks` |
+| 用户操作时 | `--subscribe` | `user:created` |
+| 外部数据源 | `--source` | `--source "bash feeders/my-feeder.sh"` |
+| 仅手动触发 | 都不用 | 直接 `loom process run` |
 
-### 3. Create the Process
+### 3. 创建流程
 
-For lightweight:
+轻量模式：
 ```bash
 loom process add --name "task-summary" \
   --cron "0 9 * * *" \
@@ -50,148 +50,142 @@ loom process add --name "task-summary" \
   --model "claude-sonnet-4-6"
 ```
 
-For full:
+完整模式：
 ```bash
-# Step 1: Generate scaffold
+# 步骤 1：生成脚手架
 loom process generate weekly-report --description "Weekly analytics report"
 
-# Step 2: Edit PROCESS.md with detailed flow
-# (AI should write the PROCESS.md content)
+# 步骤 2：编辑 PROCESS.md，填写详细流程
+# （AI 应编写 PROCESS.md 内容）
 
-# Step 3: Add reference files if needed
-# If this process requires additional context, create the references directory
-# and add files that the AI agent will need during execution:
+# 步骤 3：按需添加引用文件
+# 如果流程需要额外上下文，创建 references 目录
+# 并添加 AI 代理执行时需要的文件：
 mkdir -p .loom/processes/weekly-report/references
-# Then add reference files such as:
-#   - Skill references (CLI command usage, API docs)
-#   - Domain knowledge (data schemas, business rules)
-#   - Scripts or tools (data transforms, query templates)
-# Only create the directory when reference files are actually needed.
-# Skip this step if no additional context is required.
-
-# Step 4: Register the process
+# 然后添加引用文件，例如：
+#   - Skill 引用（CLI 命令用法、API 文档）
+#   - 领域知识（数据模型、业务规则）
+#   - 脚本或工具（数据转换、查询模板）
+# 仅在确实需要引用文件时才创建该目录。
+# 无需额外上下文时跳过此步骤。
+
+# 步骤 4：注册流程
 loom process add --name "weekly-report" \
   --cron "0 9 * * 1" \
   --process "weekly-report" \
   --owner admin
 
-# Step 5: Initialize metrics view config (if PROCESS.md has ## Metrics section)
-# Design the view config based on ## Metrics section (see "Initializing Metrics Visualization" below)
-# Then write it using metrics-set-view-config:
+# 步骤 5：初始化指标视图配置（如果 PROCESS.md 中有 ## Metrics 章节才需要）
+# 根据 ## Metrics 章节设计视图配置（见下方"初始化指标可视化"）
+# 然后使用 metrics-set-view-config 写入：
 loom process metrics-set-view-config weekly-report --config @./view-config.json
 ```
 
-### Event-triggered process with Feeder source
+### 事件触发 + Feeder 数据源
 
-When the process needs a persistent data source (e.g., DingTalk messages, webhooks), use `--source` to declare a Feeder script:
+当流程需要持久数据源（如钉钉消息、Webhook）时，使用 `--source` 声明 Feeder 脚本：
 
 ```bash
-# Step 1: Generate scaffold (if full mode)
+# 步骤 1：生成脚手架（如果是完整模式）
 loom process generate ingest --description "AI semantic router for incoming messages"
 
-# Step 2: Edit PROCESS.md with routing logic
+# 步骤 2：编辑 PROCESS.md，编写路由逻辑
 # ...
 
-# Step 3: Register with Feeder source
+# 步骤 3：注册时指定 Feeder 数据源
 loom process add --name "ingest" \
-  --on-event "dingtalk:mention" \
+  --subscribe "dingtalk:mention" \
   --source "bash examples/feeders/dingtalk-mention.sh" \
   --process "ingest" \
   --owner admin
 ```
 
-**When to use `--source`:**
-- Process needs a persistent external data source (DingTalk, Git webhook, scanner, etc.)
-- The Feeder should run as long as the Loom instance is running
-- You want auto-restart and backoff for the Feeder
+**何时使用 `--source`：**
+- 流程需要持久的外部数据源（钉钉、Git Webhook、扫描器等）
+- Feeder 应随 Loom 实例的运行持续运行
+- 需要 Feeder 的自动重启和退避机制
 
-**Feeder script requirements:**
-- Trap SIGTERM/SIGINT and exit 0 for graceful shutdown
-- Use `$LOOM_SERVER_URL` instead of hardcoded URLs
-- Exit code 0 = normal stop (no restart); non-zero = crash (auto-restart)
-- Write data to `POST $LOOM_SERVER_URL/api/v1/events/notify`
+Feeder 脚本要求、生命周期事件、清理机制详见 **`process.md` → Source (Feeder)**。
 
-**Cleanup:** Removing the process with `loom process remove` automatically stops the Feeder if no other process subscribes to the same event pattern.
-
-### 4. Verify
+### 4. 验证
 
 ```bash
 loom process status <name>
-loom process run <name>  # manual test
-loom process logs <name>  # check result
+loom process run <name>  # 手动测试
+loom process logs <name>  # 查看结果
 ```
 
-## PROCESS.md Best Practices
+## PROCESS.md 最佳实践
 
-### Structure
+### 结构
 
 ```markdown
 # Process: <name>
 
 ## Description
-What this process does and why.
+此流程的功能及目的。
 
 ## Trigger
-When it runs and what triggers it.
+运行时机和触发条件。
 
 ## Flow
-Step-by-step instructions:
-1. Read data from <model>
-2. Analyze <something>
-3. Write results to <model>
-4. Send notification with execution result via `loom notification send`
+逐步指令：
+1. 从 <model> 读取数据
+2. 分析 <something>
+3. 将结果写入 <model>
+4. 通过 `loom notification send` 发送执行结果通知
 
 ## Decision Points
-Key decisions the AI should make:
-- If X, do Y
-- If Z, skip to step N
+AI 应做出的关键判断：
+- 如果 X，执行 Y
+- 如果 Z，跳到步骤 N
 
 ## Metrics
-How success is measured:
-- Execution time < N seconds
-- Error rate < X%
-- Output quality: <criteria>
+如何衡量成功：
+- 执行时间 < N 秒
+- 错误率 < X%
+- 输出质量：<标准>
 
 ## Evolution
-How this process should improve:
-- After N runs, review and optimize prompt
-- Track common errors and add handling
+此流程应如何改进：
+- 运行 N 次后，回顾并优化提示词
+- 追踪常见错误并添加处理逻辑
 
 ## References
-_List files in the `references/` directory that support this process:_
-- _Skill references (e.g., CLI command usage, API docs)_
-- _Domain knowledge (e.g., data schemas, business rules)_
-- _Scripts or tools (e.g., data transforms, query templates)_
-_Only create the `references/` directory and add files when needed._
+_列出 `references/` 目录中支持此流程的文件：_
+- _Skill 引用（如 CLI 命令用法、API 文档）_
+- _领域知识（如数据模型、业务规则）_
+- _脚本或工具（如数据转换、查询模板）_
+_仅在需要时才创建 `references/` 目录并添加文件。_
 ```
 
-### Tips
-- Be specific in Flow steps — AI follows them literally
-- Include data model names and field names
-- Reference CLI commands: `loom data list <model>`, `loom data create <model>`
-- Use `loom data` commands for data operations, not direct file I/O
-- Include error handling in Decision Points
-- Add a notification step at the end of Flow to send execution results to yourself: `loom notification send --userId <owner> --type success --title "Process completed" --description "Summary of results" --token $LOOM_TOKEN`
-- If your process needs strong reasoning, specify a max-level model via `--model` when creating it. Fast models are best for simple data aggregations.
+### 技巧
+- Flow 步骤要具体 — AI 会严格按字面执行
+- 包含数据模型名称和字段名称
+- 引用 CLI 命令：`loom data list <model>`、`loom data create <model>`
+- 数据操作使用 `loom data` 命令，而非直接文件 I/O
+- 在 Decision Points 中包含错误处理
+- 在 Flow 末尾添加通知步骤，将执行结果发送给自己：`loom notification send --userId <owner> --type success --title "Process completed" --description "Summary of results" --token $LOOM_TOKEN`
+- 如果流程需要强推理能力，创建时通过 `--model` 指定最大级别模型。简单数据聚合任务使用快速模型即可。
 
-## Metrics Definition
+## 指标定义
 
-When defining `## Metrics` in PROCESS.md, follow these guidelines so the system can properly track and visualize them:
+在 PROCESS.md 中定义 `## Metrics` 时，遵循以下指南以便系统正确追踪和可视化：
 
-### Format
+### 格式
 
-Each metric should include:
-- **Name**: A clear, concise identifier (e.g., "错题 review 率")
-- **Meaning**: What this metric measures and why it matters
-- **Direction**: Whether the metric should increase, decrease, or approach a target
-  - `increasing` = higher is better (e.g., success rate)
-  - `decreasing` = lower is better (e.g., error count)
-  - `target` = should approach a specific value (e.g., 100% coverage)
-- **Target** (optional): The goal value
-- **Unit** (optional): Measurement unit (e.g., "%", "条", "次")
-- **Chart** (optional): Suggested chart type for visualization
+每个指标应包含：
+- **名称**：清晰简洁的标识符（如"错题 review 率"）
+- **含义**：该指标衡量什么以及为什么重要
+- **方向**：指标应增大、减小还是趋近目标值
+  - `increasing` = 越高越好（如成功率）
+  - `decreasing` = 越低越好（如错误数）
+  - `target` = 应趋近特定值（如 100% 覆盖率）
+- **目标值**（可选）：目标数值
+- **单位**（可选）：度量单位（如"%"、"条"、"次"）
+- **图表**（可选）：建议的可视化图表类型
 
-### Example
+### 示例
 
 ```markdown
 ## Metrics
@@ -200,77 +194,77 @@ Each metric should include:
 - **错题重复出现率**: 统计相同错误模式的错题数量趋势。方向：越低越好。单位：条。图表：line。
 ```
 
-### Initializing Metrics Visualization
+### 初始化指标可视化
 
-After registering a full process with `--process`, you MUST initialize the metrics view configuration so the Process Management page can render charts for each metric. This is a two-step process:
+使用 `--process` 注册完整流程后，必须初始化指标视图配置，以便流程管理页面能为每个指标渲染图表。这是一个两步过程：
 
-#### Step 1: Design the view config based on ## Metrics
+#### 步骤 1：根据 ## Metrics 设计视图配置
 
-Analyze each metric in the `## Metrics` section and generate a `ProcessMetricsViewConfig` JSON. The config has two parts:
+分析 `## Metrics` 章节中的每个指标，生成 `ProcessMetricsViewConfig` JSON。配置包含两部分：
 
-- **`metrics[]`**: Metric card definitions (shown as number + trend + target)
-- **`charts[]`**: G2 v5 chart specs (one independent chart per metric, filtered by `metricName`)
+- **`metrics[]`**：指标卡片定义（显示数值 + 趋势 + 目标）
+- **`charts[]`**：G2 v5 图表规格（每个指标一个独立图表，通过 `metricName` 过滤）
 
-**ProcessMetricsViewConfig Schema:**
+**ProcessMetricsViewConfig Schema：**
 
 ```typescript
 {
   version: 1,
-  metrics: ProcessMetricView[],        // Metric card definitions
-  charts: ProcessMetricChartSpec[]     // Chart specs with metric binding
+  metrics: ProcessMetricView[],        // 指标卡片定义
+  charts: ProcessMetricChartSpec[]     // 带指标绑定的图表规格
 }
 
 // ProcessMetricView:
 {
-  metricName: string;                   // Must match the exact name used in metrics-report
-  title: LocaleString;                  // Display title for the card (i18n)
-  description?: LocaleString;           // Optional tooltip description (i18n)
+  metricName: string;                   // 必须与 metrics-report 中使用的名称完全一致
+  title: LocaleString;                  // 卡片显示标题（i18n）
+  description?: LocaleString;           // 可选的工具提示描述（i18n）
   chartType: string;                    // 'line' | 'bar' | 'area' | 'gauge' | 'number'
   direction?: 'increasing' | 'decreasing' | 'target';
-  target?: number;                      // Goal value (shown on card)
-  unit?: string;                        // Unit label (e.g., "%", "条", "次")
+  target?: number;                      // 目标值（显示在卡片上）
+  unit?: string;                        // 单位标签（如 "%"、"条"、"次"）
 }
 
 // ProcessMetricChartSpec:
 {
-  metricName?: string;                  // Filter snapshots for this metric
-  title?: LocaleString;                 // Chart title (i18n)
-  type: string;                         // G2 chart type: 'line' | 'interval' | 'area' | 'cell'
-  encode?: Record<string, unknown>;     // G2 encode config
-  scale?: Record<string, unknown>;      // G2 scale config
-  coordinate?: Record<string, unknown>; // G2 coordinate config
-  transform?: Record<string, unknown>[];// G2 transform config
-  style?: Record<string, unknown>;      // G2 style config
+  metricName?: string;                  // 按此指标名称过滤快照数据
+  title?: LocaleString;                 // 图表标题（i18n）
+  type: string;                         // G2 图表类型: 'line' | 'interval' | 'area' | 'cell'
+  encode?: Record<string, unknown>;     // G2 encode 配置
+  scale?: Record<string, unknown>;      // G2 scale 配置
+  coordinate?: Record<string, unknown>; // G2 coordinate 配置
+  transform?: Record<string, unknown>[];// G2 transform 配置
+  style?: Record<string, unknown>;      // G2 style 配置
   legend?: Record<string, unknown> | boolean;
   labels?: Record<string, unknown>[];
-  interval?: 'minute' | 'hour' | 'day' | 'week' | 'month'; // Date truncation for timestamp field
-  aggregate?: 'count' | 'sum' | 'avg'; // Aggregate function when interval is set (default: 'avg')
+  interval?: 'minute' | 'hour' | 'day' | 'week' | 'month'; // 时间戳字段的日期截断
+  aggregate?: 'count' | 'sum' | 'avg'; // 设置 interval 时的聚合函数（默认: 'avg'）
 }
 
-// LocaleString is either a plain string or { "zh-CN": "...", "en-US": "..." }
+// LocaleString 可以是纯字符串或 { "zh-CN": "...", "en-US": "..." }
 type LocaleString = string | { "zh-CN": string; "en-US": string };
 ```
 
-**Chart type selection guide:**
+**图表类型选择指南：**
 
-| Metric direction + unit | chartType | Has chart? | Reasoning |
-|------------------------|-----------|-----------|-----------|
-| `target` + `%` unit | `gauge` | No (card only) | Percentage target → card shows current vs target |
-| `target` + non-`%` unit | `number` | No (card only) | Numeric target → card is sufficient |
-| `increasing` / `decreasing` + `%` | `line` | Yes | Track trend over time |
-| `increasing` / `decreasing` + count unit | `bar` | Yes | Compare across runs |
+| 指标方向 + 单位 | chartType | 是否有图表？ | 原因 |
+|----------------|-----------|------------|------|
+| `target` + `%` 单位 | `gauge` | 无（仅卡片） | 百分比目标 → 卡片显示当前值与目标值 |
+| `target` + 非 `%` 单位 | `number` | 无（仅卡片） | 数值目标 → 卡片已足够 |
+| `increasing` / `decreasing` + `%` | `line` | 有 | 追踪时间趋势 |
+| `increasing` / `decreasing` + 计数单位 | `bar` | 有 | 跨运行对比 |
 
-**Chart spec design rules:**
+**图表规格设计规则：**
 
-1. **Each metric gets its own independent chart** — never mix different metrics in one chart. Different metrics have different units and scales, combining them makes the chart unreadable.
-2. **Every chart MUST include `metricName`** — the frontend uses this field to filter `metricSnapshots` for that specific metric. Without it, all data would be mixed.
-3. **Chart data fields** reference `ProcessMetricSnapshot` properties: `timestamp`, `value`, `metricName`, `dimensions`, `target`, `unit`. The frontend injects filtered snapshots as `data`.
-4. **Title each chart** — add a `title` field (use LocaleString format for i18n support).
+1. **每个指标独立一个图表** — 绝不在一个图表中混合不同指标。不同指标有不同单位和量级，合并会导致图表不可读。
+2. **每个图表必须包含 `metricName`** — 前端使用此字段为该特定指标过滤 `metricSnapshots`。缺少此字段会导致所有数据混合。
+3. **图表数据字段**引用 `ProcessMetricSnapshot` 属性：`timestamp`、`value`、`metricName`、`dimensions`、`target`、`unit`。前端将过滤后的快照作为 `data` 注入。
+4. **为每个图表添加标题** — 添加 `title` 字段（使用 LocaleString 格式支持 i18n）。
 
-**Chart spec templates by type:**
+**按图表类型的规格模板：**
 
 ```jsonc
-// line chart — time series trend (with date aggregation)
+// 折线图 — 时间序列趋势（带日期聚合）
 {
   "metricName": "错题重复出现率",
   "title": { "zh-CN": "错题重复出现率趋势", "en-US": "Repeat Error Rate Trend" },
@@ -281,7 +275,7 @@ type LocaleString = string | { "zh-CN": string; "en-US": string };
   "scale": { "y": { "nice": true } }
 }
 
-// bar chart — per-run comparison
+// 柱状图 — 每次运行对比
 {
   "metricName": "新增错题数",
   "title": { "zh-CN": "每次执行新增错题数", "en-US": "New Errors Per Run" },
@@ -290,7 +284,7 @@ type LocaleString = string | { "zh-CN": string; "en-US": string };
   "scale": { "y": { "nice": true } }
 }
 
-// area chart — cumulative trend (with date aggregation)
+// 面积图 — 累计趋势（带日期聚合）
 {
   "metricName": "review 完成数",
   "title": { "zh-CN": "Review 完成趋势", "en-US": "Review Completion Trend" },
@@ -302,15 +296,15 @@ type LocaleString = string | { "zh-CN": string; "en-US": string };
 }
 ```
 
-5. **gauge and number types do NOT need a chart entry** — they only appear as metric cards (showing latest value, trend arrow, and target).
-6. **When `interval` is set**, the frontend automatically aggregates snapshots by truncated date (minute/hour/day/week/month). Use `encode: { "x": "name", "y": "value" }` for interval-mode charts. When `interval` is omitted, raw snapshots are passed through to G2 directly (use `encode: { "x": "timestamp", "y": "value" }` for time series without aggregation).
+5. **gauge 和 number 类型不需要图表条目** — 它们仅作为指标卡片显示（展示最新值、趋势箭头和目标值）。
+6. **设置 `interval` 时**，前端自动按截断日期（分钟/小时/天/周/月）聚合快照。interval 模式图表使用 `encode: { "x": "name", "y": "value" }`。省略 `interval` 时，原始快照直接传递给 G2（无聚合的时间序列使用 `encode: { "x": "timestamp", "y": "value" }`）。
 
-#### Step 2: Write the view config
+#### 步骤 2：写入视图配置
 
-Use `loom process metrics-set-view-config` to write the configuration:
+使用 `loom process metrics-set-view-config` 写入配置：
 
 ```bash
-# From JSON string
+# 从 JSON 字符串写入
 loom process metrics-set-view-config <name> --config '{
   "version": 1,
   "metrics": [
@@ -345,15 +339,15 @@ loom process metrics-set-view-config <name> --config '{
   ]
 }'
 
-# Or from a file
+# 或从文件读取
 loom process metrics-set-view-config <name> --config @./view-config.json
 ```
 
-Note: The server must be running when using this command (it calls the API).
+注意：使用此命令时服务器必须正在运行（它会调用 API）。
 
-### Complete example — error-pattern-analysis process
+### 完整示例 — error-pattern-analysis 流程
 
-PROCESS.md `## Metrics` section:
+PROCESS.md `## Metrics` 章节：
 
 ```markdown
 ## Metrics
@@ -362,7 +356,7 @@ PROCESS.md `## Metrics` section:
 - **错题重复出现率**: 统计相同错误模式的错题数量趋势。方向：越低越好。单位：条。图表：line。
 ```
 
-Corresponding view config:
+对应的视图配置：
 
 ```json
 {
@@ -400,11 +394,11 @@ Corresponding view config:
 }
 ```
 
-Note: "错题 review 率" has `chartType: "gauge"` which only renders as a metric card (latest value + target + trend). It does NOT need a chart entry in `charts[]`.
+注意："错题 review 率"的 `chartType: "gauge"` 仅渲染为指标卡片（最新值 + 目标值 + 趋势）。它在 `charts[]` 中不需要图表条目。
 
-### Reporting metrics during execution
+### 执行期间上报指标
 
-When a process's PROCESS.md has a `## Metrics` section, the system automatically injects a Metrics Protocol into the AI prompt. The agent MUST call `loom process metrics-report` for each metric after computing its value:
+当流程的 PROCESS.md 包含 `## Metrics` 章节时，系统会自动在 AI 提示词中注入指标协议（Metrics Protocol）。代理在计算每个指标的值后，必须调用 `loom process metrics-report`：
 
 ```bash
 loom process metrics-report <process-name> \
@@ -415,30 +409,12 @@ loom process metrics-report <process-name> \
   --run-id $LOOM_RUN_ID
 ```
 
-Key points:
-- `--metric-name` MUST exactly match the name used in the view config (including `metrics[]` entries)
-- `--run-id` is automatically available via the `$LOOM_RUN_ID` environment variable
-- `--dimensions` is optional for dimensional breakdown (e.g., `--dimensions '{"subject":"数学"}'`)
-- Report each metric as soon as it's computed, don't batch at the end
-
-## Common Cron Patterns
-
-| Pattern | Schedule |
-|---------|----------|
-| `*/5 * * * *` | Every 5 minutes |
-| `*/15 * * * *` | Every 15 minutes |
-| `0 * * * *` | Every hour |
-| `0 9 * * *` | Daily at 9 AM |
-| `0 9 * * 1-5` | Weekdays at 9 AM |
-| `0 9 * * 1` | Every Monday at 9 AM |
-| `0 0 1 * *` | First of every month |
-
-## Common Event Patterns
-
-| Pattern | When |
-|---------|------|
-| `data:create:<model>` | New record created |
-| `data:update:<model>` | Record updated |
-| `data:delete:<model>` | Record deleted |
-| `user:created` | New user registered |
-| `process:completed:<name>` | Another process finished |
+关键要点：
+- `--metric-name` 必须与视图配置中使用的名称完全一致（包括 `metrics[]` 条目中的名称）
+- `--run-id` 通过 `$LOOM_RUN_ID` 环境变量自动获取
+- `--dimensions` 可选，用于维度拆分（如 `--dimensions '{"subject":"数学"}'`）
+- 每个指标计算完成后立即上报，不要在最后批量上报
+
+## 快速参考
+
+常用 Cron 和 Event 模式表见 **`process.md` → Trigger Types**。