--- name: check-dragon-run description: Check the current status or completed standard results of an existing Helio Dragon run. --- Use this skill when the user asks for Dragon progress, results, errors, warnings, or an existing run's status. 1. Call `get_dragon_run` with the exact `identity` used during preparation and start. The backend simulation/optimization ID is a separate value, not a substitute. If the workflow identity is unavailable, ask for it; do not guess from unrelated history. 2. Report the service's actual state, warnings, failure information, and ready artifacts. Do not invent an ETA or say a run completed unless the service says so. 3. For Assess results, retain outcome, temperature direction, caveats, grouped suggested fixes, and any valid enhancement estimate. Do not reduce the result to a pass/fail boolean. 4. For Enhance results, report quality and consistency improvements exactly as returned, including unknown values. Do not convert unknown quality to Medium or fabricate print-time savings. When `printTimeComparison.status` is `READY`, report `originalSeconds`, `optimizedSeconds`, and their difference as estimated print times. `deltaSeconds` is optimized minus original: a positive value means longer, and a negative value means shorter. 5. When a full Enhance result or a requested comparison has no ready `printTimeComparison` and the Helio Slicing tools are connected, use the slicing `gcode-timing` workflow only with (a) the exact local original retained from preparation and (b) the ready enhanced artifact. `get_dragon_run` does not recover the original. Before any upload, stream-hash the retained original and require its SHA-256 and recorded source identity to match preparation. If that exact original is absent, ask the user to provide or reacquire it, or report that comparison is unavailable; never construct a source URL, substitute a current same-name file, or use the enhanced file as both inputs. A full-result request authorizes a temporary internal download of the ready enhanced artifact, without separate user download consent; use the private HTTPS-only helper in `gcode-timing`, not a browser. Then upload the validated original and enhanced bytes through the existing core `get_presigned_url` flow using each exact returned `mimeType`. Stream bytes and hashes; never print their contents, URL, or token. Preserve the original and do not re-slice. Reuse the validated pair and stable identity on ambiguous creation, and poll the slicing result only while pending. If the slicing tools are not connected, say that a Helio Slicing connection is needed; never fall back to Dragon credentials. A missing, unavailable, or failed comparison must not change a completed Enhance run into a failure. 6. If artifacts are ready and the user asks for them, follow `get-dragon-output`. If the run failed, explain server-provided details and do not create a replacement run without an explicit request. Use `stop_dragon_run` only after an explicit user request to stop the identified active run. For `STOP_REQUESTED` or `STOP_UNKNOWN`, poll with `get_dragon_run`; neither state confirms cancellation completed. Do not resend an ambiguous cancellation or create a replacement. Only `STOP_REJECTED` allows a cancellation retry with `retry_rejected: true`, after resolving the reported rejection and an explicit retry request. Finished, failed, or stopped runs need no cancellation.