No divergency should occur in the automated slapos business process.

fixConsistency can be called twice in the same transaction.

Packing List does not control instance state.

No purchase packing list are created with the software installation.

Slaptool should not try to update Packing List state.

afterSetUp logs as superuser, do not repeat it.

Thanks to this running tests outside of Zope has similar conditions: Manager
is used.

Set more properties on invoice, as there are not merged anymore.

Drop delivery select method, as there is no need to merge invoices.

Invoicing Software Installation usage can be done with a global alarm if needed
(as done for Software Instance).

Lines will not be merged in invoices, so aggregate shall follow.

Missing script.

Workflow history is analyzed to decide the kind of packing list to create.
Remove hardcoded values and use template documents instead.

Check simulation only once.

Drop Sale Order expanding, as no Sale Orders are going to be present.

Switch alarm to expand *and* solve causality state in same moment. See
9d1b92cc which is changing causality state
on delivery state change.

Update test to reflect the change.

Check SimulationMovement_buildSlapOS no-op behaviour on delivered Simulation
Movement.

Check behaviour of Delivery_updateCausalityState in case of been called on
documents with various states.