scenario-zbrush-automation

# ZBrush automation (tools and pipeline TD) An expert ZBrush TD automates with contracts and proof: every file is its own tool, every step is a separate call with a time limit, every output is read back from disk, and a hung plugin costs one file, never the batch. ZBrush has no timeout, no undo control from Python and dialogs that code cannot answer, so the safety lives on the agent side: the runner, the checkpoints, the report. If a sibling skill named here is missing from your available skills, ask the user to install it (`npx skills add scenario-labs/skills --skill <name>`); unattended, proceed from tool schemas and flag the gap. **REQUIRED BACKGROUND:** scenario-zbrush-expert (bridge, zb_launch, zb_ops, zb_audit, review loop, 2026 traps). **Status (2026-09-24, refactor pass 2):** every ZBrush call here is **not yet run in ZBrush** (no session assigned; the README's startup stall is still open). Offline: 56 tests pass (`tests/code/zbrush-automation/run_offline.py`), including a GoZ reader and writer matching ZBrush's own `ZResources/DXFStar.GoZ` byte for byte. Live suite: `tests/code/zbrush-automation/run_live.sh`. ## Stance (the expert delta) - **One file, one tool, one step per call.** "Only one zscript/plugin can be active at a time, so if your zscript calls someting like UV Mapper control passes to UV Mapper and no more commands will run" (marcus_civis, ZBrushCentral 2014); pressing Decimation Master's Pre-process ended ijacobs' script (2013) and forced cgside int...