feat: node:start auto-provisions config and unlock key

When the wizard calls node:start with {hubUrl, username}, the handler
writes a minimal node.toml and a random unlock.key if they don't exist.
The daemon then creates the keystore on first start using the unlock
file — fully non-interactive.

Existing configs are left untouched: if node.toml or unlock.key already
exist, provisioning is skipped and the node starts as before.

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

1 files changed, 2 insertions, 2 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/platform.js b/packages/meshbay-hub/src/meshbay_hub/static/platform.js
index eeffd49..a8e17bf 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/platform.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/platform.js
@@ -227,9 +227,9 @@ export const node = {
   async installed() {
     return bridge && bridge.node ? bridge.node.installed() : { installed: false };
   },
-  async start() {
+  async start(opts) {
     if (!bridge || !bridge.node) throw new Error('Node bridge not available');
-    return bridge.node.start();
+    return bridge.node.start(opts);
   },
   async call(method, path, body) {
     if (!bridge || !bridge.node) throw new Error('Node bridge not available');