Why this matters
The bug. Holding a Promise in a variable doesn't *do* anything; awaiting it is what extracts the value. Reading .name from a Promise is silently undefined and the bug ships.
The fix. Both calls were started concurrently (good — they fire in parallel), but only one was awaited. Add await to the other. Modern lints catch this with @typescript-eslint/no-floating-promises.
Why it's sneaky. This pattern *looks* like the standard concurrent-await idiom and the test suite often passes if mocks resolve synchronously.
Review heuristic
Read every async function twice: once for missing awaits, once for unnecessary awaits. The first set causes incorrectness; the second set causes performance regressions that nobody notices until the API gets slow.