0eca98103e
CI / lint (push) Successful in 20s
CI / quality (push) Successful in 32s
CI / push-validation (push) Successful in 21s
CI / helm (push) Successful in 24s
CI / typecheck (push) Successful in 54s
CI / security (push) Successful in 59s
CI / benchmark-regression (push) Has been skipped
CI / build (push) Successful in 47s
CI / e2e_tests (push) Successful in 3m8s
CI / integration_tests (push) Successful in 4m1s
CI / unit_tests (push) Successful in 4m58s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 10m16s
CI / status-check (push) Successful in 2s
CI / benchmark-publish (push) Has been cancelled
- Created new async-agent-manager to handle all async operations centrally - Fixed permission issues where agents couldn't execute curl commands - Updated all agents to use async-agent-manager instead of direct curl - Only async-agent-manager has curl permissions to localhost:4096 - All other agents use it via Task tool with proper permissions - Tested and verified all curl commands work correctly - Added comprehensive operations: start, status, messages, search, cleanup, health monitoring - Improved error handling with structured JSON responses - Enhanced security with proper input escaping This fixes the blocking issue where supervisors couldn't launch workers due to environment restrictions on curl commands. Now all async operations go through a single, well-tested agent with proper permissions.