Fix heatmap not updating on rapid layout parameter changes

[Copilot]

Heatmap failed to update when users changed layout parameters rapidly. The 3D worker's results were incorrectly discarded because cachedCalculationParams3D was invalidated by layoutGenerated events before the worker completed.

Root Cause

Race condition in result validation:

1. User changes layout → layoutGenerated fires → cachedCalculationParams3D = null
2. Worker completes calculation for the (now current) layout
3. Validation checks cachedCalculationParams3D?.layoutHash → undefined
4. Result discarded despite being valid for current layout

Changes

• Worker returns layoutHash: beam_worker_3d.js now includes the layoutHash it calculated for in the result message
• Validate against current layout: Handler compares worker's layoutHash against live getLayoutHash(getAllAntennas()) instead of potentially-invalidated cache params
• Fallback for compatibility: If worker doesn't return hash, falls back to cachedCalculationParams3D validation

// Before: checked against invalidated cache
if (cachedCalculationParams3D?.layoutHash === currentLayoutHash) { ... }

// After: validate worker result directly against current state
const workerLayoutHash = e.data.layoutHash;
if (workerLayoutHash && workerLayoutHash === currentLayoutHash) {
    cachedCalculationResult3D = e.data.data;
    cachedCalculationParams3D = { layoutHash: currentLayoutHash };
    refreshVisualization();
}

Debug logging added throughout the visualization pipeline to trace future issues.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.