fix(adapters): validate and coerce raw bounty status to known BountyStatus (#279)

[ghzhost]

Summary

Fixes #279.

src/lib/adapters.ts#adaptBounty mapped raw.status directly without runtime validation against known BountyStatus values. If the backend sent an unrecognized, future, or invalid status enum value, it would flow directly into StatusBadge (producing unstyled badges) and IssueActions (producing zero action buttons).

Changes

• Defined VALID_BOUNTY_STATUSES containing all 8 valid BountyStatus values.
• Introduced coerceBountyStatus(status: unknown, fallback: BountyStatus = "open"): BountyStatus to validate incoming values at runtime and fall back safely to "open" on unrecognized or missing status strings.
• Updated adaptBounty to pass raw.status through coerceBountyStatus.
• Added unit tests in src/lib/adapters.test.ts verifying that valid statuses are preserved and unrecognized/malformed status strings are coerced safely to "open".

[vercel]

Someone is attempting to deploy a commit to the chonilius' projects Team on Vercel.

A member of the Team first needs to authorize it.