arkennemasis Run Switches (what runs, what is skipped)

The arkennemasis variation canvas grew optional stages until their enabled toggles were scattered across eight thousand pixels of graph. Somewhere out there was the switch for the expensive stage, and there was nowhere to look to answer the obvious question: what is this run actually going to do? ArkRunSwitches collects every optional stage into one readable panel at the top-left.

Notice what's not in it: loading the sheet, generating the images, and saving them. Those aren't optional, so they're not listed. The panel is for the parts you might genuinely want to skip this run.

The six switches

• 1. Check every image (fast, free) - on by default. Measures each result against the original: right colour, did the product move, did the colour leak. Milliseconds, costs nothing. Turn it off and nothing stands between a bad render and delivery.
• 2. Let AI LOOK at every image (SLOW, costs money) - off by default, and the only one that is. About 90 seconds and one paid vision call per image, so on a 30-image run it's the difference between minutes and most of an hour. The tooltip says it plainly: the cost of forgetting should be that a slow check didn't happen, not that you spent money. Turn it on for a final pass once the prompts are settled.
• 3. Make the Excalidraw board - on. The matrix.excalidraw client deliverable.
• 4. Make the review web page - on. The review.html with Approve/Reject.
• 5. Turn the board into a picture - on. Draws the grid as a normal image so you can see it inside ComfyUI, and saves matrix.png.
• 6. Make the shop upload file (CSV) - on. The spreadsheet a client imports into their shop.

Each switch outputs a BOOLEAN (the short wiring name - verify, qc_critic, excalidraw, html_sheet, board_preview, store_export) plus a report describing what the run will do. The labels carry the meaning for the human; the short names carry the wiring.

Why booleans on wires instead of a fancier switch

The pack deliberately chose plain Boolean outputs over a frontend-extension switch. The reason is in the source: a frontend switch sets node modes and needs JavaScript kept in step with the graph's group titles. Booleans on wires need no frontend and cannot silently desynchronise from the canvas. If the wire says off, the stage is off - no "the extension forgot to update" failure mode.

Install and gotchas

Part of the arkennemasis pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Hishamahmer/comfyui-arkennemasis
pip install -r ComfyUI/custom_nodes/comfyui-arkennemasis/requirements.txt

Restart, or install via ComfyUI Manager by repo URL.

The switch people get wrong is the second one. It's off by default on purpose - if you turn it on for every run, you've made the expensive stage the default, which is exactly what the design avoids. Wire it on for a final pass over a settled recipe, then flip it back. And if you're debugging a run where the images look wrong but nothing stopped them, check switch 1: with it off, the pipeline happily delivers whatever the generator produced, and that's a you problem, not a bug.