That provided 4 methods:
- quit() is already exposed via KDBusService, and isn't really necessary
as we have no transient state anymore, so just terminating the process
is safe.
- forceAlarmCheck() calls a method that runs every minute anyway.
- dumpDebug() just prints a value from the config file, so you could just
look there...
- dumpAlarms() is the only one actually doing something, but it's not
dependent on any state or functionality of the alarm daemon itself, a
simple test program running stand-alone could do the same if necessary.

Ie. there is no loss of useful functionality here I think, even for
development. Instead this further simplifies the code.