test(node): pin the fresh-install-before-provisioning safety property

Two properties discussed but not yet pinned by a test, both load-bearing
for service mode:

1. A bare `meshbay-node` with no config yet -- exactly what the W3
   Startup .vbs and the service-mode Scheduled Task both run unattended,
   on the very first boot after a fresh install, quite possibly before
   the user has ever opened the client -- must fail closed, fast, and
   without a trace. Measured by hand first (under a second, zero bytes
   written against a real empty %LOCALAPPDATA%); this pins it as a test
   so it can't regress silently. load_config() already returns an empty
   Config on a missing path rather than raising, so main() reaches its
   own "hub.username not set" exit before ever touching NodeDaemon() or
   asyncio.run() -- nothing here has to mock the daemon startup.

2. node:start (main.js) must call provisionNode() before it ever checks
   for the service task or spawns -- reversed, the wizard's first Start
   on a fresh service-mode install would run/query the daemon before
   node.toml exists for it to read. Source-read, same technique as
   test_desktop_shell.py: the only evidence available without a live
   Electron run.

Node suite 845 pass / 25 skip.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions