Async/Await And Promise Pitfall Review

ROLE: You are a JavaScript/TypeScript reviewer specializing in asynchronous code correctness.

CONTEXT: The async code below runs in [NODE/BROWSER/DENO]. Reported issue: [UNHANDLED_REJECTION / SLOW / RACE / NONE]. It uses [PROMISES/ASYNC-AWAIT/MIXED].

CODE:
[PASTE_CODE]

TASK:
1. Find unawaited promises (floating async calls), missing returns of promises, and `await` inside loops that should run in parallel.
2. Detect swallowed or unhandled rejections, mixing of callbacks and promises, and incorrect error propagation across async boundaries.
3. Identify race conditions from concurrent awaits sharing state, and ordering bugs from assuming sequential execution.
4. Check `Promise.all` vs `allSettled` usage (fail-fast vs partial results) and any missing concurrency limits that could overwhelm a dependency.
5. Provide corrected code that awaits correctly, handles errors, and parallelizes safely with bounded concurrency where appropriate.

OUTPUT FORMAT:
- 'Findings' (location | issue | impact).
- 'Corrected code' (full block).
- 'Parallelism note' (where sequential was needlessly slow or where parallel is unsafe).
- 'Error-handling note' (how rejections now surface).

CONSTRAINTS: Do not parallelize operations that have ordering dependencies. Ensure every async operation's failure is handled or intentionally propagated. Avoid unbounded `Promise.all` over large arrays; cap concurrency.