Skip to main content
← Back to list
01Issue
BugShippedSwamp CLI
Assigneesstack72

Relationships

#728 serve: webhook scheme not surfaced in startup event, health endpoint, or log line

Opened by keeb · 6/21/2026· Shipped 6/21/2026

The webhook verifier scheme (ep.verifier.scheme) is parsed and stored on each WebhookEndpoint, but it is never surfaced in swamp serve output. This makes it impossible to confirm via script or log which scheme was actually applied — relevant because a mis-typed scheme keyword silently falls back to the legacy parser and uses github. Three spots in src/cli/commands/serve.ts, all fixable by adding scheme: ep.verifier.scheme:

  1. webhook_registered JSON startup event (~line 449). Emits { kind, route, workflow } — no scheme. A user capturing --json to verify their config can't confirm the parsed scheme.

  2. Health endpoint JSON (~line 542). GET /health returns { route, workflow } per webhook. A healthcheck script that wants to assert "this endpoint uses the stripe scheme" has nothing to compare against.

  3. Log-mode registration line (same file). Webhook registered: {route} → {workflow} doesn't mention the scheme, so a non-default scheme (e.g. stripe) leaves no log trace confirming it was applied. Lower priority since the flag is visible in the startup invocation, but it helps when debugging a silent fallback to github.

Severity: Low — observability gap, no functional impact. All three are effectively one-liners.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

6/21/2026, 11:18:47 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack726/21/2026, 10:41:55 PM

Sign in to post a ripple.