fix: prevent tokio runtime deadlock in credential issue/verify

The credential issuance and verification handlers used
Handle::block_on() directly inside the tokio runtime, causing a
deadlock. Wrapped with block_in_place() to properly yield the
runtime thread.

Also completed full feature verification across all 25 test groups
(~175 checks) on live server.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

neode-ui/src/stores/web5Badge.ts

@@ -0,0 +1,18 @@
+import { defineStore } from 'pinia'
+import { ref } from 'vue'
+import { rpcClient } from '@/api/rpc-client'
+
+export const useWeb5BadgeStore = defineStore('web5Badge', () => {
+  const pendingRequestCount = ref(0)
+
+  async function refresh() {
+    try {
+      const res = await rpcClient.call<{ requests: Array<{ id: string }> }>({ method: 'network.list-requests' })
+      pendingRequestCount.value = res.requests?.length ?? 0
+    } catch {
+      // ignore — badge is best-effort
+    }
+  }
+
+  return { pendingRequestCount, refresh }
+})