* fix(nuxt): pre-bundle the CommonJS deps of the markdown stack
`debug` and `extend` are imported by micromark and unified through
@elysola/ui. Served unbundled by the dev server they have no default
export, so the console page failed with a 500 in `nuxt dev`.
* docs(deployment): list the fragments and feishu link migrations
The manual `d1 execute` fallback stopped at 0008, and AGENTS.md named
0001..0010 although 0011 already exists.
* feat(storage): persist the per-group route order
Routes used to load in id order, so the order saved from the console
was lost on the next read. Migration 0012 adds `d1_routes.position`:
saving writes each route's index within its own group (saving one group
never shifts another), and routes load by `group_id, position, id`.
A database without the column keeps working: only a "no such column" /
"has no column named" error falls back to the legacy statements, and
nothing is cached, so a later migration is picked up on the next call.
* feat(console): add in-app destructive-action confirmation
Deleting a route or a group used `window.confirm`, which blocks the page
and ignores the console theme. A promise-based `useConfirm()` now drives
one <ConfirmDialog /> built on the reka-ui AlertDialog that
@elysola/ui ships; reka-ui is pre-bundled so dev keeps a single copy and
the dialog stacks with the Rc dialogs.
A request never outlives its asker: one made after the asking component
unmounted resolves false, and one still open when it unmounts is
cancelled.
* feat(console): confirm member and webhook removal
Removing a member, revoking an invite link and disabling a group's
webhook endpoint took effect on the first click. They now ask first;
disabling the webhook explains that senders still using the secret will
be rejected, and its button is styled as destructive.
* feat(console): confirm removing filled editor rows
Filter conditions and groups, delivery targets, saved fragments and forge
hosts vanished on a single click, taking whatever had been typed with
them. Rows holding content now ask first, while empty, never-filled
rows (`isBlankNode`: default operator, no path, no values, not negated)
are still removed directly.
* fix(i18n): remove duplicate button glyphs
"New Route", "New Group" and the group cards' "Open" link render a Plus
or ArrowRight icon next to their label, so the "+" and "→" baked into
the strings appeared twice.
* style(console): redesign route cards for narrow screens
The card was one flex row whose badges, filter chips, targets and five
hand-drawn icon buttons squeezed the route name on small screens. It is
now a grid driven by a container query: name and actions share the top
line, the filter summary (clamped to two lines) and targets follow, and
the tags wrap below; from 40rem the tags move up beside the title.
Targets of the same platform collapse into one tag with a count, long
ids truncate instead of widening the page, and the actions use lucide
icons with accessible labels.
* feat(console): reorder a group's routes by drag or keyboard
The per-card up/down arrows saved after every single step, so moving a
route five places took five writes. A Reorder mode on the group page now
swaps each card's switch for a drag handle: pointer drags (mouse and
touch) slide the neighbours out of the way and auto-scroll near the
viewport edges, Arrow Up/Down on a focused handle moves a card by one
and is announced to screen readers, and nothing is written until Save
order. Cancel or Escape (unless a dialog or list owns it) drops the
draft.
The cards move into a new RouteList component that owns the drag state.
* style(members): align member cards and invite actions
* style(group-editor): size forge and log target controls
Keep source hosts, platform selectors and remove actions aligned without stretching short controls across the dialog. Wrap component roots explicitly so their internal markup cannot break the grid.
* style(route-editor): group options and delivery target fields
Give each target labeled fields and a compact platform header, widen the filter workspace, and align fragment controls. Scroll failed validation into view when the footer is far from the affected section.
* feat(filters): add bilingual suggestions and value validation
Catalog forge events, actions, payload paths and known values with searchable English and Chinese descriptions. Match-value validation mirrors the server and only rejects inputs that cannot match.
* feat(filters): add searchable creatable value inputs
Build a theme-aligned combobox on the shared reka-ui primitives. Rank stored keys before bilingual descriptions, allow validated custom values, and preserve unconfirmed multi-value drafts instead of silently committing them.
* feat(filter-editor): integrate searchable condition inputs
Replace chip-only values with context-aware bilingual inputs and a compact condition grid. Preserve drafts across tree changes, block saves and tests until drafts are resolved, and keep keyword filters free of hidden operators.
* feat(filters): split pasted values without breaking regexes
Accept multiple values separated by commas or lines while retaining commas inside wrapped expressions and raw regex patterns. Pasting replaces the selected range and keeps rejected values as an explicit draft.
* fix(filters): adapt suggestions to the selected operator
Offer literal prefixes and suffixes for substring operators, escaped anchored patterns for regex, and numeric suggestions only for comparisons. Suggestion syntax must mean what the selected matcher actually reads.
* fix(filters): preserve regex meaning when changing operators
Swap wrapped and raw regex sources only when both compile identically after saving. Leave literal, glob, multiline and Unicode-sensitive comparisons unchanged rather than inventing non-equivalent conversions.
* a11y(filter-editor): label type and operator controls
Associate each fixed select with a stable per-condition label while keeping the compact visual layout unchanged.
* fix(editors): ignore accidental backdrop dismissal
Do not discard unsaved route or group edits when the user clicks outside the dialog. Preserve Escape, Cancel and explicit close, including popovers and confirmation dialogs stacked above the editor.
* feat(dispatch)!: scope stop and fallback to each group
A match in one group must not suppress delivery in another group. Track regular matches and stopped scopes independently, and document the routing-table boundary.
BREAKING CHANGE: stop and fallback no longer apply globally across
groups. Put mutually exclusive routes in the same group and define
fallback routes in each group that needs its own catch-all.
* fix(dispatch): honor stop on a matching fallback route
Once a fallback matches with stop enabled, skip later routes of the same group without affecting other groups. Cover multiple fallback routes in the group-isolation regression test.
* style(console): pin theme and language controls to the right
Separate utility controls from page actions so narrow screens retain a readable title column and right-aligned actions below. Wrap long headings without letting them push controls out of view.
* style(groups): place creation beside the aligned group count
Keep the new-group action inside the group list at every width and align the label and count on one baseline with a consistent type scale.
* style(groups): align card footers and keep role badges intact
Give long names two lines, show the current role in its own non-wrapping row, and anchor every card footer to the grid-row bottom regardless of optional source metadata.
* style(logs): prevent filter labels and metadata overflow
Keep filter labels on one line and allow long channel, thread and repository identifiers to wrap instead of widening the page.
* style(console): scale the sidebar and hide mobile tab tracks
Narrow the sidebar proportionally while retaining enough room for both locales. Keep mobile navigation swipeable without a visible horizontal scrollbar.
* feat(console): give each group its own routes URL
Resolve the selected group from /admin/groups/{groupId}, validate console paths, and use browser history for back navigation. Keep Groups active and let an active mobile-tab tap return to the list. Scope pending route loads to their group and retain the count beside long headings.
* feat(console): confirm leaving unsaved page work
Guard route changes when an editor or changed order draft is open. Cancel superseded questions and restore the shown history entry when repeated Back or Forward navigation is refused; only completed navigation resets page work.
* feat(console): confirm sign-out from desktop and mobile
Expose sign-out in the mobile topbar when the sidebar is hidden. Both entry points use the in-app confirmation before navigating to the server logout endpoint.
* fix(console): keep topbar tools clear of very narrow headings
Below 360px, place the full-width heading beneath the breadcrumb and utility row so the three top-right buttons cannot overlap it.
* feat(console): prioritize group titles over actions
Place New Route after Reorder in the group bar. Measure available space and remove the reorder label first, then the creation label, before truncating the group title; remeasure on resize, locale and font changes.
* fix(editors): focus the dialog without selecting its name field
Cancel the non-bubbling FocusScope mount event in the capture phase and focus the dialog itself. Keep keyboard navigation working without highlighting the name or opening the touch keyboard automatically.
* perf(console): preserve one instance across admin navigation
Use a fixed page key instead of remounting the whole console for each URL. Refresh each view when shown and isolate overview metrics and logs so page filters cannot leak into the dashboard.
* fix(console-data): discard superseded load responses
Only the latest request may update a list, its error or loading state. Invalidate pending group loads after a save so an older response cannot restore stale configuration during persistent-console navigation.
* fix(routes): serialize writes and reject unloaded route lists
Whole-list saves must start from loaded data and wait for other route writes. Lock switches and actions during saves, recheck deletion after confirmation, and rebuild saved ordering from the newest route objects.
* fix(editors): scope async results and fragment writes to sessions
A completed save or dry run must not close or overwrite a newer editor. Keep fragment state scoped by group, reject writes until the real list is ready, and retain in-flight fragment locks across navigation.
* fix(groups): serialize edits and isolate group detail panels
Prevent overlapping whole-list writes, avoid duplicate ids after rename, and discard delete confirmations prepared on a page that has since been left. Key member and webhook panels by group so local state cannot cross tenants.
* fix(console): omit the empty action row outside overview
Render the refresh-action container only where it has content so narrow layouts do not reserve a blank row after creation controls move into their page bars.
* perf(metrics): send all seven queries in one D1 batch
Avoid seven sequential network round trips and read totals, breakdowns and recent failures in one consistent transaction. Reuse the failed-send statement and row mapping while retaining group scoping.
* fix(admin-api): bypass browser cache locks for live requests
Use no-store on both client requests and admin responses. Personalized live data must not be reused, and one stalled same-URL cache entry must not block later log requests behind the browser cache lock.
* docs(routes): Clarify fallback hints and document group-scoped stop and fallback upgrade behavior
36 KiB
AGENTS.md — WebHooker
Project Purpose
Nuxt 4 (Nitro) app deployed as a Cloudflare Worker that receives GitHub webhooks and dispatches processed events to Discord channels/threads, Telegram chats/topics and Feishu group chats, and receives Discord interactions (slash commands, buttons, modals) via the Interactions Endpoint plus Telegram bot /gh commands and Feishu bot /gh commands + card buttons via their respective webhooks.
Core pipeline: GitHub Webhook → Worker (verify + filter + format) → Discord (REST) / Telegram (Bot API)
Key Decisions
- Runtime: Cloudflare Workers via the Nitro
cloudflare_modulepreset (_worker.js), H3 event handlers inserver/routes/ - UI: Vue 3 + Tailwind CSS v4 (
@tailwindcss/vite) +@elysola/ui(Nuxt module,Rcprefix); admin console is a client-side SPA (routeRules: "/admin/**": { ssr: false }), home/legal pages render server-side; app-level composites (FilterCombobox,ConfirmDialog) are built on the reka-ui primitives that@elysola/uiships (same copy, pre-bundled viavite.optimizeDeps.includeso dev keeps a single instance and dialogs/popovers stack correctly) and styled like their Rc counterparts - Styling: Elysola UI supplies semantic components and blue theme tokens;
app/assets/css/main.cssretains--wh-*RGB-triplet aliases for app-specific Tailwind utilities and bespoke layouts (avoiding collision with Elysola's--surface/--text/--borderhex tokens); theme switching supports auto/light/dark viauseTheme/ThemeToggle, toggling<html>.darkwith inline anti-flash head script - Discord interactions: HTTPS Interactions Endpoint (
POST /discord/interactions, Ed25519-signed) — no Discord Gateway / Durable Object; bot stays offline, messages always sent via REST - Storage: D1 is the source of truth for config (routes/groups via
d1_routes/d1_groups, seeserver/lib/storage/config-store.ts; each route's per-group order lives ind1_routes.position— migration 0012 — and routes load ordered bygroup_id, position, id, falling back to id order on an unmigrated database), send/audit logs, dedup (dedup_keys), delivery state (delivery_state) and message tracking (message_trackingviaserver/lib/storage/d1.tscanUseD1gate). KV keeps only cache + short-lived/ephemeral state (tokens, OAuth state, admin sessions,msg:*-adjacent locks, per-group secretstenant:*, invites, i18n overrides) with explicit TTLs. R2 parks oversized queue payloads (webhooks/YYYY/MM/DD/*.json,server/lib/storage/payload.ts) instead of KV. Astorage-prunescheduled task cleans up expired dedup/delivery/message-tracking rows - Signature verification: Web Crypto API (HMAC-SHA256 for GitHub/Gitea, Ed25519 for Discord, timing-safe secret-token compare for Telegram)
- Webhook providers: pluggable forge adapters under
server/lib/providers/(github, gitea) — each verifies its own signature format and normalizes its payload to a GitHub-shapedWebhookEvent; acustomprovider accepts arbitrary signed JSON posts (X-WebHooker-Signature) ascustomevents; GitLab etc. can be added later - Per-group webhook ingress: optional
POST /webhook/{groupId}with a per-group secret in KV (tenant:{groupId}) — Gitea/classic-GitHub/custom webhooks are verified against the group's secret instead of the operator's global ones; only that group's routes fire. The legacyPOST /webhook(global secrets, all routes) stays untouched - GitHub App tenant isolation:
Group.installationIdbinds a group to one GitHub App installation; events whosepayload.installation.iddiffers are rejected at dispatch (hard isolation on top of the optionalownerslist). The App's Setup URL points atGET /auth/github/install, which renders a choice page (createinst-{installationId}or bind to a group the signed-in user owns, verified by role);POST /auth/github/install/bindperforms the provisioning.installation.createdwebhook events auto-provision as a fallback (createinst-{installationId}or bind existing groups whoseownersmatch the installing account) - GitHub OAuth: octokit (token is stored hashed for reverse lookup)
- Admin WebUI:
/adminconfig console, OAuth-session protected viaADMIN_USER_IDSwhitelist (local-onlyDEBUG_MODE=truebypasses authentication); left sidebar navigation (Overview / Groups / Send Logs / Audit / Stats) + topbar, deep-linkable routes (/adminoverview ·/admin/groups·/admin/groups/{groupId}a group's routes, members and webhook ·/admin/logs·/admin/audit·/admin/metrics, parsed byapp/utils/admin-path.ts; the admin page'svalidate404s any other path) — the page has a fixedkey, so one console instance (and its in-flight saves) persists across these URLs while each view refreshes its data when shown; every page is a history entry, so the browser's back button returns from a group to the list (no in-page back button) and leaving with an open editor or an unsaved route order asks first; route switches/actions lock while a route write is in flight; sign-out asks for confirmation (sidebar, or a top-right button on narrow screens); editor dialogs open without focusing a field (useDialogFocus); the overview dashboard (AdminHome.vue) aggregates delivery KPIs, a routes table and recent send logs; the stats page (MetricsPanel.vue) renders KPI cards plus per-platform/per-event ok/failed bar legends and a per-status breakdown, and filters by group (?groupId=); the route/group editors (RouteEditor.vue/GroupEditor.vue) are centered, scrollableRcDialogforms with an eyebrow header and sectioned bodies - Access control: every group has role-based members (
owner/admin/viewer); super admins bypass; legacyadminIdsare read as owners (backward compatible); owners manage members + invites;ownersfield stays super-only - Invites: single-use 7-day links (
invite:{token}) for joining a group as admin/viewer;ALLOW_SELF_SIGNUP=1gives access-less users a personal group on first login (self-service SaaS entry) - Audit log: every admin operation (logins, group/route/member/invite changes) recorded in D1
audit_logs; pruned by the scheduled trigger afterAUDIT_RETENTION_DAYS(default 90) - Group webhook log channel: optional
Group.logTarget(Discord channel/thread or Telegram chat/topic) receives one summary message per webhook the group's routes dispatched (event, repo, delivery id, per route×target ✅/❌ outcome, green/red color); best-effort, not recorded insend_logs - Per-group forge branding: optional
Group.forgeSources(a list of{ host, type: "github" | "gitea", name? }the group defines itself) labels each message's footer with the first entry whose type matches the event's provider and whose host matches the repository URL's hostname (GitHub matchesgithub.com, so two Gitea instances can begit1.example.com/git2.example.com); the label is the entry's optionalname(fallback: host); links are derived from the repo URL and footer icons use raster PNGs Discord renders (GitHub'sfluidicon.png, Gitea's/assets/img/favicon.png—.icofavicons are silently ignored); Discord shows the footer icon + name, Telegram a linked name - Delivery queue: when the
QUEUEbinding is present, webhook ingress enqueues one message per event (not per target) to a Cloudflare Queue (webhooker-delivery); a Nitrocloudflare:queueplugin consumes batches, dispatches, and retries retryable failures (5xx/network/429-exhaustion) with exponential backoff (5s/30s/2m/10m) up to the queuemax_retries, after which the DLQ (webhooker-delivery-dlq) marks the delivery dead. Oversized payloads (>~100 KB) are parked in R2 (webhooks/YYYY/MM/DD/*.json, falling back to KVqueue:payload:*without the R2 binding) and resolved by the consumer; delivery state is tracked as the D1delivery_statetable (KVdelivery-state:*fallback). Without theQUEUEbinding, dispatch stays inline (existing behavior) - Storage quotas: the design avoids KV write pressure (Workers Free KV allows ~1,000 writes/day) by keeping high-frequency ephemeral writes in D1 instead — webhook dedup (
dedup_keys, atomicON CONFLICTUPSERT), delivery state and message tracking all use D1 rows viacanUseD1(prepare+batch probe) with automatic KV fallback when D1 is unavailable or unmigrated. D1 Free allows 100,000 rows written/day, so the per-event KV write cost drops to ~0; config stays cached in memory + KV with D1 authoritative - Filter DSL: a route's flat
filterscan be replaced by a nestedast(all/any/notnodes,server/lib/events/filter-ast.ts) that takes precedence when present; thefieldfilter type reads any payload value by JSONPath (path, arrays expand so any element matches) and 12 comparison operators (op:eq/ne/contains/startsWith/endsWith/regex/gt/gte/lt/lte/in/exists) extend the legacy glob/regex/case-insensitive-exact semantics; named filter fragments (D1d1_fragmentsviaserver/lib/fragments.ts, per-group) are editor-side templates inlined into the route'saston insert — the matcher never resolves fragment references; the route editor (RouteEditor.vue) exposes a recursive AST builder (FilterNodeEditor.vue: plain selects for filter type/operator, an all/any segmented toggle, NOT toggle + delete pinned per condition), searchable multi-value / path inputs (FilterCombobox.vue) fed by a bilingual suggestion catalog (app/utils/filter-catalog.ts: GitHub events/actions from@octokit/webhooksplus Gitea extras, common payload paths and their known values, English keys searchable in either language) where custom values are allowed but rejected when the matcher could never match them (validateFilterValue), a live explanation and a statelessPOST /admin/api/test-matchdry-run - Local dev: wrangler + Miniflare
Architecture
app/ # Vue 3 UI (Nuxt app dir)
├── app.vue # root component (NuxtPage)
├── assets/css/main.css # Tailwind v4 entry: Elysola-compatible RGB aliases + bespoke layout classes + Vue transition glue
├── pages/ # index (landing), terms, privacy, admin/[...slug] (console SPA)
├── components/ # ConsolePage (sidebar shell + topbar), AdminHome (overview dashboard),
│ # RouteList (drag/keyboard reorder mode) + RouteCard, RouteEditor (FilterNodeEditor
│ # AST builder + FilterCombobox searchable inputs), GroupEditor, MembersPanel, WebhookPanel,
│ # ConfirmDialog (app-wide destructive-action confirm), SendLogs, AuditLog, MetricsPanel,
│ # AppToasts, LegalLayout
├── composables/ # useI18n, useToasts, useConfirm (promise-based confirm), useBackdropGuard (editor dialogs ignore
│ # backdrop clicks), useDialogFocus (editor dialogs open without focusing a field), useGroups, useGroupRoutes, useFilterNode (AST helpers), useFragments, useLogs,
│ # useAudit, useInvites, useWebhook
├── types.ts # shared client types (Route, Group, Filter, ...)
└── utils/ # legal.ts (terms/privacy HTML bodies, zh/en), format.ts, admin-path.ts (console URL parsing),
# filter-catalog.ts (bilingual filter suggestions + value/path validators)
server/ # Nitro server
├── routes/ # H3 handlers: /health, /webhook[/:groupId], /discord/interactions, /telegram/webhook,
│ # /auth/github*, /admin/{login,logout,invite,api/**}, /api/{comment,merge,close,react,richheader}
├── tasks/ # scheduled (cron */5): discord-sync, telegram-sync, audit-prune, storage-prune
├── plugins/ # Nitro plugins: queue-consumer (hooks cloudflare:queue → handleQueueBatch)
├── error-handler.ts # JSON error handler
└── lib/
├── types.ts # Env, Config, Route, Filter, Group, WebhookEvent, NeutralMessage
├── config.ts # loadRoutes/saveRoutes (delegates to D1 ConfigStore when available, else KV config:routes), loadConfig from env
├── fragments.ts # named filter fragments (loadFragments/saveFragments — D1 d1_fragments, no KV)
├── config/ # config schema + migration + validation
│ └── schema.ts # CONFIG_SCHEMA_VERSION, valibot route/group/filter schemas, migrateRoutes/Groups, validateRoutes/Groups (non-destructive), explainRoute
├── cf.ts # cfEnv(event) — env bindings from event.context.cloudflare
├── http.ts # shared HTTP helpers
├── webhook.ts # processWebhook/handleWebhook: tenant lookup, provider detect/verify/parse, dedup (D1/KV), enqueue (or inline dispatch)
├── queue/ # Cloudflare Queue delivery pipeline
│ ├── delivery.ts # DeliveryMessage, enqueueWebhook, retry backoff, delivery-state (D1 w/ KV fallback), payload-overflow parking (R2 → KV)
│ └── consumer.ts # handleQueueBatch: resolve payload → dispatch → classify → ack/retry/DLQ
├── core/
│ └── dispatch.ts # Platform-neutral dispatch: match routes → formatEvent → driver.send/edit (batched recordSend + group filter + per-group webhook log)
├── events/
│ ├── match.ts # matchRoute, eventOwners; unified pattern syntax (*/? globs + //-wrapped regex)
│ └── filter-ast.ts # FilterNode evaluator (all/any/not + field JSONPath + 12 ops), containsKeyword, explainFilter/explainFilterNode; pattern helpers (regex/glob compile)
├── providers/ # Forge webhook providers (verify + parse/normalize to GitHub-shaped events)
│ ├── types.ts # Provider interface (matches/verify/parse)
│ ├── hmac.ts # HMAC-SHA256 + timing-safe compare helpers
│ ├── index.ts # detectProvider() registry (gitea, github, custom)
│ ├── github/ # X-GitHub-Event + X-Hub-Signature-256 ("sha256=" prefix); extracts installation.id
│ │ ├── verify.ts
│ │ └── parse.ts
│ ├── gitea/ # X-Gitea-Event + X-Gitea-Signature (plain hex HMAC)
│ │ ├── verify.ts
│ │ └── parse.ts # parse + normalize Gitea payloads to GitHub shape
│ └── custom/ # X-WebHooker-Signature (sha256= HMAC) + arbitrary JSON → `custom` events
├── formatters/ # Platform-neutral message formatters (was formatter.ts)
│ ├── index.ts # formatEvent: builds FormatContext → findFormatter → .format (falls back to formatGeneric)
│ ├── types.ts # FormatContext + EventFormatter (formatter plugin interface)
│ ├── registry.ts # eventFormatters[] + findFormatter() — 29-event formatter plugin registry
│ ├── colors.ts # GITHUB_COLORS + WORKFLOW_CONCLUSION_EMOJI
│ ├── helpers.ts # emojiPrefix, T, buildMessage, commitLink/branchLink/tagLink
│ └── *.ts # push, pull-request, issues, comments, workflow, release, create,
│ # repo, check, review, commit-comment, deployment, member, label,
│ # milestone, discussion, repository, security, generic, ping, custom
├── drivers/ # Platform drivers (pluggable push targets)
│ ├── types.ts # PlatformDriver interface + SendResult (send + edit)
│ ├── index.ts # getDriver() registry (discord default + telegram + feishu)
│ ├── discord/
│ │ ├── index.ts # DiscordDriver: send/edit → renderNeutralMessage + rest.sendMessage/editMessage
│ │ ├── render.ts # renderNeutralMessage: NeutralMessage → Discord FormattedMessage
│ │ ├── rest.ts # Discord REST sendMessage/editMessage with retry + rate-limit handling
│ │ ├── interactions.ts # Ed25519 verify + interaction handlers (/gh, buttons, modals)
│ │ └── commands.ts # APP_COMMANDS + registerGlobalCommands/syncGuildCommands/syncCommands
│ └── telegram/
│ ├── index.ts # TelegramDriver: send/edit → renderNeutralMessage + rest.sendMessage (avatar rich-header card)
│ ├── render.ts # renderNeutralMessage: NeutralMessage → Telegram HTML (parse_mode HTML)
│ ├── rest.ts # Telegram Bot API sendMessage/sendPhoto/editMessage* (chat_id + message_thread_id), retry
│ ├── updates.ts # POST /telegram/webhook: secret-token verify + handleTelegramUpdate
│ └── commands.ts # Telegram /gh login|logout|comment|merge|close + reply-message parsing + syncTelegramWebhook
│ └── feishu/
│ ├── index.ts # FeishuDriver: send/edit → renderNeutralMessage + rest.sendMessage/updateMessage
│ ├── render.ts # renderNeutralMessage: NeutralMessage → Feishu interactive card
│ ├── rest.ts # getTenantAccessToken (KV cache) + sendMessage/updateMessage/sendText/updateCard, retry
│ └── updates.ts # X-Lark-Signature verify + url_verification + /gh commands + card.action.trigger buttons
├── github/
│ ├── oauth.ts # OAuth URL, callback token exchange, getUserOctokit, comment/getComment/editComment/deleteComment/merge/close actions
│ ├── app-token.ts # createAppJwt-backed getInstallationToken + GITHUB_API_VERSION (shared App auth)
│ ├── check-run.ts # getCheckSuiteBuildLogUrl: Check-suite build-log enrichment (installation token)
│ ├── workflow-jobs.ts # getWorkflowRunJobs: fetch a workflow_run's jobs via jobs_url (App token or unauthenticated)
│ └── store.ts # KV token CRUD + D1 discord-link/telegram-link mapping (was token-store.ts)
├── web/ # HTTP UI/API logic (called from server/routes)
│ ├── oauth.ts # handleOAuthStart/Callback, install page + bind, personal-group self-signup
│ ├── actions.ts # POST /api/comment|merge|close|react (Bearer token auth via shared middleware)
│ ├── admin.ts # adminLogin/Logout, adminApi* (routes|groups|me|logs|invites|audit|webhook|metrics|delivery)
│ ├── auth.ts # Shared auth middleware + guards: requireAnyAccess, requireGroup(Role), bearerUserId, clientIp
│ ├── invites.ts # Invite CRUD (KV invite:{token}, 7d TTL) + acceptInvite (join group as admin/viewer)
│ ├── session.ts # Session CRUD (KV session:{id}), isAdminUser, cookie helpers
│ ├── groups.ts # Group CRUD (config:groups), member roles (normalizeGroupMembers/memberRole), resolveScope + role helpers (roleAt/canEditRoutes/canEditGroup)
│ ├── tenants.ts # Per-group webhook secret CRUD (KV tenant:{groupId}, 32-byte random hex)
│ └── richheader.ts # GET /api/richheader: Open Graph page for Telegram avatar link-preview card
├── observability/ # delivery metrics aggregation
│ └── metrics.ts # DeliveryMetrics + getDeliveryMetrics (SQL GROUP BY over send_logs in one D1 batch: totals, per platform/event/status, duration, attempts, recent failures)
├── storage/ # storage primitives: canUseD1 probe, D1 config store (L1 memory → L2 KV cache → L3 D1), R2 payload store
│ ├── d1.ts # canUseD1(db) — prepare+batch probe for D1 availability (falls back to KV)
│ ├── config-store.ts # ConfigStore (loadRoutes/saveRoutes/loadGroups/saveGroups/invalidateCache) backed by d1_groups/d1_routes (per-group `position` order when migrated), seeds from KV + syncs cache
│ └── payload.ts # PayloadStore backed by R2 (webhooks/YYYY/MM/DD/*.json), no-binding stub throws
└── lib/ # shared infra
├── i18n.ts # loadTranslations (KV i18n:{lang} overrides), t() with param interpolation
├── idempotency.ts # IdempotencyStore interface + kvIdempotencyStore/d1IdempotencyStore (delivery dedup via claim/has, D1 atomic UPSERT w/ KV fallback) + deliveryKey
├── correlation.ts # newCorrelationId() — per-request/delivery correlation id for logs + responses
├── message-tracker.ts # MessageTracker interface + kvMessageTracker/d1MessageTracker (msg:{eventId}:{targetId} for workflow_run/check_run edits)
├── send-log.ts # SendRecord, recordSend/getSendLog/getSendLogById/getSendLogByDelivery/getFailedSendLog (D1 send_logs)
├── send-log-batch.ts # recordSendBatch (D1 batch INSERT for send_logs)
├── audit.ts # recordAudit/getAuditLog/pruneAuditLogs (D1 audit_logs, best-effort writes)
├── log.ts # JSON console logger (info/warn/error/fatal)
└── locales/ # en.ts, zh.ts translation dictionaries
tests/ # bun test unit tests (webhook, formatter, discord, telegram, admin, groups, invites, audit, send-log, token-store, ...)
tests/fixtures/ # provider payload fixtures (github/gitea/custom) feeding provider + formatter tests
tests/__snapshots__/ # formatter snapshot golden files (toMatchSnapshot)
Responsibilities
- Verify GitHub webhook signatures (Web Crypto HMAC-SHA256,
X-Hub-Signature-256) - Verify Gitea webhook signatures (Web Crypto HMAC-SHA256, plain hex
X-Gitea-Signature) - Verify custom webhook signatures (Web Crypto HMAC-SHA256, GitHub-style
sha256=viaX-WebHooker-Signature; optional replay protection viaX-WebHooker-Timestamp+X-WebHooker-Nonce— signature over{timestamp}.{nonce}.{body}, ±5 min window, nonce dedup in KV) - Normalize Gitea webhook payloads to a GitHub-shaped
WebhookEvent(pushcompare_url→compare,pull_request_comment→pull_request_review_comment, ...) - Verify Discord interactions (Web Crypto Ed25519, X-Signature-Ed25519 over timestamp + body)
- Verify Telegram webhook calls (X-Telegram-Bot-Api-Secret-Token when configured)
- Filter events by: event type, repo name, actor, action, branch, keyword, or any payload field (
fieldwith a JSONPathpath— arrays expand so any element matches) — every filter type supports*/?glob matching and//-wrapped regular expressions (case-insensitive) plus 12 comparison operators (op:eq/ne/contains/startsWith/endsWith/regex/gt/gte/lt/lte/in/exists) - Combine filters into an AST (
Route.ast:all/any/notnodes) that overrides the flatfiltersAND-list;explainRoute/explainFilterNoderender a human-readable description of the tree - Store named filter fragments (D1
d1_fragments, per group,GET/PUT /admin/api/groups/:groupId/fragments) as editor-side templates; inserting a fragment inlines its node into the route'sast— dispatch never resolves fragment references - Offer a stateless filter dry-run (
POST /admin/api/test-match, body{ node | filters, event?, payload }) that evaluates in memory and returns{ matched, explanation }— no event payload is stored - Validate route/group config against valibot schemas on load (non-destructive: invalid entries log a warning but still load);
CONFIG_SCHEMA_VERSIONmarks the schema version andmigrateRoutes/migrateGroupsmigrate legacy shapes (e.g.target→targets) - Filter routes by group owner restriction (
Group.owners), group source-platform restriction (Group.providers: github/gitea), GitHub App installation restriction (Group.installationId), and skip a group's fallback routes whenever a regular route of that group matched; stop evaluating the group's further routes when a matched route hasstop: true(both scoped per group, so one group's routes never silence another's) - Auto-provision GitHub App installs: the App's Setup URL flow (
/auth/github/installchoice page +POST /auth/github/install/bind, owner-role verified for existing groups) and theinstallation.createdwebhook fallback both createinst-{installationId}groups or bind existing groups - Enforce role-based access on every admin API: super admins bypass,
ownermanages the group (routes/members/invites/settings),adminedits routes,vieweris read-only; legacyadminIdsgroups resolve toownermembers - Issue single-use 7-day group invite links (
invite:{token}); accepting joins as admin/viewer (never owner);ALLOW_SELF_SIGNUP=1creates a deterministic personal group (u-{userId}) on first login - Record every admin operation (login/logout, group/route/member/invite changes) to D1
audit_logs; the scheduled trigger prunes entries pastAUDIT_RETENTION_DAYS - Mention Discord roles on route trigger: route-level
discordRoleIdsare rendered as<@&id>into the Discord messagecontent(Telegram targets ignore the field) - Format 28 GitHub/Gitea event types plus
customwebhooks as platform-neutral messages (Discord embeds + Telegram HTML) - Show the forge source (named per
Group.forgeSourceshost entries) in the message footer when the group defines a host matching the event's repository - Route messages to Discord channels/threads and Telegram chats/topics via REST
- Edit already-sent messages in place for
workflow_run/check_runprogress (stableupdateKey,message_trackingvia D1 with KVmsg:*fallback);workflow_runkeys on the workflow id whilecheck_runkeys on check name + commit SHA (falling back to the run id) so providers that emit a fresh run id per phase — e.g. Cloudflare Pages — still edit the same message - Record every dispatch attempt to D1
send_logs(route id, event, target, ok/error, duration, error code) - Aggregate delivery metrics (
server/lib/observability/metrics.ts) fromsend_logs— totals, ok/failed counts + failure rate, per-platform/per-event/per-status breakdowns, average duration and attempts, recent failures;getDeliveryMetrics(db, groupId?)sends all seven queries as one D1batch(a single round trip and a consistent snapshot) and scopes every query bygroup_idwhen a group is passed - Expose admin observability endpoints —
GET /admin/api/metrics?groupId=(delivery metrics, optional group scope; recent failures group-scoped for non-super) andGET /admin/api/delivery/:deliveryId(all send-log attempts for one delivery, group-scoped) — through the/admin/api/[...slug]catch-all route (server/routes/admin/api/[...slug].ts) that wires every admin API handler to its method+path - Serve a per-group webhook ingress (
POST /webhook/{groupId}, per-group secret in KVtenant:{groupId}) for Gitea/classic-GitHub/custom senders; only that group's routes fire; dedup keys are provider- and tenant-scoped (delivery:{provider}:{groupId}:{id}viaidempotencyStore, D1dedup_keyswith KV fallback) - Issue a per-request correlation id (
requestId) in webhook responses and dispatch logs - When the
QUEUEbinding is present, enqueue each verified webhook as a single Queue message (webhooker-delivery) instead of dispatching inline; the consumer resolves the payload, re-scopes routes to the tenant group, and dispatches; retryable failures (5xx/network/429-exhaustion) are retried with exponential backoff (5s/30s/2m/10m) up to the queuemax_retries, then the DLQ marks the delivery dead - Track delivery state in the D1
delivery_statetable (delivery-state:*KV fallback: pending/processing/delivered/retrying/failed/dead) so redelivered messages are skipped idempotently; oversized payloads are parked in R2 (webhooks/YYYY/MM/DD/*.json, KVqueue:payload:*fallback) and deleted after dispatch - Prune expired D1 rows via the scheduled
storage-prunetask (dedup keys past expiry, delivery state older than 7 days, message tracking older than 30 days; audits viaaudit-prune) - Send a per-event summary (event, repo, delivery id, per route×target ✅/❌ outcome) to the group's
logTargetwhen configured - Serve
/ghslash commands + message context-menu commands + PR merge/close buttons + comment modals - Serve Telegram
/ghcommands (login/logout/comment/merge/close) via reply-message parsing - Serve Feishu
/ghcommands (login/logout/comment/merge/close) and card Merge/Close buttons via the/feishu/webhookendpoint (X-Lark-Signature verify +url_verificationchallenge) - Sync application commands from the scheduled trigger (global ~1h propagation + per-guild instant)
- Sync the Telegram webhook URL from the scheduled trigger (setWebhook)
Message Format Spec
- Every message title must start with the repo, then optional
#number, then: subject:{repo}{#number}: {subject}(e.g.acme/widget#7: Add feature). Repo comes frompayload.repository.full_name; fall back tot("common.repository")when missing. - Only the repo head is hyperlinked (never the whole title). Drivers split the title via
splitMessageTitle(server/lib/formatters/helpers.ts): the Discord embed title is{repo}{#number}linked to the event's object URL (message.url, e.g. the issue/PR/commenthtml_url) and: {subject}renders as the first description line; Telegram keeps the one-line title with an inline repo link and a plain subject. Messages without a colon separator (a:followed by a space) keep the legacy whole-title link — use colon-free wording for such titles. - Do NOT use
"Comment on org/repo"/"Review on org/repo"prefixes. Comments, reviews and inline comments use the same{repo}{#number}: {title}title as their parent object. - All event-specific emoji live in
server/lib/formatters/(via theemojiPrefixhelper), never in the locale files. Emoji is controlled per group through theGroup.emojitoggle (default true);showEmoji=falsemust strip every emoji from titles, descriptions, fields and links. - Milestone progress bars (🟢🟡🟠⬜) are data visualization and are exempt from the emoji toggle.
workflow_runmessages render a Jobs field as a Discorddifffenced code block (server/lib/formatters/workflow.ts): one line per job,${marker} ${name} ${emoji}${status}plus· {duration}for completed jobs.+(green) forsuccess,-(red) for other non-pending conclusions, a plain space for running/queued/pending; job names clamp to 200 chars and the field to the platform field limit. Drivers without diff support (Telegram, Feishu) collapse it to inline code.- Commit hashes, branches and tags render as inline code wrapped in a hyperlink
(
commitLink/branchLink/tagLinkhelpers inserver/lib/formatters/helpers.ts, e.g.[`abc123d`](https://.../commit/abc123def456),[`main`](https://.../tree/main)), falling back to plain inline code when the repo base URL is unavailable. - Content is clamped to the Discord embed limits (title 256, description 4096, field value 1024, 25 fields) both in the formatters and as a final safety net in the Discord render; the Telegram render caps the whole message at 4096 chars with tag-safe truncation. Commit subjects render only the first line, truncated to 200 chars.
- Locale templates use a
{emoji}placeholder immediately followed by the text (no space); the formatter injectsem(...)which carries the trailing space.
Development
Package manager is bun — never use npm/npx (no package-lock.json, lockfile is bun.lock; CI runs bun install --frozen-lockfile).
bun install # Install dependencies (updates bun.lock)
bun run dev # Nuxt dev (HMR + Nitro dev server)
bun run build # Production build (nuxt build, cloudflare_module preset)
bunx wrangler dev # Miniflare preview of a built worker (bun run build first)
bun run typecheck # Type checking (nuxt typecheck)
bun run lint # ESLint
bun test # Unit tests (under tests/)
Test suites beyond the per-module unit tests: provider fixtures (tests/fixtures/ +
tests/provider-fixtures.test.ts), formatter snapshots (tests/formatter-snapshot.test.ts →
tests/__snapshots__/), and platform contract tests (tests/platform-contract.test.ts, which
assert the Discord/Telegram renderers clamp to their platform limits). CI
(.github/workflows/ci.yml) runs bun install --frozen-lockfile + bun test + bun run lint;
CodeQL (codeql.yml) and Dependabot (dependabot.yml) are configured under .github/.
Documentation
Keep every functional change in sync with the docs. After implementing a feature, fix, or refactor, update all of the following that are affected:
AGENTS.md(this file) — architecture tree, responsibilities, key decisions, configREADME.md/README.zh.md— features, setup, configuration, supported eventsdocs/(VitePress) — bothdocs/(English) anddocs/zh/(Chinese) mirrorsconfig.example.yaml/.env.example— example config/secret files
Rule: no functional change ships without its documentation; docs and code must not drift.
Configuration
- Local dev:
.dev.vars(wrangler reads this for env bindings) - Production:
wrangler secret put <NAME>for each secret - Routes: config in D1
d1_routes/d1_groups(authoritative), seeded from legacy KVconfig:routes/config:groupson first load; cache-only KV keys - KV namespace: Required binding for token/state/session/cache storage (dedup/delivery-state/message-tracking fall back to KV when D1 is unavailable)
- D1 database: Binding
DB(databasewebhooker, id214a0104-3235-47c0-b7bf-ddda95f3c8ac) forsend_logs+audit_logs+discord_links+telegram_links+d1_groups+d1_routes+d1_fragments+dedup_keys+delivery_state+message_trackingtables - Queue: optional
QUEUEproducer binding plus consumerswebhooker-deliveryand its DLQwebhooker-delivery-dlq(declared inwrangler.jsonc); when absent, webhook dispatch stays inline - R2: optional
PAYLOADbinding (bucketwebhooker-payloads) for oversized queue payloads; without it, oversized payloads fall back to KVqueue:payload:* - Access control:
ADMIN_USER_IDS(super admins),DEBUG_MODE=true(local-only authentication bypass),ALLOW_SELF_SIGNUP(optional personal group on first login),AUDIT_RETENTION_DAYS(default 90) — all plain env vars, not secrets - Discord:
DISCORD_PUBLIC_KEY(Interactions Endpoint signature verification, from Discord Developer Portal) andDISCORD_APPLICATION_ID(optional, auto-resolved viaGET /oauth2/applications/@mewhen omitted) are required for interactions - Telegram:
TELEGRAM_TOKEN(Bot API token from BotFather) required for Telegram routes;TELEGRAM_WEBHOOK_SECRET(optional secret token forPOST /telegram/webhookverification); avatars are sent as a link-preview card via the built-inGET /api/richheader(overridable withTELEGRAM_RICH_HEADER_HOST) - Webhook providers:
GITEA_WEBHOOK_SECRET(required to receive Gitea webhooks; Gitea signsX-Gitea-Signaturewith the hex HMAC-SHA256 of the body)
Deployment
bunx wrangler secret put GITHUB_WEBHOOK_SECRET
bunx wrangler secret put DISCORD_TOKEN
bunx wrangler secret put DISCORD_PUBLIC_KEY
bunx wrangler kv namespace create KV
# Update wrangler.jsonc with KV ID
bunx wrangler d1 create webhooker
# Update wrangler.jsonc d1_databases with the database ID
bunx wrangler queues create webhooker-delivery
bunx wrangler queues create webhooker-delivery-dlq
# Queues are declared in wrangler.jsonc (QUEUE binding); no env var needed
bun run db:migrate:prod # wrangler d1 migrations apply webhooker --remote (migrations/0001..0012)
# R2 bucket for oversized payloads (P0): bunx wrangler r2 bucket create webhooker-payloads
bunx wrangler deploy
Full list of secrets used: GITHUB_WEBHOOK_SECRET, GITEA_WEBHOOK_SECRET,
GITHUB_APP_ID, GITHUB_PRIVATE_KEY
(PKCS#8 PEM), GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, DISCORD_TOKEN,
DISCORD_PUBLIC_KEY, TELEGRAM_TOKEN, TELEGRAM_WEBHOOK_SECRET, ADMIN_USER_IDS, DEBUG_MODE,
plus optional BASE_URL, DISCORD_APPLICATION_ID, TELEGRAM_RICH_HEADER_HOST,
NUXT_PUBLIC_DOCS_URL, NUXT_PUBLIC_REPO_URL, NUXT_PUBLIC_LEGAL_CONTACT. See .env.example and docs/guide/configuration.md.
Notes
- Commands sync from the scheduled trigger (
*/5 * * * *): registered per-guild for instant availability and globally (24h dedup, ~1h propagation). - The bot is always offline (no Discord Gateway); interactions arrive via the HTTP endpoint.