MutationQueue

Enqueues "forgivable" mutations (likes, follows, and similar fire-and-forget writes) for background execution with retry, instead of awaiting them inline from a ViewModel.

enqueueMutation/enqueue return immediately — the actual ApiClient.request call and any retries run on scope, which the caller owns (e.g. an app-scoped CoroutineScope that outlives any single screen). This is the fix for two problems with calling apiClient.request(...) directly for mutations:

1. No queueing: if the process dies mid-flight, the mutation is silently lost.

2. No retry: DefaultRetryPolicy deliberately excludes POST/PATCH by default (retrying a non-idempotent call risks a duplicate write), so a plain NetworkClient never retries them — correct for most calls, wrong for ones the caller has decided are safe/idempotent-in-effect to retry (e.g. "set like state to true" is idempotent even though it's a POST).

Behavior:

• Coalescing: enqueueing under a MutationKey that already has a pending/retrying mutation replaces it — including cancelling any in-progress retry backoff — so only the latest desired state for that key is ever sent. See MutationKey.

• Retry: reuses RetryPolicy (the same interface io.github.maniramezan.kenwork.network.NetworkClient uses), but as a queue-level (or per-enqueue) setting distinct from io.github.maniramezan.kenwork.network.NetworkClientConfiguration.retryPolicy — so opting a mutation into non-idempotent retry never loosens the client's own default. It is also the only retry layer: each attempt runs under withRetryPolicy(RetryPolicy.None), so a io.github.maniramezan.kenwork.network.NetworkClient doesn't retry underneath the queue and multiply the attempts. With the defaults, a mutation has at most 3 queue attempts; OAuth's 401 refresh-and-replay remains a separate path within each attempt. The client's configured connectivity gate is awaited before each queue attempt, using the client's time bound, so disabling nested retries does not bypass connectivity waiting.

• Persistence: pass a MutationCodec to enqueue to have the mutation survive in store (see MutationStore for durability); omit it for a purely in-process, fire-and-forget mutation.

• Status: observe statusFlow for a key to reflect pending/retrying/succeeded/failed in the UI.

• Lifecycle & Cleanup: completed workers are removed once idle, and cancel cancels in-flight work, removes persisted records, and resets status to null. Internal status tracking is bounded so the queue does not grow indefinitely.

Parameters