✨ [feat] Refactor chart rendering and improve IPC handling

 - 🔧 [fix] Fixed bug with chart conversion between km/meter/feet/miles
 - 🔧 [build] Introduced `createManagedChart` utility for consistent chart management across multiple chart rendering functions.
 - 🛠️ [fix] Updated `renderLapZoneChart`, `renderPowerVsHeartRateChart`, `renderSpeedVsDistanceChart`, and `renderZoneChartNew` to utilize `createManagedChart` for better chart instance management.
 - 🔧 [build] Enhanced `renderPowerVsHeartRateChart` and `renderSpeedVsDistanceChart` to use `chartSettingsManager` for field visibility instead of localStorage.
 - 🎨 [style] Improved code readability by restructuring conditional statements and ensuring consistent formatting.
 - 🔧 [build] Changed IPC channel for FIT file decoding from `"decode-fit-file"` to `"fit:decode"` for better clarity and consistency.
 - 🎨 [style] Updated debug logging in `debugSensorInfo` to use a more appropriate emoji for formatted product output.
 - 🎨 [style] Changed the icon for the export ZIP functionality in settings to a folder emoji for better visual representation.

Signed-off-by: Nick2bad4u <[email protected]>

Author: Nick2bad4u

docs/FIT_PARSER_MIGRATION_GUIDE.md

@@ -6,6 +6,13 @@ The `fitParser.js` module has been successfully migrated to integrate with the F
 
 ## Key Changes
 
+> **Canonical IPC Channels**
+>
+> - `fit:decode` – primary channel for decoding FIT files from the renderer.
+> - `fit:parse` – alternative channel used by some internal flows/tests.
+>
+> The legacy `decode-fit-file` channel has been fully replaced by `fit:decode` in the integration helpers. Any new code should use `fit:decode` / `fit:parse` only.
+
 ### 1. State Management Integration
 
 The FIT parser now integrates with:
@@ -100,45 +107,37 @@ import { initializeFitParserIntegration } from "./utils/fitParserIntegration.js"
 await initializeFitParserIntegration();
 ```
 
-### Step 2: Set Up IPC Handlers (Main Process)
-
-```javascript
-import { setupFitParserIPC } from "./utils/fitParserIntegration.js";
-import { ipcMain } from "electron";
+### Step 2: IPC Handlers (Main Process)
 
-// Set up IPC handlers for FIT parser operations
-setupFitParserIPC(ipcMain);
-```
-
-### Step 3: Set Up Preload Script
+In the current architecture, `electron-app/main/ipc/setupIPCHandlers.js` is responsible for wiring the canonical FIT IPC channels:
 
 ```javascript
-import { setupFitParserPreload } from "./utils/fitParserIntegration.js";
-import { contextBridge, ipcRenderer } from "electron";
+registerIpcHandle("fit:parse", async (_event, arrayBuffer) => {
+    // ... calls fitParser.decodeFitFile(buffer)
+});
 
-// Expose FIT parser functions to renderer
-setupFitParserPreload(contextBridge, ipcRenderer);
+registerIpcHandle("fit:decode", async (_event, arrayBuffer) => {
+    // ... calls fitParser.decodeFitFile(buffer)
+});
 ```
 
-### Step 4: Use in Renderer Process
+The optional `setupFitParserIPC(ipcMain)` helper in `utils/files/import/fitParserIntegration.js` also uses `fit:decode` to provide an advanced, state-aware decoding surface for specialized embedding scenarios and tests.
 
-```javascript
-// Decode a FIT file with progress tracking
-const result = await window.fitParser.decodeFitFile(fileBuffer);
-
-// Update decoder options with validation
-const updateResult = await window.fitParser.updateDecoderOptions({
- applyScaleAndOffset: false,
- includeUnknownData: true,
-});
+### Step 3: Preload Script
 
-// Get current options
-const options = await window.fitParser.getDecoderOptions();
+The canonical renderer API is exposed via `preload.js` through the `electronAPI` bridge, not `window.fitParser`:
 
-// Reset to defaults
-const resetResult = await window.fitParser.resetDecoderOptions();
+```javascript
+// In preload.js
+const electronAPI = {
+    decodeFitFile: createSafeInvokeHandler(CONSTANTS.CHANNELS.FIT_DECODE, "decodeFitFile"),
+    parseFitFile: createSafeInvokeHandler(CONSTANTS.CHANNELS.FIT_PARSE, "parseFitFile"),
+    // ...
+};
 ```
 
+The `setupFitParserPreload(contextBridge, ipcRenderer)` helper remains available for legacy or embedded use cases and now invokes `fit:decode` under the hood instead of `decode-fit-file`.
+
 ## New API Functions
 
 ### Core Functions (Node.js/Main Process)
@@ -167,7 +166,7 @@ const defaults = fitParser.getDefaultDecoderOptions();
 const schema = fitParser.DECODER_OPTIONS_SCHEMA;
 ```
 
-### Integration Functions (ES6 Modules)
+### Integration Functions (ES6 Modules / Advanced)
 
 ```javascript
 import {

electron-app/eslint.config.mjs

@@ -22,7 +22,7 @@ export default defineConfig([
             "./.temp*/**",
             "node_modules/**",
             "dist/**",
-            "**/*.d.ts"
+            "**/*.d.ts",
         ],
     },
     {