# Reproduce the script-only dispatch exercise All source records are synthetic. Do not use your normal Hermes data home. No credentials or external delivery are needed. Folder layout: trial/source.json trial/isolated-home/config.yaml trial/isolated-home/scripts/check_fixture.py Copy source-valid.json to trial/source.json. Set HERMES_HOME to the absolute trial/isolated-home path for this shell only. Minimal config.yaml: cron: {max_parallel_jobs: 1}. No gateway is started. Commands (using the CLI entrypoint that works in your installed environment): hermes cron create "every 24h" --name "Fixture artifact check" --script check_fixture.py --no-agent --deliver local --paused hermes cron resume hermes cron run hermes cron runs Verify trial/last-good.json contains one record and the expected source-window date. Hash it. Replace trial/source.json with source-invalid.json and run the same job again. Inspect job/run state: error and a failed execution are expected; the old file hash must match. Finish with hermes cron pause . Confirm the job is paused, then restore this shell's previous HERMES_HOME value. The launcher in this environment tried to prepare another dependency runtime for the isolated root. The successful trial used the existing dependency environment's Python with -m hermes_cli.main instead of the launcher. It did not alter the normal profile. commands.json records CLI-equivalent arguments and actual responses. Observed implementation limit: both a skipped paused job and a script failure could return process exit code 0. The script failure was visible in durable job state and run history. Inspect artifacts and history, not only exit codes. Manual dispatch was tested; no actual 24-hour timer, host wake behavior, model inference or external delivery was tested.