Problem
When the app launches before the server is available, it shows "Connecting to Ankurah..." but doesn't automatically update the UI when the connection succeeds.
The websocket client does retry and eventually connects, but the nodeReady state in App.tsx is set once during initAnkurah() and doesn't reflect actual connection status changes.
Current behavior
- Start app (server not running) → Shows "Connecting to Ankurah..."
- Start server → Websocket connects in background
- UI still shows "Connecting to Ankurah..." (stuck)
- User must reload app to see connected state
Expected behavior
UI should reactively update when connection status changes - either showing "Connected" when websocket connects, or providing a retry button.
Technical notes
nodeReady in App.tsx is a one-time initialization flag, not reactive to connection state- The websocket client in Rust does retry automatically
- Need to expose connection status as a signal/observable that React can subscribe to
Problem
When the app launches before the server is available, it shows "Connecting to Ankurah..." but doesn't automatically update the UI when the connection succeeds.
The websocket client does retry and eventually connects, but the
nodeReadystate inApp.tsxis set once duringinitAnkurah()and doesn't reflect actual connection status changes.Current behavior
Expected behavior
UI should reactively update when connection status changes - either showing "Connected" when websocket connects, or providing a retry button.
Technical notes
nodeReadyinApp.tsxis a one-time initialization flag, not reactive to connection state