reverse the disabled/enabled default and logic.

[petersilva]

currently when you add a configuration to sr3, it is enabled by default. so the next time
a general sr3 start command is issued, it will be started. Normally one first creates a file
and then spends some time tweaking... it is almost never a good idea to start a newly added
configuration file.

So it would make more sense to have configurations default to "disabled" ... and have the analyst
enable them once satisfied that a configuration is runnable.

When people add a configuration, it is done by adding a file: ~/.config/<coomponent>/<configuration>.conf

To disable a configuration one must create a ~/.cache/<component>/<config/disabled file to disable it.

It would likely be better for a configuration to be disabled by default, and only be enabled if ~/.cache/<component>/<config>/enabled is present (modulo hostdir)

[petersilva]

for transition, if you find a "disabled" file... assume upgrade and convert the whole thing?

• for all places where there is nothing, put an enabeld file.
• for all places where there is a disabled file, remove it.