WASM order of execution is arbitrary - affecting `auto_run_on_build`

WASM entries can execute out of order. 

Which isn't a problem for most of the code generated by these macros, except for `auto_run_on_build`, which can fail when trying to access resources that are assumed to have been inserted already.