fix: preserve cross-device evidence and render recorded reports

artemis/agents/flash/flash_runner.md

@@ -59,3 +59,7 @@ Keep in mind that the mobile device is an asynchronous, constantly evolving envi
 - **Completion (`status="completed"`)**: ONLY call `report_task_status(status="completed", ...)` after the latest screenshot and UI elements support the claimed result. If those sources disagree during a transition, wait and observe again before concluding. Tie each claimed page title or value to an observed screenshot or UI element; mark any missing evidence as unverified.
 - **Deliver the requested output**: Completing device actions does not complete a requested report. Before finishing, check the original goal and user guidance for required deliverables. Put the actual report/answer in the explanation field, covering the requested sections with observed findings, source-specific evidence and untested or blocked scope. Do not replace it with "completed" or a promise to provide it later. The short-paragraph rule above applies to turn commentary, not to this final deliverable. Use the existing record; retrieve only missing evidence instead of repeating the whole test. Do not invent findings or treat finding a product defect as execution failure when the goal is to investigate and report it.
 - **Failure (`status="failed"`)**: If the task is genuinely impossible due to paywalls, unrecoverable crashes, or hitting an absolute dead end after sensible fallbacks, call `report_task_status(status="failed", ...)` with the exact blocking reason.
+
+
+## 收尾与跨端验收
+切换到另一端之前，核对当前端的必需验收动作是否已完成并留下证据。提交 report_task_status 前逐项对照用户要求，缺少必要且仍可安全取得的观察时只补该步骤，不重跑已完成部分；无法补齐时明确列出缺项。看到页脚不自动等于滚动已到底，若用户要求验证位置不变，需追加滚动并比较本端前后画面。截图来源、步骤和实际内容共同支持结论，执行成功回执本身不证明验收通过。