edbcfa80ab
Root cause: when multiple wiki:ingest tasks queue up for the same KB, they all hit ErrWikiIngestConcurrent and retry every 15 s. With MaxRetry=10 (150 s window), any batch taking longer than ~2.5 min caused pending tasks to exhaust retries and land in archived. Confirmed via Redis inspection: archived wiki:ingest task had retry=10, retried=10, error="concurrent wiki task active". Two-part fix: 1. Early-exit at lock conflict when pending list is empty. If another batch is active and the pending list is already empty, there is nothing left to process — the concurrent task will handle everything. Return nil (success) immediately instead of burning through retry slots on a guaranteed no-op. Only retry when the pending list still has items, i.e., we have real work to do. 2. Increase MaxRetry 10 → 25 across all four enqueue sites. 25 × 15 s = ~6 min window; accommodates large KB batches and the 60 s orphan-lock expiry with generous headroom. Combined with the early-exit above, redundant tasks now consume 0 retries instead of 10, so the remaining budget is entirely available for genuine concurrency conflicts. No API or schema changes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>