Unit tests need to be created that tests obfuscating with all possible Mutator permutations that are 2 Mutators long. So basically given the dozen or so current Mutators, make sure Mutators don't just work on their separately, but together as well. I've run into a few random cases where using Mutators in specific combinations produces faulty payloads, and want a test that can do this for me.

Us

--- FAIL: TestScripts (0.19s)
    --- FAIL: TestScripts/tiny (8.78s)
        testscript.go:382: 
            # Tiny mode (8.772s)
            > garble -tiny build
            > ! binsubstr main$exe 'main.go' 'fmt/print.go'
            > env GODEBUG='allocfreetrace=1,gcpacertrace=1,gctrace=1,scavenge=1,scavtrace=1,scheddetail=1,schedtrace=10'
            > ! exec ./main$exe
           

Is your feature request related to a problem? Please describe.
If you have XAML Databinding to public members and use ForceRen (because lets assume your project is not a public library so renaming public methods is acceptable) then this will obviously break databinding.

Describe the solution you'd like
I've hacked a solution which extracts all databinding out of the XAML and makes a l

Add 'since' information to plugin configuration parameters by inspecting the commit history.

When running confusion(Loading classpath...), this exception was thrown, how to solve it?

at the moment only ntw::system namespace and ntw::memory components are tested.
It would be great to have a test suite that covers most of the library.