Thanks for the link of what you're up to. I'm not quite sure I understand why you need Mach-automation though.
Once you have your PC program create the gcode - why not just load and run in Mach normally? What am I missing?
The first thing that caught my eye was using the integration to make the testing and calibration
stages easier. The first test will be something like:
set 0,0 on a parts corner, manually move the gantry around to the various hole centers. hit a button
to record the spot this builds a list in the pc program. go back to 0,0.power steppers, then click another button
to send first point in list to mach, click to send next point and cycle through the list.
This should also be useful latter for quickly transferring hole patterns from parts to mounting plates without
really having to measure.
Other ideas to build on top of it. Maybe I could also break out of the gcode a bit.
Add a layer of logic on top where I can take physically separate gcode files, stack them in a que to run.
still fleshing out ideas but it seems super useful.