Hey Andrew!
Just wanted to say I think this is a great idea, one that I’ve asked for before. I’ve done a little work in environments (Adobe Flex, Java) that call this 2-way data binding.
I recently realized however that there’s a complication makes this a lot more challenging. The UI control values are persisted into the flash memory which has a limited lifetime of between 10K and 100K writes. When they’re stored in response to user input, no big deal. If the code is changing the values, however, Wizard will need to come up with a reasonable strategy akin to a write-behind cache. A recent thread dives into a related issue in detail.
Pixelblaze is mostly a SPA, so I’ve always considered the UI to pretty much be open source already. I’ve used the inspector/console to hack my own features in as well as occasional TamperMonkey scripts. Also, if you search the forums you’ll see curl commands for uploading a new SPA to make your edits permanent.