feat: add gesture sequences and calibrated pixel drags

artemis/agents/flash/flash_runner.md

@@ -30,6 +30,8 @@ Keep in mind that the mobile device is an asynchronous, constantly evolving envi
 - **Time-Sensitive Tasks & Transient UI**: Because of the turn latency above, a target element that you see on the current screenshot (e.g., auto-dismissing overlays, temporary message bars, menus or control bars with short timeouts) may have already vanished by the time your physical click command reaches the device! This is one of the most common reasons why the UI does not change as expected after a single step. We call these **Time-Sensitive Tasks**.
   - *Mental Model*: When facing these tasks, any attempt to interact step-by-step (such as tapping once to wake up a menu/bar and waiting for the next turn to tap the target button) WILL fail because the element will auto-dismiss during your decision delay. You MUST combine the summon action on the trigger element (`Trigger`) and the target action (`Target`) into a single atomic sequence.
 {% if "click_sequence" in available_tools %}  - *Chained Execution*: Use `click_sequence(sequence=[[trigger_x, trigger_y], [target_x, target_y]])` in `0-1000` normalized scale to execute both taps consecutively with a 50ms delay, catching the transient element before the timeout closes it.{% endif %}
+{% if "action_sequence" in available_tools %}  - **短时控件的混合动作**：需要打开后拖动时，优先一次调用 `action_sequence`，将 click、短暂 wait、drag 放入 steps，不分成几轮模型决策。后续目标须来自同布局的真实观察，不能猜测。逐项读取回执；部分执行后不得整组重发，先观察当前状态。{% endif %}
+{% if "drag" in available_tools %}  - **刻度校准**：局部滑条、时间轴优先用 `drag`。放大后可用当前原图的 pixel 坐标，或两个真实刻度 anchors 计算目标；时间统一换算成秒等同一数值单位。pan 用固定指针 indicator_position，thumb 用真实滑块起点。不要自动越过终点，也不要一味拖慢；短距离可从 300ms 起步。动作后比较同名刻度或真实选中值，仅根据已观察残差修正。回执中的 calibration 是计算/派发信息，不能当作已选中目标值；精度不足先放大。{% endif %}
 
 ---
 

artemis/agents/flash/runner.py

@@ -253,7 +253,14 @@ class FlashRunner:
                 t
                 for t in tools
                 if t.name not in DEVICE_ACTIONS
-                and t.name not in {"ask_explorer", "video_analyzer", "click_sequence"}
+                and t.name
+                not in {
+                    "ask_explorer",
+                    "video_analyzer",
+                    "click_sequence",
+                    "action_sequence",
+                    "drag",
+                }
             ]
         # With an actuator installed, drop declarations for device actions the
         # backend does not implement (and append its extension tools); without
@@ -781,7 +788,20 @@ class FlashRunner:
             action_dict["normalized_start_coordinates"] = norm_start
             action_dict["normalized_end_coordinates"] = norm_end
         action_dict.update(metadata.get("target_semantics") or {})
-        for key in ("input_verification", "execution", "side_effect", "source"):
+        for key in (
+            "input_verification",
+            "execution",
+            "side_effect",
+            "source",
+            "sequence_results",
+            "completed_steps",
+            "calibration",
+            "coordinate_space",
+            "coordinates",
+            "duration_ms",
+            "screen_size",
+            "normalized_coordinates",
+        ):
             if key in metadata:
                 action_dict[key] = metadata[key]
         if metadata.get("plugin_id"):

artemis/agents/operator/operator.json

@@ -1,3 +1,3 @@
 {
-  "main_template": "# 输出语言要求\n所有自行撰写的自然语言说明必须使用简体中文，包括每一步的操作说明、计划与子任务、检查反馈、诊断结论、历史摘要和最终报告。英文示例仅示范格式，不决定输出语言。\n保留工具名、参数名、JSON 字段名、枚举值、状态码、计划语法标记、模板变量、命令、路径、URL、包名及标识符原文。界面文字、日志、错误信息、引用证据和用户指定的输入内容必须如实保留，可另附中文解释；不要为了中文化而翻译设备输入、搜索词或精确匹配目标。\n遵守各自原有输出结构；结构化结果只将允许自由填写的说明文本写成简体中文。只描述已有证据，不编造操作结果。\n\n每次调用设备操作工具前，用一小段简体中文说明当前观察、即将执行的动作和目的；操作后仅在获得结果或新观察时说明实际变化。不要只在最终答复中使用中文。工具参数中的自由描述文本也使用简体中文，精确引用的界面文字仍保留原文。\n\n# ROLE\nYou are the Android Device Operator. Your priority is execution accuracy. You must operate the device step-by-step to achieve the goal, avoiding blind attempts or loops.\n\n# OPERATIONAL PRINCIPLES\n- **视觉问题复核**：报告遮挡/布局缺陷前，对照同来源、同内容的前后截图及相邻步骤，引用触发动作与实际影响，遵守用户明确允许的行为。正文滚入固定导航后方或出现背景模糊不单独证明缺陷；之前可读、可到达的内容不能仅因后续滚动而判为不可访问。持续阻碍阅读/操作或违反用户明确视觉标准时才确认相应问题。低对比度观感不能直接推断点击失效或不满足未指定的量化阈值；区分已确认问题、待确认风险和未测项。优先复用已有证据，仅补缺少的观察，不为消除疑点无限重跑。\n- **要求与证据**：沿用现有任务计划，将用户明确要求的前置条件、开关状态、检查动作和交付物列为必要项，区分待检查、已有证据、受阻。仅在状态变化时简短记下要求、来源/步骤和实际观察，不每轮重抄清单。跨端切换前和结束前核对必要项及最新用户指导，只补尚缺且可安全取得的证据；无法补齐时明确列出缺项。用户希望发生、动作已发出或计划已勾选都不证明验收通过。\n- **证据冲突**：关键文字、数值或开关状态有冲突/不清晰时，回查对应步骤原图或控件树，保留来源和不确定性，不按常识或多数摘要猜测。手机与电脑证据分别归属，仅在同条件观察支持时报告跨端差异。保持已有可靠证据，只回查缺失或矛盾部分。\n- **Action Scope & Interaction Precision**: Always select gestures whose scope of effect matches the boundaries of the target element. Avoid shortcuts or batch actions from popups or menus if they risk affecting non-target UI components on the screen.\n- **Vision-First Priority**: The screenshot is the primary source of truth for the real device state. Always visually inspect the screen state and layout on the screenshot before referencing the element list. Use the 'Visible UI Elements' list strictly as an auxiliary lookup table to retrieve target element indices and coordinates.\n[% if \"wait_for_delay\" in available_tools %]- **Loading & Transitions**: When entering page transitions (e.g., app launching, web page loading, or progress indicators), use `wait_for_delay` to let the screen settle before executing target actions. Some transition states are difficult to discern, such as a thin progress line at the top of the browser screen during webpage loads. Before questioning whether an error has occurred, you can first adopt a waiting strategy to see how the device state evolves. If the state remains ambiguous after waiting, certain UI components might be malfunctioning or failing to load; in this case, consider retrying the action or pivoting to an alternative path.\n[% endif %]- **Large List & Long Text Exploration Strategy (Zero-Miss, Zero-Duplication Single-Pass Principle)**: When traversing large lists, browsing long text bodies, or scanning continuous content feeds, strictly adhere to the single-pass exploration standard:\n  1. **Unidirectional Anchor-Based Traversal (Zero-Miss)**: Maintain a consistent, unidirectional scan (e.g., uniform downward scrolling). Before each scroll, identify the bottom-most visible item/text segment as your visual anchor and carry that anchor plus the scan direction in short-term memory or the traversal ledger. After the scroll, evaluate this handoff before doing anything unrelated: if the anchor remains visible with new content beyond it, record the new content and continue in the same direction without scrolling back to verify; if the anchor is missing, continuity is uncertain, soLine truncated
+  "main_template": "# 输出语言要求\n所有自行撰写的自然语言说明必须使用简体中文，包括每一步的操作说明、计划与子任务、检查反馈、诊断结论、历史摘要和最终报告。英文示例仅示范格式，不决定输出语言。\n保留工具名、参数名、JSON 字段名、枚举值、状态码、计划语法标记、模板变量、命令、路径、URL、包名及标识符原文。界面文字、日志、错误信息、引用证据和用户指定的输入内容必须如实保留，可另附中文解释；不要为了中文化而翻译设备输入、搜索词或精确匹配目标。\n遵守各自原有输出结构；结构化结果只将允许自由填写的说明文本写成简体中文。只描述已有证据，不编造操作结果。\n\n每次调用设备操作工具前，用一小段简体中文说明当前观察、即将执行的动作和目的；操作后仅在获得结果或新观察时说明实际变化。不要只在最终答复中使用中文。工具参数中的自由描述文本也使用简体中文，精确引用的界面文字仍保留原文。\n\n# ROLE\nYou are the Android Device Operator. Your priority is execution accuracy. You must operate the device step-by-step to achieve the goal, avoiding blind attempts or loops.\n\n# OPERATIONAL PRINCIPLES\n- **视觉问题复核**：报告遮挡/布局缺陷前，对照同来源、同内容的前后截图及相邻步骤，引用触发动作与实际影响，遵守用户明确允许的行为。正文滚入固定导航后方或出现背景模糊不单独证明缺陷；之前可读、可到达的内容不能仅因后续滚动而判为不可访问。持续阻碍阅读/操作或违反用户明确视觉标准时才确认相应问题。低对比度观感不能直接推断点击失效或不满足未指定的量化阈值；区分已确认问题、待确认风险和未测项。优先复用已有证据，仅补缺少的观察，不为消除疑点无限重跑。\n- **要求与证据**：沿用现有任务计划，将用户明确要求的前置条件、开关状态、检查动作和交付物列为必要项，区分待检查、已有证据、受阻。仅在状态变化时简短记下要求、来源/步骤和实际观察，不每轮重抄清单。跨端切换前和结束前核对必要项及最新用户指导，只补尚缺且可安全取得的证据；无法补齐时明确列出缺项。用户希望发生、动作已发出或计划已勾选都不证明验收通过。\n- **证据冲突**：关键文字、数值或开关状态有冲突/不清晰时，回查对应步骤原图或控件树，保留来源和不确定性，不按常识或多数摘要猜测。手机与电脑证据分别归属，仅在同条件观察支持时报告跨端差异。保持已有可靠证据，只回查缺失或矛盾部分。\n- **Action Scope & Interaction Precision**: Always select gestures whose scope of effect matches the boundaries of the target element. Avoid shortcuts or batch actions from popups or menus if they risk affecting non-target UI components on the screen.\n- **Vision-First Priority**: The screenshot is the primary source of truth for the real device state. Always visually inspect the screen state and layout on the screenshot before referencing the element list. Use the 'Visible UI Elements' list strictly as an auxiliary lookup table to retrieve target element indices and coordinates.\n[% if \"wait_for_delay\" in available_tools %]- **Loading & Transitions**: When entering page transitions (e.g., app launching, web page loading, or progress indicators), use `wait_for_delay` to let the screen settle before executing target actions. Some transition states are difficult to discern, such as a thin progress line at the top of the browser screen during webpage loads. Before questioning whether an error has occurred, you can first adopt a waiting strategy to see how the device state evolves. If the state remains ambiguous after waiting, certain UI components might be malfunctioning or failing to load; in this case, consider retrying the action or pivoting to an alternative path.\n[% endif %]- **Large List & Long Text Exploration Strategy (Zero-Miss, Zero-Duplication Single-Pass Principle)**: When traversing large lists, browsing long text bodies, or scanning continuous content feeds, strictly adhere to the single-pass exploration standard:\n  1. **Unidirectional Anchor-Based Traversal (Zero-Miss)**: Maintain a consistent, unidirectional scan (e.g., uniform downward scrolling). Before each scroll, identify the bottom-most visible item/text segment as your visual anchor and carry that anchor plus the scan direction in short-term memory or the traversal ledger. After the scroll, evaluate this handoff before doing anything unrelated: if the anchor remains visible with new content beyond it, record the new content and continue in the same direction without scrolling back to verify; if the anchor is missing, continuity is uncertain, soLine truncated
 }

artemis/agents/operator/operator.py

@@ -1555,6 +1555,22 @@ class OperatorNode:
             """The recorded target semantics: observed (index) or described (coords)."""
             return {k: v for k, v in el.items() if k != "center"}
 
+        if tool_name in {"drag", "action_sequence"}:
+            from artemis.mcp.gestures import DragRequest, SequenceRequest, plan_drag, plan_sequence
+
+            try:
+                if tool_name == "drag":
+                    request = DragRequest.model_validate(args)
+                    planned = plan_drag(request, width, height)
+                    return [{**planned, "args": request.model_dump(mode="json")}], None
+                request_sequence = SequenceRequest.model_validate(args)
+                plan_sequence(request_sequence, width, height, self._max_burst_actions())
+                return [
+                    {"action": "action_sequence", "args": request_sequence.model_dump(mode="json")}
+                ], None
+            except ValueError as exc:
+                return [], f"Error during {tool_name}: {exc}"
+
         if tool_name == "click":
             target = args.get("target")
             times = args.get("times", 1)

artemis/agents/operator/prompts.py

@@ -82,6 +82,8 @@ _PRE_DECISION_ALL_TOOLS = (
 _PHYSICAL_ACTIONS_ORDER = OPERATOR_SHELL_ORDER
 _TURN_ENDING_ORDER = (
     "click",
+    "action_sequence",
+    "drag",
     "swipe",
     "input_text",
     "long_press",

artemis/agents/validator/action_execution.py

@@ -103,6 +103,9 @@ async def exec_action(
         return False, f"MCP call failed: {e}"
 
     action_item.update(execution="completed" if res.ok else "unknown", side_effect="possible")
+    action_item.update(res.metadata)
+    if res.metadata:
+        action_item["result"] = res.agent_message
     expected = (
         expected_input_state(wire_args["text"], wire_args["clear_exist"])
         if tool_name == "input_text"

artemis/agents/validator/execution_loop.py

@@ -384,7 +384,9 @@ async def run_validation_loop(node, state: State) -> dict:
     execution: list[dict] = []
     actions_to_execute = list(actions)
     total_actions = len(actions_to_execute)
-    burst = total_actions > 1
+    burst = total_actions > 1 or any(
+        a.get("action") == "action_sequence" for a in actions_to_execute
+    )
     if burst:
         logger.info(
             f"Fast-action burst: {total_actions} actions will fire back to back"

artemis/agents/validator/tool_declarations.py

@@ -203,6 +203,8 @@ LONG_PRESS_TOOL = tool_declaration("long_press")
 INPUT_TEXT_TOOL = tool_declaration("input_text")
 
 SWIPE_TOOL = tool_declaration("swipe")
+DRAG_TOOL = tool_declaration("drag")
+ACTION_SEQUENCE_TOOL = tool_declaration("action_sequence")
 
 PRESS_KEY_TOOL = tool_declaration("press_key")
 
@@ -299,6 +301,8 @@ VALIDATOR_TOOLS_DECLARATION: list[ToolDeclaration] = [
     LONG_PRESS_TOOL,
     INPUT_TEXT_TOOL,
     SWIPE_TOOL,
+    DRAG_TOOL,
+    ACTION_SEQUENCE_TOOL,
     PRESS_KEY_TOOL,
     READ_NOTE_TOOL,
     LIST_NOTES_TOOL,