Jakob Wennberg
ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
33 lines
1.3 KiB
TypeScript
33 lines
1.3 KiB
TypeScript
/**
|
|
* GET /api/webhooks/dispatch/cron: per-minute webhook delivery dispatcher.
|
|
*
|
|
* Picks up due deliveries (pending or retry-due failed) and POSTs them to
|
|
* their configured receivers. Each cycle handles up to 50 deliveries; with
|
|
* the per-minute cadence this gives 3000/h headroom before deliveries start
|
|
* to backlog. Bumps to a higher batch size or moves to a queue worker
|
|
* (Vercel Queues, on the post-Phase-6 roadmap) are the migration path.
|
|
*
|
|
* Authenticated via CRON_SECRET (Authorization: Bearer ...). The route
|
|
* returns the dispatch summary in the response body so an operator can grep
|
|
* Vercel logs to see how many succeeded / failed / went dead per tick.
|
|
*/
|
|
|
|
import { NextResponse } from 'next/server'
|
|
import { withCronContext } from '@/lib/api/with-cron-context'
|
|
import { dispatchDueDeliveries } from '@/lib/webhooks/dispatcher'
|
|
import { createServiceClientNoCookies } from '@/lib/auth/api-keys'
|
|
|
|
export const GET = withCronContext('cron.webhook_dispatch', async (_request, ctx) => {
|
|
const supabase = createServiceClientNoCookies()
|
|
const summary = await dispatchDueDeliveries({ supabase })
|
|
|
|
ctx.log.info('webhook dispatch cycle complete', {
|
|
picked: summary.picked,
|
|
delivered: summary.delivered,
|
|
failed: summary.failed,
|
|
dead: summary.dead,
|
|
})
|
|
|
|
return NextResponse.json({ data: summary })
|
|
})
|