Found why G30 under beta9 was not doing what I expected
I don't know if this would be consider a "bug" or not but the behavior of commands like G30 P0 X0 Y0 Z-99999 H0 were not doing what I expected.
It turns out the when doing a simple G30 S-1 the movement starts out very slow and the Z-probe is monitored.
However it appears that when doing a command like G30 P0 X0 Y0 Z-99999 H0 the movement starts out fast and the Z-probe is NOT monitored.
Then when nearing the bed the movement slows to the same rate as exhibited by a G30 S-1 command and the Z-probe is now monitored.
In my case, due to a config file typo, the "near the bed" position was unreachable, the movement never slowed, the Z-probe was never monitored and, naturally, the bed was impacted.
I'm thinking that perhaps the Z-probe should be monitored during all phases of G30 movement so this type of problem does not occur.
Perhaps if the Z-probe is activated during the "fast movement" phase the process could be aborted and an appropriate error message displayed informing the user of the issue.
On the other hand I could be completely wrong about what I think is happening.