docs: clarify on_error logic in pipeline protocol (#1251)

## Summary by Sourcery

澄清并重构关于流水线节点生命周期和 `on_error` 行为的文档，并整理代理（agent）文档中的相关表格。

Enhancements:
- 通过用新的「Node Flow」章节替换旧的流程图来整合节点生命周期文档，从而减少重复内容。

Documentation:
- 使用更新后的 Mermaid 流程图和专门的「Node Flow」章节，记录详细的节点生命周期流程。
- 澄清 `on_error` 节点在何时执行，明确将该行为与下一个节点的识别超时关联起来，并链接到新的流程图。
- 调整 `AGENTS.md` 中的 Markdown 表格格式，以确保间距一致并提升可读性。

<details>
<summary>Original summary in English</summary>

## Summary by Sourcery

Clarify and restructure documentation of the pipeline node lifecycle and
on_error behavior, and tidy related tables in agent docs.

Enhancements:
- Consolidate the node lifecycle documentation by replacing the older
flowchart with the new Node Flow section to reduce duplication.

Documentation:
- Document the detailed node lifecycle flow with an updated Mermaid
flowchart and dedicated Node Flow section.
- Clarify when on_error nodes are executed, explicitly tying the
behavior to next node recognition timeout and linking to the new
flowchart.
- Adjust Markdown table formatting in AGENTS.md for consistent spacing
and readability.

</details>

---------

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: MistEO <mistereo@hotmail.com>

Author: 3 people

AGENTS.md

@@ -61,7 +61,7 @@ MaaFramework/
 ### 术语定义
 
 | 术语 | 说明 |
-|------|------|
+| ------ | ------ |
 | **Node（节点）** | Pipeline JSON 中的一个完整对象，包含识别、动作、后继节点等配置 |
 | **Task（任务）** | 若干 Node 按顺序相连的逻辑流程 |
 | **Entry（入口）** | Task 中的第一个 Node |
@@ -91,7 +91,7 @@ MaaFramework/
 ### 识别算法类型
 
 | 类型 | 说明 | 关键参数 |
-|------|------|----------|
+| ------ | ------ | ---------- |
 | `DirectHit` | 直接命中，不进行识别 | - |
 | `TemplateMatch` | 模板匹配（找图） | `template`, `threshold`, `roi` |
 | `FeatureMatch` | 特征匹配（抗透视） | `template`, `count`, `detector` |
@@ -104,7 +104,7 @@ MaaFramework/
 ### 动作类型
 
 | 类型 | 说明 | 关键参数 |
-|------|------|----------|
+| ------ | ------ | ---------- |
 | `DoNothing` | 不执行任何操作 | - |
 | `Click` | 点击 | `target`, `target_offset` |
 | `LongPress` | 长按 | `target`, `duration` |

docs/en_us/3.1-PipelineProtocol.md

@@ -47,6 +47,31 @@ The task process terminates when any of the following conditions are met:
 - The current node's `next` list misses until timeout
 - External `post_stop` is called or `StopTask` action is executed
 
+## Node Flow
+
+A node's lifecycle is as follows:
+
+```mermaid
+    flowchart TB
+        A[enter the node] --> B[pre_wait_freezes]
+        B --> C[pre_delay]
+        C --> D[action]
+        D --> M{"repeat > 1?"}
+        M -->|yes| N[repeat_wait_freezes]
+        N --> O[repeat_delay]
+        O --> D
+        M -->|no| E[post_wait_freezes]
+        E --> F[post_delay]
+        F --> P[screenshot]
+        P --> G[recognize next]
+        G --> H{successfully identified nodes}
+        H -->|yes| I[enter a new node]
+        H -->|no| J{"timer timeout"}
+        J -->|yes| K[on_error]
+        J -->|no| L[wait for rate_limit]
+        L --> P
+```
+
 ## Application Examples
 
 ### Scenario Description
@@ -193,7 +218,7 @@ Typical flow: recognize inside `roi` (with `roi_offset`), get `box`, then calcul
     Can be approximated as `while(!hit && !timeout) { foreach(next); sleep_until(rate_limit); }`.
 
 - `on_error` : *string* | *NodeAttr* | *list<string | NodeAttr, >*  
-    Failure successors. These nodes are executed next when the current node's `next` list times out, or when a hit sub-node's action fails. Optional, empty by default.  
+    When **this node's** next list has no matching nodes and the loop recognition times out, or when the action fails to execute, the nodes in this list will be executed next (see [flowchart](#node-flow)). Optional, empty by default.  
     💡 Since v5.1, nodes with attributes, NodeAttr objects, or heterogeneous arrays combining both are supported. See [Node Attributes](#node-attributes) for details.
 
 - `anchor`: *string* | *list<string, >* | *object* **💡 v5.1**  
@@ -261,30 +286,6 @@ Typical flow: recognize inside `roi` (with `roi_offset`), get `box`, then calcul
     This field can be used to store custom configuration information that does not affect the node's execution logic but can be retrieved through related interfaces.  
     **Note**: This field will be merged with the `attach` in the default value using dict merge, not overwritten. That is, the `attach` in the node will be merged with the `attach` in the default value, where values with the same keys will be overwritten by the node's values, but other keys will be preserved.
 
-The lifecycle of a node is as follows:
-
-```mermaid
-    graph TB
-        A[enter the node] --> B[pre_wait_freezes]
-        B --> C[pre_delay]
-        C --> D[action]
-        D --> M{repeat > 1?}
-        M -->|yes| N[repeat_wait_freezes]
-        N --> O[repeat_delay]
-        O --> D
-        M -->|no| E[post_wait_freezes]
-        E --> F[post_delay]
-        F --> Q[start timer]
-        Q --> P[screenshot]
-        P --> G[recognize next]
-        G --> H{successfully identified nodes}
-        H -->|yes| I[enter a new node]
-        H -->|no| J{timeout}
-        J -->|yes| K[on_error]
-        J -->|no| L[wait for rate_limit]
-        L --> P
-```
-
 ### Pipeline v2
 
 > [!NOTE]

docs/zh_cn/3.1-任务流水线协议.md

@@ -51,6 +51,31 @@
 - 当前节点的 `next` 列表未命中且超时
 - 外部调用 `post_stop` 或执行了 `StopTask` 动作
 
+## 节点流程
+
+一个节点的生命周期如下：
+
+```mermaid
+    flowchart TB
+        A[进入节点] --> B[pre_wait_freezes]
+        B --> C[pre_delay]
+        C --> D[action]
+        D --> M{"repeat > 1?"}
+        M -->|是| N[repeat_wait_freezes]
+        N --> O[repeat_delay]
+        O --> D
+        M -->|否| E[post_wait_freezes]
+        E --> F[post_delay]
+        F --> P[截图]
+        P --> G[识别next]
+        G --> H{"是否有识别成功的节点"}
+        H -->|是| I[进入新节点]
+        H -->|否| J{"检查计时"}
+        J -->|超时| K[on_error]
+        J -->|未超时| L[等待rate_limit]
+        L --> P
+```
+
 ## 应用示例
 
 ### 场景描述
@@ -155,7 +180,7 @@ Android 设置界面存在菜单 `显示`/`存储`/`无障碍`，其中 `存储`
 | ---- | -------- |
 | v5.0 | 新增 `attach` 字段; 新增 `TouchDown` `TouchMove` `TouchUp` `KeyDown` `KeyUp` 动作; Click / LongPress / Swipe / MultiSwipe 新增 `contact` `pressure` 字段; `target` 新增 `[x, y]` 二元坐标支持 |
 | v5.1 | 新增 `anchor` `max_hit` 字段; 新增 `Scroll` 动作; 新增节点属性（`jump_back` / `anchor`）; `next` / `on_error` 新增 NodeAttr 支持; `order_by` 新增 `Expected` 排序; `is_sub` / `interrupt` 废弃 |
-| v5.3 | 新增 `repeat` `repeat_delay` `repeat_wait_freezes` 字段; 新增 `And` `Or` 识别类型; 新增 `Shell` 动作; TemplateMatch `method` 新增 `10001`; 新增默认属性（`default_pipeline.json`）|
+| v5.3 | 新增 `repeat` `repeat_delay` `repeat_wait_freezes` 字段; 新增 `And` `Or` 识别类型; 新增 `Shell` 动作; TemplateMatch `method` 新增 `10001`; 新增默认属性（`default_pipeline.json`） |
 | v5.5 | `timeout` 新增 `-1`（无限等待）支持; Scroll 新增 `target` `target_offset` |
 | v5.6 | `roi` / `target` 支持负数坐标和尺寸 |
 | v5.7 | `anchor` 新增 object 形式（指定目标节点 / 清除锚点）; `And` / `Or` 新增节点名称引用支持 |
@@ -197,7 +222,7 @@ Android 设置界面存在菜单 `显示`/`存储`/`无障碍`，其中 `存储`
     可近似理解为 `while(!hit && !timeout) { foreach(next); sleep_until(rate_limit); }` 。
 
 - `on_error` : *string* | *NodeAttr* | *list<string | NodeAttr, >*  
-    失败后继列表。当当前节点的 `next` 列表识别超时，或某个子节点识别命中后动作失败时，会执行该列表中的节点。可选，默认空。  
+    当**本节点**内的 `next` 列表中没有任何节点命中并且循环识别超时，或动作执行失败后，接下来会执行该列表中的节点（参见[流程图](#节点流程)）。可选，默认空。  
     💡 v5.1 版本起新增支持带属性节点、 NodeAttr 形式对象，或两者结合的异质数组。详情请参考 [节点属性](#节点属性)。
 
 - `anchor`: *string* | *list<string, >* | *object* **💡 v5.1**  
@@ -267,30 +292,6 @@ Android 设置界面存在菜单 `显示`/`存储`/`无障碍`，其中 `存储`
     该字段可用于存储自定义的配置信息，这些信息不会影响节点的执行逻辑，但可以通过相关接口获取。  
     **注意**：该字段会与默认值中的 `attach` 进行字典合并（dict merge），而不是覆盖。即节点中的 `attach` 会与默认值中的 `attach` 合并，相同键的值会被节点中的值覆盖，但其他键会保留。
 
-一个节点的生命周期如下
-
-```mermaid
-    graph TB
-        A[进入节点] --> B[pre_wait_freezes]
-        B --> C[pre_delay]
-        C --> D[action]
-        D --> M{repeat > 1?}
-        M -->|是| N[repeat_wait_freezes]
-        N --> O[repeat_delay]
-        O --> D
-        M -->|否| E[post_wait_freezes]
-        E --> F[post_delay]
-        F --> Q[开始计时]
-        Q --> P[截图]
-        P --> G[识别next]
-        G --> H{是否有识别成功的节点}
-        H -->|是| I[进入新节点]
-        H -->|否| J{timeout}
-        J -->|超时| K[on_error]
-        J -->|未超时| L[等待rate_limit]
-        L --> P
-```
-
 ### Pipeline v2
 
 > [!NOTE]