high-concurrency-runtime

Maintain the per-upstream CircuitBreaker state machine. Use for concurrent transitions, consecutive outcome semantics, HalfOpen probe budgets, timeout recovery, and config validation.

Maintain gateway token buckets and bounded identity rate limiting. Use for rate math, cardinality caps, eviction, concurrency, and hot-path lock reviews.

Maintain vexo/gateway orchestration and cross-subsystem policy. Use for GatewayServer, routing admission, lifecycle, resilience integration, and gateway boundary reviews.

Maintain vexo/net reactor, EventLoop, Channel, TCP, poller, timerfd, and backend code. Use for net-layer patches, reviews, lifetime fixes, and threading changes.

Maintain vexo/ds intrusive containers, heaps, trees, hash tables, bloom filters, and hash functions. Use for data-structure invariants and zero-ownership container patches.

Maintain active upstream health checking. Use for HealthChecker probes, thresholds, late callbacks, Stop semantics, overlap prevention, and health-state ownership.

Maintain gateway load-balancing strategies and factory selection. Use for peer eligibility, weighted algorithms, hash rings, Maglev tables, concurrency, and hot-path cost.

Maintain proxy request forwarding and GatewayServer proxy orchestration. Use for UpstreamRequest state, retries, deadlines, response framing, connection pooling, budgets, and backpressure.

Maintain Upstream, UpstreamPeer, UpstreamRegistry, and per-loop upstream connection pools. Use for topology publication, peer state ownership, request accounting, and pool lifetime.

Maintain vexo/memory arenas, fixed block pools, object pools, and PMR adapters. Use for allocator ownership, alignment, reset, cleanup, and pool lifetime patches.

Maintain vexo/time Timestamp, Timer, TimerId, and timer indexes. Use for clock semantics, timer ordering, cancellation handles, and time-layer dependency reviews.