3148c9154cf4d52b2fa2f824fec8c3f5dac4c0b4
Salvage ships flew to their assigned Salvage Bay with full cargo and waited there forever without delivering. A Salvage Bay's outputBuffer.capacity was never initialized (stayed 0), so deliverScrapToSalvageBay always rejected the hand-over, cargo never drained, and DeliverScrap stayed the winning behavior indefinitely. Give the bay a config-driven output-buffer capacity: - BuildingDef gains optional outputBufferCapacity; ConfigLoader parses the new output_buffer_capacity key. - salvage_bay in both buildings.toml files sets it to 20. - initSalvageBayBuffer applies it on both operational-creation paths (construction completion and placeImmediate). - REQ-BLD-SALVAGE-BAY documents the config-sized buffer and hand-over. - Tests: config parse assertion and end-to-end delivery hand-over. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VGNNLeFWhVzvxkK9qVXP2K
Description
No description provided
Languages
C++
96%
CMake
2.2%
Python
1.2%
C
0.6%