Scan concurrency and restart-state recovery
Scanner capacity now distinguishes running instances from remaining RAM slots, so healthy queued scans no longer remain pending behind an impossible shrinking maximum. The admin view separates running, queued, and paused scanner work. Graceful restart handoffs no longer terminalize active Supabase rows. If resumed work finishes before SaaS observes its active window, the stopped row self-heals only after an exact, backend-bound scanner snapshot proves both completion and a restart-only stop reason.
xalgorix