fix(e2e): record Jetson cancellation recovery

test/e2e/docs/jetson-dispatch.md

@@ -139,8 +139,12 @@ workflow run ID and attempt, selectors, event, and hardware opt-in decisions.
 
 The Jetson controller writes private files under the target artifact directory:
 
-- `jetson-dispatch.json` contains the validated completed status and bounded
-  log. It excludes the base64 archive payload.
+- `jetson-dispatch.json` records the validated request and derived job ID before
+  submission begins. It records the cancellation reason and final outcome. If
+  cancellation reports that the job is absent after submission may have reached
+  the dispatcher, the controller records one follow-up request. A completed
+  artifact replaces this recovery state with the validated status and bounded
+  log. The file excludes the base64 archive payload.
 - `jetson-e2e-artifacts.tar.gz` contains the decoded target evidence when the
   service returns an archive.
 
@@ -149,6 +153,13 @@ failure. A successful proof requires the exact candidate request, a conclusion
 of `success`, `cleanup: "succeeded"`, a device identity, and the artifact
 archive.
 
+If a workflow fails after submission begins, inspect `jetson-dispatch.json`
+before another dispatch. Use its job ID to inspect the operator-service job,
+even when the receipt has no `cancellation` record. If artifact upload failed
+and the file is unavailable, use the job ID from the workflow error or logs.
+Cancel the job or confirm completion before another dispatch, regardless of
+whether the cancellation outcome is absent, pending, succeeded, or failed.
+
 ## Live Target
 
 `test/e2e/live/jetson-nvmap-gpu.test.ts` runs the Jetson hardware target for the