Yogesh Ojha a700bbed03 feat(scans): concurrent scan limit with a launch-order queue ...

Launches past the limit stay pending and start in launch order when a slot
frees, so each running scan gets full speed and memory stays bounded.

- run_scan admits a pending scan under an advisory lock: running plus waiting
  scans ahead of it must be under the limit
- finalize, cancel, pause, delete and a limit change start the next scans;
  the reaper re-sends only scans whose turn has come
- automatic limit: live worker-scans stage slots over the widest step,
  so --scale raises it; Settings sets a fixed limit from 1 to 50
- watch probes skip the queue, resume is never held
- queued scans show how many are ahead

2026-09-25 05:38:23 +05:30

..

api

feat(whats-new): activity lanes, expandable events and whole-run counts

2026-09-24 21:51:06 +05:30

channels

fix(remote-control): pairing race, listener pool, ceiling grants and copy

2026-09-24 13:27:27 +05:30

grammar

feat(scans): concurrent scan limit with a launch-order queue

2026-09-25 05:38:23 +05:30

hygiene

feat(hygiene): internal addresses a response hands out

2026-09-24 23:17:45 +05:30

pipeline

feat(scans): concurrent scan limit with a launch-order queue

2026-09-25 05:38:23 +05:30

posture

fix(posture): mail rows judged on sender checks only, ranked MX sweep

2026-09-15 12:38:47 +05:30

conftest.py

chore: production-readiness review across the tree

2026-09-13 18:03:29 +05:30