fix(file-search): bound dispatcher claims and skip locked rows

[icecrasher321]

Summary

• Bound dispatcher claim probes to each workspace's available slots and skip locked pending rows, avoiding backlog-wide ranking and waits on busy candidates.
• Preserve current-file eligibility and global/workspace concurrency caps. Add PostgreSQL coverage for locked rows, concurrent dispatch, a large backlog, and capacity limits.

Type of Change

• Bug fix

Testing

• 10 focused unit tests and 6 PostgreSQL 17 integration tests pass. The new locked-candidate regression fails against the previous query and passes with this change.
• App type-check, repository lint, all 46 repository audits (including API validation), block registry, and docs manifest checks pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 17, 2026 8:09pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no actionable correctness, security, or repository-rule violations were identified.

Summary

This PR replaces backlog-wide candidate ranking with bounded, per-workspace PostgreSQL probes that lock eligible rows using SKIP LOCKED.

• Limits each workspace probe to its currently available outstanding slots.
• Preserves current-file eligibility and global dispatch capacity.
• Adds PostgreSQL integration coverage for locked candidates, concurrent preparation, large backlogs, and capacity limits.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Acquire dispatcher advisory lock] --> B[Count global active claims]
    B --> C[Select queued workspaces]
    C --> D[Count active claims per workspace]
    D --> E[Probe only available candidate slots]
    E --> F[Lock candidates with SKIP LOCKED]
    F --> G[Apply remaining global-capacity limit]
    G --> H[Set dispatched_at and return payloads]
    H --> I{Eligible undispatched rows remain?}
    I -->|Yes| J[Retain queue row and update dispatch time]
    I -->|No| K[Delete queue row]

Loading

_{Reviews (1) · Last reviewed commit: "fix(file-search): bound dispatcher claim..."}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}