Recent change to assemblyWF introduced a required step leaving several hundred in-pipeline objects in limbo

[blalbrit]

The addition of a new pre-requisite to assemblyWF left hundreds of active objects in limbo since they do not have that WF step instantiated. Filing a remediation ticket to fix those objects (and others that may crop up) but wanted to leave this as a reminder to double-check with accessioning/infrastructure teams before dropping a WF step requirement change to prod.