b08daadbdc
A bad ed25519 pubkey on the creator member (legacy data) made sealTopicKeyForMember throw, which propagated up through createTopic and made the WS topic_create handler never send a topic_created frame. CLI saw a 5s timeout and printed 'topic create failed'. Wraps the seal call in try/catch — topic creation succeeds even if no copy gets sealed for the creator. They'll see GET /v1/topics/:name/key return 404 until they re-seal (or a holder does it for them via the phase-3 background loop). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>