The overnight queue rules and the evening preflight check (free sample)

Turn this list into queue.json with run_id r<date>: one job per prop, output_dir staging/<run_id>/<id>, tris_max, minutes_max and rounds_max 1 to 3, and publish, upload, purchase, install_addon and delete false, spend_usd 0.
Run queue_preflight.py and fix every finding except P1. Then show me the queue and wait for my yes.

The rules and the check are in the file.

# The overnight queue rules and the evening preflight check (free sample)

From the Hermes Overnight Worker by PaperChaseWebb. Free to use. Works with Grok Bot, Claude Code, Codex and Hermes.

Two pieces of the worker you can use tonight, before you set up any Blender automation: the approval rules that decide what an unattended agent may do while you sleep, and a small read-only Python check that tells you whether tonight's queue follows them. No Blender needed for either.

## 1. The rules for an unattended night

1. **The queue is approved before the run.** The owner sees every job, its budgets and its source, and replies `yes queue <run_id>`. The yes names the run id. A job added after the yes means a new run id and a new yes.
2. **Every job has three budgets.** A triangle cap for the exported mesh, a wall-clock cap in minutes for the Blender process, and a cap of one to three critique rounds before the job stops and goes to a person.
3. **Writes go to staging only.** Every output goes to staging/<run_id>/<job_id>/. The owner's files sit in originals/, are hashed before the run, and are never written.
4. **The critic is not the builder.** A separate session, under its own name, judges each preview against the brief and writes keep, revise or drop.
5. **Nothing is published or bought.** No publishing, uploading, buying assets or credits, installing add-ons, deleting, or calling a paid generator. Those are daytime tasks with the owner present.
6. **The morning promote step n