Quick update: out of professional respect for the work behind Oban and Oban Pro, and because Squid Mesh operates in an adjacent space, I’m going to stop using Oban directly as the execution backend.
The current integration uses Oban as the durable job substrate (we don’t use it for retries, exp. backoff, etc). Going forward, Squid Mesh will provide its own narrow execution engine focused only on the runtime guarantees the project needs: durable step dispatch, delayed continuations, restart/redelivery behavior, cron activation, and test support.
That should hopefully mean a few weeks of development (to build only what I need at the moment) until I have something ready to be used.
