Setting it only rebound main.py's own module-level WEB_POOL_SIZE -
runtime.py and maintenance.py each imported their own copy at process
start (from config import WEB_POOL_SIZE), so the actual pool-sizing
logic in ensure_web_pool()/cleanup_loop never saw the change and kept
targeting the .env value. The UI control only ever changed what the
admin page displayed back to itself, plus a couple of >0/<=0 branch
checks in main.py - never the real pool. Removed the input, button,
JS handler and the dead endpoint rather than wiring the three-module
sync it would take to make it actually work.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ruslan
f4fdeb12c1