qector-workbenchlisted

# QECTOR Workbench (Optional Desktop App) Source of authority: v1.0.0 reference manual, section 17.5; the 1.0.0 API freeze note; the device-local Workbench handler. ## What the Workbench is The Workbench is an **optional desktop application** that exposes real `.stim` / `.dem` loading, a cancelable benchmark job queue, and JSON / CSV / PDF export. Every number is traced to a real decode, with an environment snapshot and git commit. It is real historical code (changelog `0.7.0 -> 1.0.0`) but it is **absent from the shipped `qector-decoder-v3` wheel** (file listing, pip RECORD, `--mcp` grep, filename search, pip cache). Its exact tools, version, license, and hardware status are **device-local** and must be negotiated with `initialize` and `tools/list` on the target machine. ## The class hierarchy - **`QectorWorkbench-Portable.exe --mcp`** is the launch command on Windows. The executable is a portable app; it starts an stdio MCP server. - **`workbench.py`** in the library is a headless application controller (benchmark job queue, JSON/CSV/PDF export). Its docstring references a `run-qector` skill that is not part of this package. - The optional direct-wheel `qector_decoder_v3.workbench` module is not shipped in 1.0.0. ## How to probe the Workbench `qector-admin.workbench_probe` runs a local stdio probe of an approved Workbench executable. The admin server must be enabled with `QECTOR_ADMIN_ENABLED=1`, the binary must sit inside `QECTOR_WORKBENCH_DIR`, and the