@thinkingai/ae-cli 1.0.1 → 1.0.3

package/skills/te-dataops/references/dataops-flow-create.md

@@ -1,163 +1,163 @@
 ---
 name: dataops-flow-create
 version: 1.0.0
-description: "任务流创建与配置：创建任务流、添加任务节点、配置依赖关系、保存任务定义、配置调度、测试、发布到生产。触发关键词：创建任务流、新建工作流、配置调度、添加任务节点、发布、cron、定时执行。"
+description: "Flow creation and configuration: create flows, add task nodes, configure dependencies, save task definitions, configure scheduling, test, and release to production. Trigger keywords: create flow, new workflow, configure schedule, add task node, release, cron, scheduled execution."
 metadata:
   requires:
-    bins: ["te-cli"]
+    bins: ["ae-cli"]
 ---
 
-# DataOps 任务流创建与配置
+# DataOps Flow Creation and Configuration
 
-> **前置条件:** 阅读 [`te-dataops/SKILL.md`](../SKILL.md) 了解通用规则。
+> **Prerequisites:** Read [`te-dataops/SKILL.md`](../SKILL.md) for general rules.
 
-使用 `dataops_flow` 子命令管理任务流生命周期。
+Use the `dataops_flow` subcommand to manage flow lifecycle.
 
-**任务流生命周期：创建 → 配置节点 → 配置调度 → DEV 环境测试 → 发布到 PROD → 上线调度**
+**Flow Lifecycle: Create → Configure Nodes → Configure Schedule → Test in DEV → Release to PROD → Online Schedule**
 
 ---
 
-## 完整任务流创建流程
+## Complete Flow Creation Process
 
-按顺序执行以下步骤，从零创建一个可上线的任务流。
+Follow these steps in order to create a production-ready flow from scratch.
 
-### Step 1: 创建任务流
+### Step 1: Create Flow
 
 ```bash
-te-cli dataops_flow +create_flow --spaceCode "${spaceCode}" \
-  --flowName "每日ETL流程" --remark "处理用户数据" --confirmed true
-# 返回 flowCode，后续步骤都需要
+ae-cli dataops_flow +create_flow --spaceCode "${spaceCode}" \
+  --flowName "Daily ETL Process" --remark "Process user data" --confirmed true
+# Returns flowCode, required for subsequent steps
 ```
 
-### Step 2: 创建任务节点（可多次调用）
+### Step 2: Create Task Nodes (can be called multiple times)
 
 ```bash
-# 创建 SQL 任务
-te-cli dataops_flow +create_task --spaceCode "${spaceCode}" \
-  --flowCode "${flowCode}" --taskName "处理用户数据" --taskType "TRINO_SQL" --confirmed true
-# 返回 taskCode
-
-# 创建带前置依赖的任务
-te-cli dataops_flow +create_task --spaceCode "${spaceCode}" \
-  --flowCode "${flowCode}" --taskName "导出结果" --taskType "TRINO_SQL" \
+# Create SQL task
+ae-cli dataops_flow +create_task --spaceCode "${spaceCode}" \
+  --flowCode "${flowCode}" --taskName "Process User Data" --taskType "TRINO_SQL" --confirmed true
+# Returns taskCode
+
+# Create task with upstream dependency
+ae-cli dataops_flow +create_task --spaceCode "${spaceCode}" \
+  --flowCode "${flowCode}" --taskName "Export Results" --taskType "TRINO_SQL" \
   --preTaskCode "${upstreamTaskCode}" --confirmed true
 ```
 
-**任务节点类型：**
+**Task Node Types:**
 
-| 类型 | 说明 | 典型用途 |
-|------|------|---------|
-| TRINO_SQL | Trino SQL 查询 | 数据加工、ETL |
-| SHELL | Shell 脚本 | 系统命令、文件操作 |
-| FLOW_CHECK | 流程检查 | 检查上游任务流是否完成 |
-| TASK_CHECK | 任务检查 | 检查指定任务是否完成 |
-| OFFLINE_SYNC | 离线同步 | 集成方案数据同步（需 syncId） |
-| APP_SYNC | 应用同步 | 应用表数据同步（需 syncId） |
-| PLACE_HOLDER | 占位符 | 流程控制、逻辑分组 |
+| Type | Description | Typical Use |
+|------|-------------|-------------|
+| TRINO_SQL | Trino SQL query | Data processing, ETL |
+| SHELL | Shell script | System commands, file operations |
+| FLOW_CHECK | Flow check | Check if upstream flow is complete |
+| TASK_CHECK | Task check | Check if specified task is complete |
+| OFFLINE_SYNC | Offline sync | Integration solution data sync (requires syncId) |
+| APP_SYNC | App sync | App table data sync (requires syncId) |
+| PLACE_HOLDER | Placeholder | Flow control, logical grouping |
 
-### Step 3: 保存任务定义（配置 SQL/Shell 内容）
+### Step 3: Save Task Definition (configure SQL/Shell content)
 
 ```bash
-# SQL 任务
-te-cli dataops_flow +save_task_definition --spaceCode "${spaceCode}" \
+# SQL task
+ae-cli dataops_flow +save_task_definition --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --taskCode "${taskCode}" \
   --taskContentJson '{"sql":"SELECT * FROM dwd_user","repoCode":"te_etl","catalog":"hive","schema":"ws_default_dev"}' \
   --failRetryTimes 3 --failRetryInterval 30 --timeout 60 --confirmed true
 
-# Shell 任务
-te-cli dataops_flow +save_task_definition --spaceCode "${spaceCode}" \
+# Shell task
+ae-cli dataops_flow +save_task_definition --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --taskCode "${taskCode}" \
   --taskContentJson '{"script":"#!/bin/bash\necho hello"}' \
   --confirmed true
 ```
 
-### Step 4: 校验 SQL（推荐，仅 TRINO_SQL 类型）
+### Step 4: Validate SQL (recommended, TRINO_SQL type only)
 
 ```bash
-te-cli dataops_flow +validate_task_sql --spaceCode "${spaceCode}" \
+ae-cli dataops_flow +validate_task_sql --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --taskCode "${taskCode}" \
   --sql "SELECT * FROM dwd_user" --repoCode "te_etl" \
   --catalog "hive" --schema "ws_default_dev"
-# 检查 valid=true，否则查看 message 和 errorPosition
+# Check valid=true, otherwise review message and errorPosition
 ```
 
-### Step 5: 添加任务依赖关系（DAG 连线）
+### Step 5: Add Task Dependencies (DAG connections)
 
 ```bash
-te-cli dataops_flow +add_task_relation --spaceCode "${spaceCode}" \
+ae-cli dataops_flow +add_task_relation --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --preTaskCode "${upstreamTaskCode}" --taskCode "${downstreamTaskCode}" \
   --confirmed true
 ```
 
-### Step 6: 配置调度
+### Step 6: Configure Schedule
 
 ```bash
-# CRON 表达式定时执行
-te-cli dataops_flow +save_schedule_config --spaceCode "${spaceCode}" \
+# CRON expression for scheduled execution
+ae-cli dataops_flow +save_schedule_config --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --scheduled 1 --scheduleType "CRON" \
   --cron "0 0 2 * * ?" --confirmed true
-# 示例：0 0 2 * * ? = 每天凌晨2点
+# Example: 0 0 2 * * ? = Daily at 2 AM
 ```
 
-**CRON 格式**（6 字段）：`秒 分 时 日 月 周`
-- `0 0 */4 * * ?` — 每 4 小时
-- `0 30 8 * * 1-5` — 工作日 8:30
+**CRON Format** (6 fields): `second minute hour day month weekday`
+- `0 0 */4 * * ?` — Every 4 hours
+- `0 30 8 * * 1-5` — Weekdays at 8:30
 
-### Step 7: DEV 环境测试
+### Step 7: Test in DEV Environment
 
 ```bash
-# 手动触发执行
-te-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
+# Manually trigger execution
+ae-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --env "DEV" --confirmed true
 
-# 查看执行状态
-te-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
+# Check execution status
+ae-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
 
-# 查看任务日志（从 DAG 获取 bsTaskInstanceId 和 taskCode）
-te-cli dataops_flow +get_task_instance_log --bsTaskInstanceId "${instanceId}" --taskCode "${taskCode}"
+# View task logs (get bsTaskInstanceId and taskCode from DAG)
+ae-cli dataops_flow +get_task_instance_log --bsTaskInstanceId "${instanceId}" --taskCode "${taskCode}"
 
-# 根据日志调整配置后，重复测试
+# Adjust configuration based on logs, then repeat testing
 ```
 
-### Step 8: 发布到生产
+### Step 8: Release to Production
 
 ```bash
-te-cli dataops_flow +release_flow --spaceCode "${spaceCode}" \
+ae-cli dataops_flow +release_flow --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --confirmed true
-# 发布后 PROD 调度立即生效，不会中断运行中的实例
+# After release, PROD schedule takes effect immediately without interrupting running instances
 ```
 
 ---
 
-## 命令速查
-
-| 命令 | 用途 | 关键 Flags |
-|------|------|-----------|
-| `+create_flow` | 创建任务流 | `--spaceCode` `--flowName` `--remark` `--confirmed` |
-| `+create_task` | 创建任务节点 | `--spaceCode` `--flowCode` `--taskName` `--taskType` `--syncId` `--preTaskCode` `--confirmed` |
-| `+save_task_definition` | 保存任务定义 | `--spaceCode` `--flowCode` `--taskCode` `--taskContentJson` `--failRetryTimes` `--failRetryInterval` `--timeout` `--confirmed` |
-| `+validate_task_sql` | 校验 SQL | `--spaceCode` `--flowCode` `--taskCode` `--sql` `--repoCode` `--catalog` `--schema` |
-| `+add_task_relation` | 添加依赖 | `--spaceCode` `--flowCode` `--preTaskCode` `--taskCode` `--confirmed` |
-| `+save_schedule_config` | 配置调度 | `--spaceCode` `--flowCode` `--scheduled` `--scheduleType` `--cron` `--confirmed` |
-| `+get_flow_dag` | 查看 DAG 结构 | `--spaceCode` `--flowCode` `--env` |
-| `+get_task_params` | 查看任务参数 | `--spaceCode` `--flowCode` `--taskCode` `--env` |
-| `+execute_flow` | 手动执行 | `--spaceCode` `--flowCode` `--env` `--confirmed` |
-| `+get_execute_dag` | 查看运行态 DAG | `--spaceCode` `--executeId` |
-| `+get_task_instance_log` | 查看任务日志 | `--bsTaskInstanceId` `--taskCode` `--startOffset` `--limit` |
-| `+release_flow` | 发布到生产 | `--spaceCode` `--flowCode` `--confirmed` |
-
-## 参数说明
-
-- **参数引用**: 任务中通过 `${paramKey}` 引用空间参数（如 `${ws_run_date}`）
-- **环境**: `DEV`（默认）| `PROD`
-- **taskContentJson**: JSON 字符串，格式因 taskType 而异：
+## Command Quick Reference
+
+| Command | Purpose | Key Flags |
+|---------|---------|-----------|
+| `+create_flow` | Create flow | `--spaceCode` `--flowName` `--remark` `--confirmed` |
+| `+create_task` | Create task node | `--spaceCode` `--flowCode` `--taskName` `--taskType` `--syncId` `--preTaskCode` `--confirmed` |
+| `+save_task_definition` | Save task definition | `--spaceCode` `--flowCode` `--taskCode` `--taskContentJson` `--failRetryTimes` `--failRetryInterval` `--timeout` `--confirmed` |
+| `+validate_task_sql` | Validate SQL | `--spaceCode` `--flowCode` `--taskCode` `--sql` `--repoCode` `--catalog` `--schema` |
+| `+add_task_relation` | Add dependency | `--spaceCode` `--flowCode` `--preTaskCode` `--taskCode` `--confirmed` |
+| `+save_schedule_config` | Configure schedule | `--spaceCode` `--flowCode` `--scheduled` `--scheduleType` `--cron` `--confirmed` |
+| `+get_flow_dag` | View DAG structure | `--spaceCode` `--flowCode` `--env` |
+| `+get_task_params` | View task parameters | `--spaceCode` `--flowCode` `--taskCode` `--env` |
+| `+execute_flow` | Manual execution | `--spaceCode` `--flowCode` `--env` `--confirmed` |
+| `+get_execute_dag` | View runtime DAG | `--spaceCode` `--executeId` |
+| `+get_task_instance_log` | View task logs | `--bsTaskInstanceId` `--taskCode` `--startOffset` `--limit` |
+| `+release_flow` | Release to production | `--spaceCode` `--flowCode` `--confirmed` |
+
+## Parameter Notes
+
+- **Parameter Reference**: Reference workspace parameters in tasks using `${paramKey}` (e.g., `${ws_run_date}`)
+- **Environment**: `DEV` (default) | `PROD`
+- **taskContentJson**: JSON string, format varies by taskType:
   - TRINO_SQL: `{"sql":"SELECT ...","repoCode":"xxx","catalog":"hive","schema":"db"}`
   - SHELL: `{"script":"#!/bin/bash\n..."}`
 
-## 注意事项
+## Important Notes
 
-1. **flowCode 获取**: 通过 `+list_flows` 获取（见 `dataops-flow-monitor` Skill）
-2. **taskCode 获取**: 通过 `+create_task` 返回或 `+get_flow_dag` 查询
-3. **发布影响**: 将 DEV 所有变更同步到 PROD，PROD 调度立即生效
-4. **SQL 校验**: 保存 TRINO_SQL 任务前建议先校验
-5. **不能创建循环依赖**
+1. **Getting flowCode**: Use `+list_flows` (see `dataops-flow-monitor` Skill)
+2. **Getting taskCode**: Returned by `+create_task` or query via `+get_flow_dag`
+3. **Release Impact**: Syncs all DEV changes to PROD, PROD schedule takes effect immediately
+4. **SQL Validation**: Recommended to validate before saving TRINO_SQL tasks
+5. **Cannot create circular dependencies**

package/skills/te-dataops/references/dataops-flow-monitor.md

@@ -1,118 +1,118 @@
 ---
 name: dataops-flow-monitor
 version: 1.0.0
-description: "任务流执行与监控：查看执行实例、运行态 DAG、任务日志、手动执行/停止任务流。触发关键词：执行任务流、运行实例、监控、日志、停止、DAG、排错、实例、flow instance。"
+description: "Flow execution and monitoring: view execution instances, runtime DAG, task logs, manually execute/stop flows. Trigger keywords: execute flow, running instance, monitor, logs, stop, DAG, troubleshoot, instance, flow instance."
 metadata:
   requires:
-    bins: ["te-cli"]
+    bins: ["ae-cli"]
 ---
 
-# DataOps 任务流执行与监控
+# DataOps Flow Execution and Monitoring
 
-> **前置条件:** 阅读 [`te-dataops/SKILL.md`](../SKILL.md) 了解通用规则。
+> **Prerequisites:** Read [`te-dataops/SKILL.md`](../SKILL.md) for general rules.
 
-使用 `dataops_flow` 子命令执行和监控任务流。
+Use the `dataops_flow` subcommand to execute and monitor flows.
 
-**核心概念：**
-- **executeId** — flow_* 工具使用的执行记录 ID（通过 `+list_flow_instances` 获取）
-- **flowInstanceId** — operations_* 工具使用的运维实例 ID（两者不互通，不可混用）
-- **实例列表默认查询 PROD 环境**（与其他工具默认 DEV 不同）
+**Core Concepts:**
+- **executeId** — Execution record ID used by flow_* tools (obtained via `+list_flow_instances`)
+- **flowInstanceId** — Operations instance ID used by operations_* tools (these two are not interchangeable)
+- **Instance list queries PROD environment by default** (unlike other tools which default to DEV)
 
 ---
 
-## 工作流 A：查找并查看任务流执行状态
+## Workflow A: Find and View Flow Execution Status
 
 ```bash
-# Step 1: 搜索任务流（获取 flowCode）
-te-cli dataops_flow +list_flows --spaceCode "${spaceCode}" --keyword "etl"
+# Step 1: Search flows (get flowCode)
+ae-cli dataops_flow +list_flows --spaceCode "${spaceCode}" --keyword "etl"
 
-# Step 2: 查看执行实例列表（默认 PROD，按时间倒序）
-te-cli dataops_flow +list_flow_instances --spaceCode "${spaceCode}" \
+# Step 2: View execution instance list (default PROD, sorted by time descending)
+ae-cli dataops_flow +list_flow_instances --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --env "PROD" --size 30
 
-# Step 3: 查看运行态 DAG（含各节点执行状态）
-te-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
+# Step 3: View runtime DAG (with execution status for each node)
+ae-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
 
-# Step 4: 查看执行记录详情
-te-cli dataops_flow +get_execute_record --spaceCode "${spaceCode}" --executeId "${executeId}"
+# Step 4: View execution record details
+ae-cli dataops_flow +get_execute_record --spaceCode "${spaceCode}" --executeId "${executeId}"
 ```
 
 ---
 
-## 工作流 B：排查任务失败
+## Workflow B: Troubleshoot Task Failures
 
 ```bash
-# Step 1: 获取运行态 DAG，定位失败节点
-te-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
-# 从返回中找到 status=FAILED 的节点，获取其 bsTaskInstanceId 和 taskCode
+# Step 1: Get runtime DAG, locate failed node
+ae-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
+# Find node with status=FAILED, get its bsTaskInstanceId and taskCode
 
-# Step 2: 查看失败任务的日志
-te-cli dataops_flow +get_task_instance_log --bsTaskInstanceId "${bsTaskInstanceId}" \
+# Step 2: View failed task logs
+ae-cli dataops_flow +get_task_instance_log --bsTaskInstanceId "${bsTaskInstanceId}" \
   --taskCode "${taskCode}" --limit 100
 
-# Step 3: 查看任务定义（确认 SQL/配置）
-te-cli dataops_flow +get_task_params --spaceCode "${spaceCode}" \
+# Step 3: View task definition (confirm SQL/configuration)
+ae-cli dataops_flow +get_task_params --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --taskCode "${taskCode}"
 
-# Step 4: 修复后重新执行
-te-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
+# Step 4: Re-execute after fixing
+ae-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --env "DEV" --confirmed true
 ```
 
 ---
 
-## 工作流 C：手动执行与停止
+## Workflow C: Manual Execution and Stop
 
 ```bash
-# 手动触发执行（默认 DEV，可指定 PROD）
-te-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
+# Manually trigger execution (default DEV, can specify PROD)
+ae-cli dataops_flow +execute_flow --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --env "DEV" --confirmed true
-# 返回 executeId
+# Returns executeId
 
-# 监控执行过程
-te-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
+# Monitor execution progress
+ae-cli dataops_flow +get_execute_dag --spaceCode "${spaceCode}" --executeId "${executeId}"
 
-# 必要时停止执行（不可撤销）
-te-cli dataops_flow +stop_flow --spaceCode "${spaceCode}" \
+# Stop execution if necessary (irreversible)
+ae-cli dataops_flow +stop_flow --spaceCode "${spaceCode}" \
   --flowCode "${flowCode}" --executeId "${executeId}" --confirmed true
 ```
 
 ---
 
-## 工作流 D：查看任务流结构
+## Workflow D: View Flow Structure
 
 ```bash
-# 查看任务流定义态 DAG（静态结构、依赖关系）
-te-cli dataops_flow +get_flow_dag --spaceCode "${spaceCode}" --flowCode "${flowCode}"
+# View flow definition DAG (static structure, dependencies)
+ae-cli dataops_flow +get_flow_dag --spaceCode "${spaceCode}" --flowCode "${flowCode}"
 
-# 查看任务流基本信息
-te-cli dataops_flow +get_flow_detail --spaceCode "${spaceCode}" --flowCode "${flowCode}"
+# View flow basic information
+ae-cli dataops_flow +get_flow_detail --spaceCode "${spaceCode}" --flowCode "${flowCode}"
 
-# 查看调度配置
-te-cli dataops_flow +get_schedule_config --spaceCode "${spaceCode}" --flowCode "${flowCode}"
+# View schedule configuration
+ae-cli dataops_flow +get_schedule_config --spaceCode "${spaceCode}" --flowCode "${flowCode}"
 ```
 
 ---
 
-## 命令速查
-
-| 命令 | 用途 | 关键 Flags |
-|------|------|-----------|
-| `+list_flows` | 搜索任务流 | `--spaceCode` `--keyword` |
-| `+get_flow_detail` | 任务流信息 | `--spaceCode` `--flowCode` `--env` |
-| `+get_flow_dag` | 定义态 DAG | `--spaceCode` `--flowCode` `--env` |
-| `+get_schedule_config` | 调度配置 | `--spaceCode` `--flowCode` `--env` |
-| `+execute_flow` | 手动执行 | `--spaceCode` `--flowCode` `--env` `--confirmed` |
-| `+stop_flow` | 停止执行 | `--spaceCode` `--flowCode` `--executeId` `--confirmed` |
-| `+list_flow_instances` | 实例列表 | `--spaceCode` `--flowCode` `--env` `--size` |
-| `+get_execute_record` | 执行记录 | `--spaceCode` `--executeId` |
-| `+get_execute_dag` | 运行态 DAG | `--spaceCode` `--executeId` |
-| `+get_task_instance_log` | 任务日志 | `--bsTaskInstanceId` `--taskCode` `--startOffset` `--limit` |
-| `+get_task_params` | 任务参数 | `--spaceCode` `--flowCode` `--taskCode` `--env` |
-| `+update_flow` | 更新任务流 | `--spaceCode` `--flowCode` `--flowName` `--remark` `--confirmed` |
-
-## 参数说明
-
-- **env**: `DEV`（开发）| `PROD`（生产，实例列表默认 PROD）
-- **任务状态**: `success` / `failure` / `running` / `waiting`
-- **DAG 区别**: `+get_flow_dag` 返回静态定义结构，`+get_execute_dag` 返回含执行状态的运行态结构
+## Command Quick Reference
+
+| Command | Purpose | Key Flags |
+|---------|---------|-----------|
+| `+list_flows` | Search flows | `--spaceCode` `--keyword` |
+| `+get_flow_detail` | Flow information | `--spaceCode` `--flowCode` `--env` |
+| `+get_flow_dag` | Definition DAG | `--spaceCode` `--flowCode` `--env` |
+| `+get_schedule_config` | Schedule configuration | `--spaceCode` `--flowCode` `--env` |
+| `+execute_flow` | Manual execution | `--spaceCode` `--flowCode` `--env` `--confirmed` |
+| `+stop_flow` | Stop execution | `--spaceCode` `--flowCode` `--executeId` `--confirmed` |
+| `+list_flow_instances` | Instance list | `--spaceCode` `--flowCode` `--env` `--size` |
+| `+get_execute_record` | Execution record | `--spaceCode` `--executeId` |
+| `+get_execute_dag` | Runtime DAG | `--spaceCode` `--executeId` |
+| `+get_task_instance_log` | Task logs | `--bsTaskInstanceId` `--taskCode` `--startOffset` `--limit` |
+| `+get_task_params` | Task parameters | `--spaceCode` `--flowCode` `--taskCode` `--env` |
+| `+update_flow` | Update flow | `--spaceCode` `--flowCode` `--flowName` `--remark` `--confirmed` |
+
+## Parameter Notes
+
+- **env**: `DEV` (development) | `PROD` (production, instance list defaults to PROD)
+- **Task Status**: `success` / `failure` / `running` / `waiting`
+- **DAG Difference**: `+get_flow_dag` returns static definition structure, `+get_execute_dag` returns runtime structure with execution status