Phase 3 / Task 1: Extract chunk queue and upload coordinator

[MichaelFisher1997]

Goal

Split the chunk generation, meshing, and upload orchestration out of WorldStreamer.

Scope

• src/world/world_streamer.zig

Work

• Create a focused coordinator for generation/meshing/upload progression
• Move processGenJob, processMeshJob, and processUploads into it
• Preserve the current chunk state machine and worker-pool behavior

Acceptance criteria

• Queue management is separated from LOD and GPU concerns
• Chunk generation still reaches renderable through the same states

Parallel-safe

Yes

[github-actions]

Classification: Refactoring task (Feature Request)

Analysis:

This is a well-scoped extraction task. The current WorldStreamer mixes three concerns:

1. Queue orchestration (what this task extracts): gen_queue, mesh_queue, upload_queue, processGenJob, processMeshJob, processUploads, state machine transitions in updateStreaming

2. LOD/GPU concerns (stays in WorldStreamer): lod_manager, gpu_block_buffer, gpu_mesher

3. World lifecycle (stays in WorldStreamer): processUnloads, checkAutoSave, player movement tracking

Suggested extraction (src/world/chunk_coordinator.zig):

ChunkCoordinator
├── gen_queue: *JobQueue
├── mesh_queue: *JobQueue  
├── upload_queue: RingBuffer(ChunkKey)
├── processGenJob()
├── processMeshJob()
├── processUploads()
└── State machine logic from updateStreaming()

Key interfaces to preserve:

• WorldStreamer passes ChunkStorage, Generator, TextureAtlas, PlayerMovement, render_distance to coordinator
• Coordinator notifies WorldStreamer when chunks reach mesh_ready state
• WorldStreamer handles LOD/GPU decisions and calls back to coordinator for uploads

Verification: The chunk state machine (missing → generating → generated → meshing → mesh_ready → uploading → renderable) must remain intact per acceptance criteria.

This is appropriately scoped—one cohesive extraction with clear boundaries. No sub-issues needed.

opencode session  |  github run