Fix critical resolution mismatch and memory tracking bugs

[Copilot]

Two serious logic errors causing runtime failures in the distributed path tracer:

1. Resolution Calculation Mismatch

Master and worker nodes calculated pixel array dimensions differently, causing out-of-bounds access:

// master.cpp - WAS: missing +1
this->resolution = math::uvec2(
    (m_worker_info.max_x - m_worker_info.min_x) + 1,  // NOW: matches worker
    (m_worker_info.max_y - m_worker_info.min_y) + 1
);

// worker.cpp - always had +1
this->resolution = fvec2(
    (info.max_x - info.min_x) + 1,
    (info.max_y - info.min_y) + 1
);

Workers generated rays for (max-min+1) × (max-min+1) pixels, but master allocated only (max-min) × (max-min) array → memory corruption during accumulation.

2. Memory Tracking Broken

Preprocessor never incremented current_size, breaking memory-based work distribution:

# WAS: current_size always 0, condition never triggers
if (current_size + prim_size) >= self.memory_per_worker_GB:
    
# NOW: properly tracks accumulated size
current_size += prim_size
if current_size >= self.memory_per_worker_GB:

Workers could exceed memory limits → OOM crashes.

Original prompt

Review my code.

Compile all SERIOUS logic errors.

---

💡 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.