Clarify repository scan queue flow

[hudsonaikins]

Summary

• rename the dashboard action from queue scan to add repository so the first click matches what the UI does
• show the local runner command before submit because Cloudflare can only queue the job, not read the user's filesystem
• hide completed/failed jobs from the open-job strip so stale jobs do not look active
• document the hosted queue plus local runner flow in dashboard and docs

Root cause

The dashboard button looked like it would execute a scan immediately. In reality it posts a job to Neon through the Worker, and the local CLI runner must claim and process that job.

Validation

• bun run lint
• bun run build
• bun run test:e2e
• cd docs-site && bun run build
• Playwright full UI submit against hosted Worker API
• local runner processed queued UI job and Worker API reported completed

Smoke evidence

• UI queued job: job_70b79a70-3a34-4d2d-89bb-de2b2b00bf67
• Runner completed it with agent-permit runner --once --deep-agent off
• Hosted snapshot returned queuedJobs: 0 after completion