[Enhancement] make it easier not to accidentally flush bad data to permanent storages

[Twisted-Code]

I use the held item as a placeholder for my macro test parameters and keep forgetting to disable/remove the scribe's gambit before clearing the rest of the grid for the actual macro. The result is that the iota being accepted by Scribe's Gambit changes, Even though it's in a completely invalid state for the hex. 😬
I was thinking perhaps make it so that, by default, it only flushes persistent data storages (including the help focus and anything else) when you press a button. That way you can edit freely and choose when it recalculates?

[Twisted-Code]

(It would also be good if you could cover the "I want to provide arguments to my macro test" use case I have for the held item, but I have no particularly good ideas for it)