#13 · Add !bounty command to surface open feature bounties in Signal

Context

The community-facing bot should surface open bounties so contributors can claim them without leaving Signal. Today, bounties live only on score.irregulars.io and GitLab — adding a !bounty command closes that loop and brings the bot ↔ scoreboard parity in line with !jobs, !events, !tasks.

Acceptance criteria

• [ ] !bounty (no args) lists up to 10 unclaimed bounties with title, app, tier, points
• [ ] !bounty <iid> shows full description and acceptance criteria for one issue
• [ ] !bounty mine shows bounties assigned to the calling user (matched by email)
• [ ] Output uses Signal's text formatting (bold for title, monospace for app name)
• [ ] Caches GitLab API response in Redis for 5 min to avoid rate-limit churn

Technical hints

• !bounty already exists as a link-only stub: handleBounty in selfhost/messaging-apps/signal-messenger/src/src/bot/command-handler.ts (dispatched from the switch as !bounty/!bounties). Expand it to list inline; handleJobSearch in the same file is the closest listing pattern.
• For the data source, wrap GET on score.irregulars.io if a JSON endpoint is added there, otherwise direct GitLab API. Put the client in packages/shared-utils/src/bot-utils/ (alongside career-board-client.ts) so both bots can share it.
• Add an isBountyConfigured() guard in packages/shared-utils/src/bot-utils/ following the same pattern as isCareerBoardConfigured()

Related

• Bounty page on scoreboard: https://score.irregulars.io/bounties
• GitLab issues API: https://docs.gitlab.com/ee/api/issues.html

--- *Submit a merge request that says Closes #<this issue iid> in the description. On merge to main, the GitLab webhook will auto-award your bounty + the standard merge_pr (40 pts) to your scoreboard account. Email on commit must match your Authentik email.*