fix: map cancelled check runs to failure, preserve raw conclusion

[mlahargou]

Summary

• Cancelled GitHub Actions runs (manual cancel or timeout) now map to failure instead of error, so they block merge like real failures
• The description field in commit_statuses now stores the raw GitHub conclusion (cancelled, failure, timed_out, etc.) instead of the mapped state, so Grafana dashboards can differentiate between true failures and cancelled runs
• Updated both the webhook path (githubHooks.js) and the refresh path (git-manager.js) for consistency

Context

GitHub Actions reports skipped/cancelled jobs with conclusion cancelled, which was falling into the default case in mapCheckToStatus() and being recorded as state='error'. This polluted CI dashboards with ~800 false error entries per week.

The description column is only used for display text in the Pulldasher UI popover — no code branches on its value. Storing the raw conclusion is arguably better UX since it tells users why a check failed.

Test plan

• Deploy and verify cancelled runs show as failure (not error) in commit_statuses
• Verify Pulldasher UI shows raw conclusion text in the status popover
• Verify skipped runs still map to success

🤖 Generated with Claude Code

[mlahargou]

QA 📱

Before:

After:

[erinemay]

cr 👍 makes sense to me.

• description now stores the actual gh output instead of a copy of state
• cancelled now returns failure instead of falling through to error

deploy_block 🌵
Did you mean to add a timed_out case mapped to failure too? Hard to tell from the description whether you want timeout mapped to failure vs error, or if the dashboards will/can use the new description value of the test result.

[mlahargou]

Good call. QA 📱 CR 📱 carry-over

Ref: https://docs.github.com/en/graphql/reference/checks#enum-checkconclusionstate