What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since

the docs page contains a link to Arc which is https://docs.rs/async-std/1.8.0/async_std/gsync/struct.Arc.html when I believe it should be https://docs.rs/async-std/1.8.0/async_std/sync/struct.Arc.html.

Task export inconsistent with actions

In JS mode, exporting tasks as module.exports = class SomeTask causes AH to throw an error when trying to execute it ' task not found' but exporting as exports.someTask = SomeTask works. Actions work either way.

From @evantahler:
actions have this line https://github.com/actionhero/actionhero/blob/v24.0.4/src/initializers/actions.ts#L65-L67
where