Two engines.mc9.config.engine: native (default; mc9hook.dll inside MC9 posts MC9's own commands and fills its dialogs - no mouse,
keyboard or screen coordinates) and clicks (the old mouse/keyboard drivers, used only if the DLL cannot start). The prebuilt DLL is shipped in the wheel.
Offset auto-search inside MC9 (byte patterns, string anchors, MFC message maps), tools/sigmaker.py for other builds.
Many runs:Circuit.step, stepping_mode, clear_steps (written as MC9's [Stepping] sections), temperature lists, Monte Carlo
(tolerance, monte_carlo, model), run parameters (run.params, result.select), the optimizer (optimize, native engine).
Any MC9 part in Netlist/Schematic: definitions are learned from MC9 on first use (catalog.learn), placed by the generic placer
(transistor-like parts on the signal path, everything else beside the circuit joined by node names), J, JP, MP, Z, E, SW helpers.
Native engine: Monte Carlo histogram window screenshot (show_histogram), cursor_case, cursors_y, autoscale, restore_scale,
normalize_y, command(name) for ~20 more MC9 commands; the hook now sees posted menu commands and can switch MDI windows (mdi).