amal66 moves Mike's heavy lifting off the front desk

A proposed job system shifts slow and failure-prone work out of the live user request, without forcing every installation to add new infrastructure.

amal66 is building one durable background-work model that can use a fast message service when available, or rely on the application's existing database when it is not. That matters because a conversion, export or cleanup task can survive a restart instead of quietly failing after the user has moved on.

It puts several operational chores on that footing:

Document conversion and table extraction can continue after the browser closes.
Exports can be prepared in the background, then downloaded when ready.
Audit records, account deletion and storage cleanup gain retries rather than best-effort handling.
Connected-service access can be refreshed proactively, reducing avoidable reconnection prompts.
Older document formats can have their text prepared once for later use.

Existing installations retain their current heavy-work behaviour unless they opt in, while new container-based installs receive asynchronous processing and progress updates.