mobile-load-race pattern

i updated obsidian from `1.12.7` to `1.13.4`, afterward i updated harper to latest version, the harper underlines are flashing instead of drawn always, it just happens on mobile/android.

on obsidian startup on android, it just shows a notif about fail to load harper, but after some sec, it actually loaded while underline flashes.

i went to settings, disabled and re-enabled the harper, the flashes fixed, but i have to do this step on every obsidian startup

i asked "Claude" why this keep happening, it said cuz of mobile-load-race pattern, following is claude response:
```
That matches a known pattern — Harper's WASM engine sometimes isn't ready by the time Obsidian's mobile shell finishes its own load,
so it fails silently then partially initializes in a broken decoration state.
Disabling/re-enabling forces a clean re-init, which is why it fixes it each time.

🐛 Not something you're misconfiguring
This lines up with existing reports on Harper's tracker
(mobile-load-race issues, e.g. #1499, #2847 "Issue on mobile") — no official fix from Harper side yet as of my search.
```

The report names no files, tests, or entry points. Start by reproducing the startup sequence on Android and inspect the Harper WASM initialization and underline behavior; done means Harper loads without the startup failure notification and underlines remain stable without disabling and re-enabling it.

Written by the indexing model from the issue text.