[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

skills/dpgen-run/references/validation-and-run.md

@@ -91,11 +91,11 @@ DPDispatcher does not hash the raw bytes of `machine.json`. The checksum is
 useful provenance, but restart behavior follows the resolved current-stage
 submission identity:
 
-| Restart situation | Expected behavior |
-| --- | --- |
-| `machine.json` is byte-identical, the DP-GEN/DPDispatcher versions are unchanged, and the same stage generates the same tasks and common-file lists | The same submission hash is expected, so DPDispatcher can recover the existing submission JSON and scheduler job IDs. |
-| The file checksum changed, but the resolved block for the active stage did not (for example, only `fp` changed while `train` is active) | The active-stage submission hash may remain unchanged and recover normally. The raw checksum alone cannot decide this. |
-| A resolved machine/resource field for the active stage changed, or the generated tasks/common-file lists changed | A new submission hash is expected. DP-GEN re-enters the stage named by `record.dpgen`, but DPDispatcher treats its generated task list as a fresh submission rather than importing completion state from the old identity. |
+| Restart situation                                                                                                                                   | Expected behavior                                                                                                                                                                                                          |
+| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `machine.json` is byte-identical, the DP-GEN/DPDispatcher versions are unchanged, and the same stage generates the same tasks and common-file lists | The same submission hash is expected, so DPDispatcher can recover the existing submission JSON and scheduler job IDs.                                                                                                      |
+| The file checksum changed, but the resolved block for the active stage did not (for example, only `fp` changed while `train` is active)             | The active-stage submission hash may remain unchanged and recover normally. The raw checksum alone cannot decide this.                                                                                                     |
+| A resolved machine/resource field for the active stage changed, or the generated tasks/common-file lists changed                                    | A new submission hash is expected. DP-GEN re-enters the stage named by `record.dpgen`, but DPDispatcher treats its generated task list as a fresh submission rather than importing completion state from the old identity. |
 
 An unchanged machine file is therefore not sufficient if `param.json`, task
 generation, common files, or serialization behavior changed. Conversely, a