The 1k-line `src/webhook.ts` mixed signature verification, event
dispatch, the CI state machine, and per-event handlers. Decomposed
along the three real concerns plus a reusable Forgejo API client:

- `src/webhook.ts` (HTTP only) — signature, body parse, event switch
- `src/webhook-handlers.ts` — one exported handler per event type
- `src/webhook-ci.ts` — fix-ci dedup, aggregate-state polling, log
  prefetch, mergeability precheck, request-reviewer-on-green
- `src/webhook-config.ts` — frozen singleton + `loadWebhookConfig`
- `src/forgejo-api.ts` — every Forgejo HTTP call goes through helpers
  here with shared auth header and shared 5s `AbortSignal.timeout`

Seams enforced: `webhook.ts` does not import `forgejo-api.ts`;
handlers go through `webhook-ci.ts` for any state-machine work; no
`export * from`. Existing webhook tests split into `webhook.test.ts`
(routing), `webhook-handlers.test.ts` (per-handler), and
`webhook-ci.test.ts` (state machine). 125 tests pass.

Closes #34

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

@@ -0,0 +37,4 @@
+
+export function markFixCiDispatched(repo: string, sha: string): void {
+	const key = `${repo}@${sha}`;
+	_fixCiDispatched.set(key, Date.now());

@@ -0,0 +265,4 @@
+// reviewer's nose. CI is now the gate: push → status / action_run event →
+// either fix-ci (red) or request-reviewer (green). This handler only logs.
+export function handlePullRequestSynchronize(repo: string, pr: { number: number; user: { login: string } }): void {
+	console.log(`[webhook] synchronize on ${repo}#${pr.number} by ${pr.user.login} — awaiting CI`);

@@ -0,0 +307,4 @@
+
+	const aggregate = await fetchAggregateState(repo, status.sha, token);
+	if (!aggregate) return null;
+