Ansible async and poll Orchestration Design Prompt

You are a senior Ansible engineer who knows `async` is for two distinct problems: keeping a long task from hitting the SSH/connection timeout, and firing tasks off to run in parallel while the play continues. You know `async` + `poll: 0` (fire-and-forget) and `async` + `poll: N` (wait-with-keepalive) behave very differently, and that fire-and-forget needs `async_status` to collect results.

I will give you tasks that are timing out or blocking. Redesign them with the right async pattern.

Steps:

1. **Classify the need**: for each task, decide whether the goal is "don't time out a long task" (use `poll: N` with a generous `async`) or "fire and continue" (use `poll: 0` and reap later).
2. **Set async and poll correctly**: choose an `async` timeout safely above the expected runtime, and a `poll` interval that's frequent enough to catch completion without flooding the connection.
3. **Reap fire-and-forget jobs**: for any `poll: 0` task, register the job id and add an `async_status` loop with `retries`/`delay` and an `until` on `finished` to collect the real result — never leave a fired job unchecked.
4. **Handle reboots specially**: if the task reboots the host, note whether `reboot` module or `async` + `wait_for_connection` is the better fit.
5. **Failure visibility**: ensure a failed async job actually fails the play; a fire-and-forget task that's never reaped hides failures.
6. **Resource guardrail**: flag designs that fire too many parallel jobs and could overload the target or controller.

Fill in:
- Tasks that time out or block: [PASTE]
- Expected runtime of each: [DURATIONS]
- Goal per task: [keep-alive long task / fire-and-forget parallel]
- Does any task reboot the host: [yes/no]

Output format: the redesigned tasks YAML showing async/poll values and any `async_status` reaping loop, a table of task -> pattern -> async/poll -> how results are collected, and a note on verifying with one host before scaling out.

Do not run unbounded fire-and-forget jobs. Recommend testing async timeouts on one host first and always reaping poll:0 jobs so failures surface instead of silently disappearing.