Main.mjs: Consolidate queues into Read/Write model

The Neo.Main class currently manages three queues: readQueue, updateQueue, and writeQueue. Historically, writeQueue was intended for initial renders and updateQueue for subsequent updates.

Goal: Simplify the architecture to a strict Read/Write model, aligning with standard DOM batching practices (like FastDOM).

Plan:

1. Rename/Consolidate:
   • Rename the current updateQueue to writeQueue.
   • Remove the old writeQueue (and its associated logic).
   • Effectively, all DOM modifications (inserts, updates, moves, removes) will now live in the writeQueue.
2. Refactor Neo.Main:
   • Update renderFrame to process only readQueue and the new writeQueue.
   • Update queueUpdate -> queueWrite.
   • Ensure onRender (if it still exists/is used) and onUpdateVdom both feed into this single writeQueue.
   • Remove mode === 'update' logic.
3. Refactor processQueue:
   • Handle operations based on their content/type if necessary, but primarily just delegate to DeltaUpdates.
   • DeltaUpdates methods (update, insertNode) should be unified or handled generically. Actually, DeltaUpdates.update handles all delta types including insertNode (via action). So we might just need to call DeltaUpdates.update(operation) for everything in the write queue?
   • Critical Check: DeltaUpdates.insertNode expects a specific payload structure. DeltaUpdates.update expects { deltas: [...] }.
   • If we unified autoMount to send deltas (which we did in Manager.mjs), then everything coming from WorkerManager is now a delta update!
   • So processQueue can just call DeltaUpdates.update(operation).

Dependencies:

• This relies on the previous Manager.mjs refactoring where autoMount was transformed into updateVdom with deltas.