Yeah, that's the classic trap. High unit test coverage on components doesn't translate to confidence because you're testing in isolation. You're not catching integration failures, state management bugs, or actual user flows.
For e2e flakiness, the problem is usually waiting for elements that don't exist yet or racing network calls. Switch to waiting for specific conditions instead of hardcoded waits. Playwright's waitForLoadState and explicit assertions on page state help way more than tweaking timeouts.
Honestly though, I'd question if you need 80% unit coverage. Drop that to maybe 50-60% on pure logic, then invest those cycles into focused integration tests covering actual user paths. Fewer, slower, more reliable tests beat tons of flaky ones. We cut our e2e suite in half and actually ship faster.