chore(deps): bloom 1.0.6, and the woff2 assets its web theme imports

Bloom 1.0's web theme entry imports its four `.woff2` faces straight from JS
(`fonts/font-urls.web`, reached from `BloomThemeProvider`), and Metro carries
neither `woff2` nor `woff` in its default `assetExts` — so the web bundle failed
to resolve them as modules and the export died. `fonts={false}` does not avoid
it: the import is module-level. Same two extensions Mention, Alia, Clarity and
CrowdSource add for the same reason.

This app depends on no `@oxyhq/services` or `@oxyhq/core`, so the three-package
1.0 upgrade is a single bump here. The typecheck is real evidence of it:
`customConditions: ["react-native"]` resolves Bloom to its own `src/`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: NateIsern

bun.lock

@@ -33,7 +33,12 @@ const originalResolveRequest = config.resolver?.resolveRequest;
 
 config.resolver = {
   ...config.resolver,
-  assetExts: [...(config.resolver?.assetExts ?? []), "wasm"],
+  // `wasm`: expo-sqlite ships wa-sqlite as a WebAssembly binary on web.
+  // `woff2`/`woff`: Bloom's web theme entry imports its four web fonts straight
+  // from JS (`fonts/font-urls.web`), and Metro carries neither extension in its
+  // default `assetExts`, so without them the web bundle fails to resolve them
+  // as modules — `fonts={false}` does not help, the import is module-level.
+  assetExts: [...(config.resolver?.assetExts ?? []), "wasm", "woff2", "woff"],
   resolveRequest(context, moduleName, platform) {
     // On web, replace react-native-tcp-socket with an empty shim
     // (TCP sockets are not available in browsers; Electron uses IPC instead)

metro.config.js

@@ -26,7 +26,7 @@
     "@maplibre/maplibre-react-native": "^10.4.2",
     "@noble/hashes": "1.8.0",
     "@noble/secp256k1": "2.3.0",
-    "@oxyhq/bloom": "0.50.2",
+    "@oxyhq/bloom": "1.0.6",
     "@scure/bip32": "1.7.0",
     "@scure/bip39": "1.6.0",
     "@shopify/flash-list": "2.3.2",