Auto close stale quests older than 30 days with no pr linked

[ekwe7]

closes #232

Closes #XXX

Description

This PR adds an automated cron job to clean up stale quests, preventing the quest board from filling with inactive or abandoned work.

Changes

• Added GET /api/cron/close-stale-quests secured with CRON_SECRET header validation.
• Automatically marks stale in_progress quests (30+ days without activity) as abandoned.
• Automatically marks unassigned quests older than 30 days with no applicants as expired.
• Emits quest.abandoned and quest.expired protocol events for each state transition.
• Configured the cron job to run daily at 00:00 UTC via vercel.json (or equivalent cron configuration).

Tests

Added unit tests covering:

• Unauthorized requests return 401.
• Stale in_progress quests transition to abandoned.
• Stale unassigned quests transition to expired.
• No quests are updated if they are within the 30-day window.
• Event emission for both quest.abandoned and quest.expired.
• Quest updated 31 days ago is correctly marked as abandoned.

Security

• Cron endpoint is protected using CRON_SECRET.
• No state changes occur without successful authentication.

Files Changed

• app/api/cron/close-stale-quests/route.ts
• vercel.json (or equivalent cron configuration)
• Unit tests for stale quest cleanup

[leocagli]

Great work on the stale quest auto-close implementation! CI passed, but there's a merge conflict with main (likely because another PR just merged while yours was in review). Please rebase onto the latest main and push — it should be straightforward:

git fetch origin
git rebase origin/main
git push --force-with-lease

Once you push, CI will re-run and we can merge right away!

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[leocagli]

PR has a merge conflict with main after recent merges. Please rebase:

git fetch upstream
git rebase upstream/main
git push --force-with-lease

[leocagli]

CI passed but branch has conflicts with main now. Please rebase:

git fetch upstream && git rebase upstream/main && git push --force-with-lease

[leocagli]

Thanks @ekwe7 — the required SonarCloud Code Analysis quality gate is failing on this PR (see the SonarCloud dashboard linked in the checks). Typically it's new-code duplication, insufficient coverage on new code, or code smells/security hotspots. Please open the SonarCloud report for this PR, resolve the flagged issues (add tests for new code, dedupe, address smells), and push — once the gate passes (and the branch is rebased on current main) it can merge.