fix: world-map.json fabricated data, broken Solaris travel fallback, missing health API

[gnummers]

Description

Three related problems in the Solaris navigation layer:

1. world-map.json contains fabricated data. The 183-room navigation graph included 151 synthetic rooms (IDs in the 2000-series) with hand-invented descriptions, street names, and exit connections that were never verified against the retail server or client assets. Room descriptions on the 26 named locations (IDs 146–171) were also unverified.

2. Solaris travel fallback broken. When world-map.json is absent or malformed, world-data.ts did not fall back correctly — the server would emit a warning but then proceed with a broken provisional topology that caused travel commands to misbehave.

3. No liveness endpoint. There is no HTTP endpoint for external tooling (Godot client, launcher, health monitors) to confirm the server is running without needing to speak the full ARIES protocol.

Steps to Reproduce

Bug 1: Open world-map.json and inspect any room with ID > 1000. Cross-reference its description and exit targets against SOLARIS.MAP or retail screenshots — none match.

Bug 2:

1. Rename or remove world-map.json.
2. Start the server (npm run dev).
3. Connect a client and issue a travel command.
4. Observe incorrect or broken room placement.

Bug 3:

1. Start the server.
2. curl http://127.0.0.1:3002/health
3. Observe connection refused.

Expected Behavior

• world-map.json should contain only rooms and data verified from SOLARIS.MAP or retail in-room screenshots.
• The server should start and serve travel commands correctly even when world-map.json is absent, using a minimal provisional topology.
• GET /health on port 3002 should return { ok: true, version, name } so external tooling can confirm liveness without ARIES.

Actual Behavior

• world-map.json had 183 rooms; 151 were synthetic with fabricated IDs, names, descriptions, and exit links.
• Missing world-map.json caused the provisional topology to be used incorrectly, breaking Solaris travel.
• No health endpoint existed; port 3002 was not bound at all.

Environment

• Node.js version: v20.x (engine requirement >=20.6.0)
• OS: Windows_NT
• MPBT client patch level: v1.29 retail client

Priority

Medium — server starts and combat works; Solaris navigation data is wrong and the travel fallback is unreliable.

Additional Context

• SOLARIS.MAP binary confirmed layout: 32 rooms (IDs 1–6 sector meta-rooms, 146–171 named locations), point coordinates (x==x_dup, y==y_dup), district index in flags & 0xFF.
• Retail in-room screenshots (26 location folders, ~80 images) were analysed to extract verified room names, descriptions, and exit connections.
• Reconstructed world-map.json: 94 rooms total — 32 from SOLARIS.MAP, 27 screenshot sub-rooms, 35 stubs from exit-text references. Every room carries _source metadata.