Greg Weber

> By this do you mean that your expectation would be that neoq.Start returns error when there are pending migrations? (assuming this behavior is behind a configuration option, like WithAutoMigrate(false))...

yeah, we are able to workaround such issues right now.

That sound perfect to me. Should it be `neoq_jobs_completed` past tense? For actual GC of the completed table, I think it is fine to leave that to the user for...

> This behavior would likely live outside the job's transaction, but dependent upon its success. The reason being: if the job succeeds and its status is updated, we wouldn't want...

Do the pushed states need to be dynamic? Wouldn't it be better to model them ahead of time as a child state machine and when the event is sent behave...

Is the problem just one of duplicated code? What would help explain the most is if you give the state machine that demonstrates this. The README and test case seem...

Can x2bonus just be a separate state machine? In [StateTree](https://github.com/gregwebs/StateTree) this could be the same state machine using concurrent substates.

[StateTree has history states](https://github.com/gregwebs/StateTree#history-states). I found switching the behavior to default to the last history state rather than setting a default state to be invaluable. That is what is in...

I have an example with concurrent substates in the README. I don't understand everything that is going on in the given example, in part due to missing references, but also...

This applies to the whole record. It is very useful to also selectively not anonymize certain column values. We have been able to achieve that with an if statement in...