Verify Panel

In-browser recompute panel for the PQ key binding (2026-07-30). Closes a real gap flagged the same day the binding shipped: /verify-proof and /.well-known/pq-key-binding.json are both JSON APIs -- every "verify this yourself" claim meant "curl this," not "click a link and watch it recompute in front of you." Two cards now (2026-07-30, same day): ours (ML-DSA-65, NIP-01 carrier) and trustless-ai/KYA-L4's (SLH-DSA-SHA2-192s, on-chain OCP-anchored, no carrier) -- the full symmetric mirror of Merlini's own panel (ai.verticecriativo.pt/quantum), which already verifies ours. Neither side trusts the other's UI; both independently recompute from raw bytes, fetched live (CORS-enabled) from each origin. Uses vendored @noble/post-quantum@0.4.1 + @noble/hashes@1.8.0 (static/vendor/, see its README) served from our own origin, not a CDN -- a "don't trust, recompute" page shouldn't itself require trusting a third party. Scope is the hash-recompute + PQ companion-signature verify + tamper check, same as the shared pq-key-binding-v0 conformance profile's documented split; the classical signature (Schnorr for ours, the on-chain record() sender for KYA-L4) and the anchor-vs-chain read are the separate "deeper lane" (POST /verify-proof for ours; read the tx directly for theirs).