Viktor Barzin 66104a32ab parallel execution: replace single-flight lock with bounded semaphore + per-job workspace ... Multiple agent calls now run concurrently, each in its own isolated git checkout (local clone of the warm base, hardlinked objects, git-crypt re-unlocked), so concurrent jobs never share a working tree. - execution_lock (asyncio.Lock) -> execution_semaphore (default MAX_CONCURRENCY=10); excess calls queue FIFO instead of 409/503. MAX_QUEUE_DEPTH safety valve. - /execute never returns 409; jobs go queued -> running. Timeout covers execution only, not queue wait. - /v1/chat/completions queues for a slot instead of 503-busy. - /health: busy = at-capacity, plus active/queued/capacity fields. - per-job workspace prepare/cleanup under a short git lock; the agent run holds none. - in-memory job registry evicted past JOB_TTL_SECONDS. Design: docs/2026-06-02-parallel-execution-design.md Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-02 20:57:41 +00:00
..
__init__.py	Initial extraction from monorepo	2026-05-07 17:07:12 +00:00
conftest.py	parallel execution: replace single-flight lock with bounded semaphore + per-job workspace	2026-06-02 20:57:41 +00:00
test_concurrency.py	parallel execution: replace single-flight lock with bounded semaphore + per-job workspace	2026-06-02 20:57:41 +00:00
test_main.py	parallel execution: replace single-flight lock with bounded semaphore + per-job workspace	2026-06-02 20:57:41 +00:00
test_openai_compat.py	parallel execution: replace single-flight lock with bounded semaphore + per-job workspace	2026-06-02 20:57:41 +00:00