Disabling all plugins now catches ones that had no settings entry and previously survived.
What's wrong with this entry?
The bulk disable path now gathers plugin sources from the live enabled list as well as from settings, so a plugin enabled from a source with no settings entry is written out as disabled instead of surviving the sweep.
- Trusted sources are checked against a restricted record set before being written.
- With nothing enabled the path still reports "No enabled plugins to disable".
No enabled plugins to disable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.