V3 has a clash with Leo's mod and for now I'm going to suggest putting bugfix V3 above Leo's mod in the load order (mod screen). This hasn't been fully tested but gets past initial problems.
Viewing post in Bugfix for 1.0d - V6b
Leo's mod replaces several functions where the Bugfix mod attempts to modify lines, thus the line numbers are wrong if the Bugfix is applied second. Applying Leo's mod after the Bugfix mod should safely resolve all conflicts, though it will undo a couple fixes.
The following files have conflicts: outside.gd, joblist.gd, and enchantments.gd. Only the conflicting bugfixs to outside.gd are significant, as those improve the handling of removed slaves. Part of your change to joblist.gd has the same result as the bugfix, and the bugfix's change to enchantments.gd is not important.
Would there be any harm in a general instruction to put the bugfix mod top of the load order? For any mods using file replacement I'm assuming there will be more stability if the file replacement is applied second. For mods using line changes I'm assuming clashes would be rare (identical line changes) but Strive would still be more stable with the bugfix applied first so the other mod remains internally consistent.