lsm / HyperNeo / 31201015686 / 9

40%

dev: 40%

push

github

feat(github-events): ingest branch_protection_rule webhook [#2327] (#2355)

Row 7 of the merge-blocking spec (#2320): the FIRST repo-scoped GitHub event.
A protection rule applies to a branch name on the whole repository, not to any
one PR, so per spec row 7 it publishes under
`github/{owner}/{repo}/repo/{branch}.branch_protection_{action}` with
`prNumber = 0` (the repo-scoped sentinel) and `prUrl` = the repo URL (not a
`/pull/{n}`). It never blocks a merge directly; it signals that what blocks a
merge may have changed, so a consumer should re-poll `mergeStateStatus`.

- WEBHOOK_EVENTS / GitHubEventKind: register `branch_protection_rule`.
- normalizeGitHubBranchProtectionRule: dispatched early (before the !prNumber
  guard, like check_run), validates on repo + branch only. Carries the rule's
  merge-gating attributes (status-check enforcement + required check-context
  names, required review count, code-owner / linear-history / conversation gates,
  admin-enforced) plus the changed-field names for edits. Branch-name globs are
  sanitized to a safe topic segment (raw pattern kept on the payload).
- mapEventType: `branch_protection_rule` → { resource: 'repo', action: `branch_protection_{action}` }.
- GITHUB_EVENT_RESOURCES (shared `github-subscription-pattern.ts`): add `repo`,
  with a dynamic supported-resources error message.
- Resource-shortcut disambiguation in the shared composer: a
  `thirdIsOwnerRepoResourceShape` helper (bare resource OR dotted
  `resource.action`) gates both shortcut branches so owner/repo/resource forms
  with an owner/repo literally named "repo" (bare or dotted) fall through
  correctly, while still allowing resource-first shorthands whose entity name is
  itself a resource (e.g. a protected branch named "pull_request").
- Essence: projects the merge-gating fields + repo url, omits prNumber for
  repo-scoped events. Feed CASE gets a "Branch protection" title.

Rebased onto dev; the composer work now lives in the shared
`githu... (continued)

2923 of 37651 branches covered (7.76%)

Branch coverage included in aggregate %.

8043 of 46517 relevant lines covered (17.29%)

51.23 hits per line