Merge flood & tsunami scenarios into main

[lolismek]

Summary

• Integrates the flood branch's flood and tsunami disaster scenarios into main's agent-based scenario architecture
• Resolves merge conflicts in index.html, index.ts, and src/main.ts by adapting flood/tsunami to main's existing patterns
• Flood and tsunami now appear as selectable scenario cards alongside fire, tornado, and earthquake
• Adds a dynamic disaster control panel with real-time parameter sliders for both new scenarios
• Preserves main's VLM agent system, replay recording, and port-fallback server logic

Conflict resolution approach

• index.html: Kept main's full UI (scenario panel, fire config, agent HUD, tornado/earthquake panels). Added a generic disaster-control panel for flood/tsunami.
• index.ts: Kept main's VLM/WebSocket agent system. Integrated flood's port-fallback logic so the server tries multiple ports.
• src/main.ts: Kept main's scenario registry + agent system. Added flood/tsunami as available scenarios using the DisasterController interface from disasters/factory.ts.

New files (from flood branch)

• disasters/types.ts — DisasterController interface, DisasterControl union type
• disasters/factory.ts — Factory pattern for creating flood/tsunami instances
• disasters/flood/ — 8 files: shallow water solver, water surface rendering, environment effects
• disasters/tsunami/ — 10 files: wave field, destruction system, splash/debris physics, sediment overlay

Test plan

• bun build ./src/main.ts compiles without errors
• bun build ./index.ts compiles without errors
• Load a location, verify all 5 scenario cards appear (fire, tornado, earthquake, flood, tsunami)
• Launch flood scenario — verify water surface renders and controls panel works
• Launch tsunami scenario — verify wave propagation and destruction system
• Verify existing scenarios (fire, tornado, earthquake) still function correctly

🤖 Generated with Claude Code