I took the app, made a backup to a zip file, and then created it to a new, completely different app.
It changed behavior again, and added, in another transaction, a default value to a NULL field that didn't exist in the prior version.
I have a development, and production version. The process of moving the version from development to production seemed to create new bad default mappings.
In "ChefEventComplete", it added a new mapping for "eventGift" field to "TRUE", which I cannot remove using your technique.
I changed the field from NULL to FALSE, and then the mapping removed the TRUE result, and changed it to FALSE. When I set the parameter to NULL it removed the FALSE mapping and set the result to TRUE again, for no reason.
The editor is storing something which is not in the .js file and not in the mappings file, and it cannot be edited away. It is continuing to add mappings which I did not product, today is another example.
In my development version it worked fine, in the production version, created from a backup, it introduced the bug. When I ran the version that had tested perfectly in development, the production event created a new faulty transaction record that didn't exist in a completely separate development instance.
I'm really finding this instability amazing.