# Bounded timed test

Use a separate Hermes data home and no credentials. Put timer_fixture.py under isolated-home/scripts and source.json one directory above isolated-home, containing {"records":[{"id":"timer-fixture","source":"synthetic input"}]}.

Create a script-only every-1-minute job with --script timer_fixture.py --no-agent --deliver local. Automatically poll the real Hermes cron tick in a bounded local loop. Do not call cron run and do not edit next_run_at. Compare stored due times with actual execution times and inspect runs.jsonl and last-good.json.

After two successes, change source.json to {"records":[]} and wait for the next due-time attempt. Inspect its durable error and confirm that last-good.json has the same hash as before. Pause the test job and stop the loop in a finally block, including on assertion failure. No gateway service or external delivery is needed.

The exact tested harness is maintained as scripts/test-timed-workflow.py in the private source checkout. timed-commands.json records its actual CLI-equivalent arguments and responses; timed-receipt.json states the entrypoint and limits. The successful trial took about 190 seconds, with two successful due-time fires and one intentional failure. All timestamps retain UTC or explicit timezone offsets.