chore(release): bump version to 1.16.0, major refactor, fix LinkAnalysisPanel click-through

Author: d3mocide

CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.16.0] - 2026-02-26
+
+### Changed
+
+- **Major Codebase Refactoring**: Executed a comprehensive restructuring of both frontend and backend architectures to improve modularity, maintainability, and testing.
+  - **Frontend Core**: Decomposed large monoliths (`MapContainer.jsx`, `Sidebar.jsx`) into focused sub-components. Implemented Facade pattern for global context (`RFContext.jsx`).
+  - **Backend API**: Refactored `server.py` into modular API routers (`analysis.py`, `elevation.py`, `tasks.py`, `optimization.py`).
+  - **Math & Physics Modules**: Split `rfMath.js` into targeted utility files (`fspl.js`, `fresnel.js`, `lora.js`, `bullington.js`, etc.) while maintaining backward compatibility.
+  - **State & Hooks**: Standardized Web Worker communication with `useWorkerState.js` and abstracted tile fetching logic.
+  - **Data Processing**: Consolidated all CSV parsing, importing, and exporting logic into dedicated utilities.
+
+### Fixed
+
+- **Link Analysis UI**: Resolved a click-through bug where adjusting settings in the Link Analysis floating panel would inadvertently interact with the map underneath and place new nodes.
+
 ## [1.15.5] - 2026-02-15
 
 ### Fixed

README.md

@@ -1,4 +1,4 @@
-# meshRF 📡 v1.15.5
+# meshRF 📡 v1.16.0
 
 A professional-grade RF propagation and link analysis tool designed for LoRa Mesh networks (Meshtastic, Reticulum, Sidewinder). Built with **React**, **Leaflet**, and a high-fidelity physics core combining a **Python Geodetic Engine** with **High-Performance WASM Modules**.
 

REFACTORING_REPORT.md

@@ -1,131 +1,41 @@
-# MeshRF v1.15.5 - Stability & Reliability Patch
+# MeshRF v1.16.0 - Major Refactoring & Modularization
 
-**Release Date**: February 15, 2026  
-**Type**: Patch Release  
-**Focus**: Critical bugfixes, memory leak prevention, and WASM binding corrections
+**Release Date**: February 26, 2026  
+**Type**: Minor Release (Architecture Update)  
+**Focus**: Codebase restructuring, modularization, and maintainability improvements.
 
 ---
 
 ## 🎯 Overview
 
-This patch addresses **18 critical stability issues** discovered through systematic code review, including infinite loops, memory leaks, race conditions, silent failures, and a critical WASM binding bug that prevented the ITM propagation model from functioning correctly.
+This release focuses entirely on **structural architecture and technical debt reduction**. The codebase has undergone a major refactor to decompose monolithic files, separate concerns, and establish a cleaner foundation for future feature development. All existing functionality has been preserved and verified against automated test suites.
 
 ---
 
-## 🐛 Critical Fixes
+## 🏗️ Refactoring Highlights
 
-### Backend (Python - 7 fixes)
+### Frontend Architecture
 
-| Issue                            | Impact                              | Fix                                       |
-| -------------------------------- | ----------------------------------- | ----------------------------------------- |
-| **SSE Infinite Loop**            | Open HTTP connections indefinitely  | Added 600-poll max timeout (5 min)        |
-| **Silent Exception Swallowing**  | Errors hidden, debugging impossible | Structured logging with error summaries   |
-| **False-Positive Perfect Links** | Misleading "100% clearance" reports | Evaluation flag prevents 0-point analysis |
-| **ThreadPoolExecutor Leaks**     | Thread count grows unbounded        | `shutdown()` + `__del__()` methods        |
-| **Missing Timeouts**             | Indefinite blocking on tile fetches | 30s timeout with `TimeoutError` handling  |
-| **Unbounded tile_locks**         | Memory exhaustion over time         | OrderedDict LRU cache (1000 limit)        |
-| **Wrong HTTP Status Codes**      | 500 errors for client mistakes      | Differentiated 400 vs 500 responses       |
+- **Component Decomposition**: Massive components like `MapContainer.jsx` and `Sidebar.jsx` have been broken down into specialized layers (`LinkLayerManager`, `CoverageLayerManager`) and sections (`HardwareSection`, `EnvironmentSection`).
+- **State Management**: Implemented Facade pattern for React Context (`RFContext.jsx` wrapping isolated domains).
+- **RF Math Modularization**: Split the monolithic `rfMath.js` into isolated mathematics modules (`fspl.js`, `bullington.js`, `earth.js`, etc.) located in `src/utils/math/`.
+- **Worker & Data Hooks**: Standardized Web Worker interactions via `useWorkerState.js` and extracted map tile fetching to `tileFetcher.js`.
 
-### Frontend (React/JS - 10 fixes)
+### Backend API Structure
 
-| Issue                         | Impact                                         | Fix                                 |
-| ----------------------------- | ---------------------------------------------- | ----------------------------------- |
-| **Stale Message Listeners**   | Duplicate worker handlers, memory leaks        | Moved handler into `useEffect`      |
-| **Stale Closures**            | Infinite re-render loops                       | Restored `configRef` pattern        |
-| **Document Listener Leaks**   | Chrome tab memory growth                       | `cleanupRef` tracking               |
-| **Missing HTTP Error Checks** | Unhandled promise rejections                   | `response.ok` validation            |
-| **Silent WASM Failures**      | Tools silently break                           | `wasmError` state + user feedback   |
-| **Scan Double-Submit**        | Duplicate Celery tasks                         | `isScanning` guard                  |
-| **Missing Imports**           | Runtime ReferenceErrors                        | Added `useRef`, `useEffect`         |
-| **Infinite Loop (Post-Fix)**  | Max update depth exceeded                      | Removed `runAnalysis` from deps     |
-| **Model Selection**           | Changing propagation model doesn't recalculate | Added `propagationSettings` to deps |
-
-### WASM/C++ (1 fix)
-
-| Issue                          | Impact                                       | Fix                                                       |
-| ------------------------------ | -------------------------------------------- | --------------------------------------------------------- |
-| **LinkParameters Constructor** | "Module.LinkParameters is not a constructor" | Changed `value_object` → `class_` with `.constructor<>()` |
-
----
-
-## 📦 Deployment
-
-### Updated Files
-
-- **Backend**: `server.py`, `rf_physics.py`, `core/algorithms.py`, `tile_manager.py`
-- **Frontend**: `useViewshedTool.js`, `LinkLayer.jsx`, `LinkAnalysisPanel.jsx`, `rfService.js`, `useRFCoverageTool.js`, `useSimulationStore.js`
-- **WASM**: `libmeshrf/src/bindings.cpp`, `meshrf.wasm` (109KB), `meshrf.js` (48KB)
-
-### Verification
-
-- ✅ Frontend build successful
-- ✅ Python syntax validated
-- ✅ WASM module compiled (100%)
-- ✅ Runtime errors resolved
-
----
-
-## 🚀 Upgrade Instructions
-
-### Development
-
-```bash
-# Frontend (uses Vite HMR - no restart needed)
-# Code changes already live via volume mount
-
-# Backend - restart to reload Python modules
-docker restart rf_engine_dev
-
-# Hard refresh browser to load new WASM
-Ctrl + Shift + R (Windows/Linux)
-Cmd + Shift + R (Mac)
-```
-
-### Production
-
-```bash
-# Pull latest code
-git pull origin main
-
-# Rebuild containers
-docker-compose build
-
-# Restart stack
-docker-compose up -d
-```
-
----
-
-## 🔍 Testing Recommendations
-
-1. **Link Analysis**: Test ITM (Longley-Rice) propagation model - should no longer throw constructor errors
-2. **Long-Running Scans**: Verify SSE endpoints timeout gracefully after 5 minutes
-3. **Memory Monitoring**: Check thread count and Redis tile cache remain bounded
-4. **Error Visibility**: Confirm viewshed errors appear in logs instead of being silently swallowed
-5. **Multi-Click Protection**: Spam-click "Start Scan" button - should only run once
-
----
-
-## 📊 Impact Summary
-
-| Category            | Fixes | Severity    |
-| ------------------- | ----- | ----------- |
-| **Infinite Loops**  | 1     | 🔴 Critical |
-| **Memory Leaks**    | 3     | 🔴 Critical |
-| **Silent Failures** | 4     | 🟠 High     |
-| **Race Conditions** | 2     | 🟠 High     |
-| **Error Handling**  | 4     | 🟡 Medium   |
-| **Import Errors**   | 3     | 🟡 Medium   |
-
-**Total**: 18 issues resolved
+- **API Routing**: `server.py` has been decomposed into dedicated FastAPI routers (`routers/analysis.py`, `routers/elevation.py`, etc.).
+- **Tile Manager Extraction**: Separated `tile_manager.py` logic into `cache_layer.py`, `elevation_client.py`, and `grid_processor.py`.
 
 ---
 
-## 🙏 Acknowledgments
+## 📊 Impact & Stability
 
-All issues identified through systematic code review and production debugging. Special attention given to resource management (threads, listeners, locks) and React hook dependency management.
+- **Components Extracted/Created**: 25+
+- **Lines of Code Relocated**: ~4,000+
+- **Test Status**: All backend (`pytest`) and frontend (`vitest`) test suites are passing.
+- **Docker Containers**: Rebuilt and stable.
 
 ---
 
 **Full Changelog**: [CHANGELOG.md](CHANGELOG.md)  
-**Previous Release**: [v1.15.4](https://github.com/d3mocide/MeshRF/releases/tag/v1.15.4)
+**Previous Release**: [v1.15.5](https://github.com/d3mocide/MeshRF/releases/tag/v1.15.5)

RELEASE_NOTES.md

@@ -6,7 +6,7 @@ services:
     container_name: meshrf_dev
     command: npm run dev -- --host
     ports:
-      - "5173:5173" # Vite Dev Port
+      - "3100:5173" # Vite Dev Port
     volumes:
       - .:/app
       - /app/node_modules

docker-compose.dev.yml

@@ -1,7 +1,7 @@
 {
   "name": "meshrf",
   "private": true,
-  "version": "1.15.5",
+  "version": "1.16.0",
   "type": "module",
   "scripts": {
     "dev": "vite",