5 Commits
Author SHA1 Message Date
sam 17e6e66e72 refactor(archied): delete the file-configured forge webhook receiver; forge webhooks arrive through event capture (#1817)
deploy / plan (push) Failing after 2s
deploy / gate (push) Skipped
deploy / archied-image (push) Skipped
deploy / agent-image (push) Skipped
deploy / dist-zip (push) Skipped
2026-11-09 00:50:00 +11:00
sam 75988204d5 docs: strip doc and issue references from config, deployments and examples 2026-10-03 22:27:08 +10:00
sam 2dd321913f docs(tools): point the forge example at the receiver's default port 2026-09-22 03:42:28 +10:00
sam 569bf7177b feat(tools): sign for the forge receiver from webhook-send
The sender drove only the capture intake, which is the one inbound path a
config change cannot break. It now also signs a GitHub issue delivery for
[forge].webhook_addr: X-Hub-Signature-256 over the exact bytes, the event
header, and optional --assignee/--label so the payload can satisfy a
bot-user or label trigger. The signature is the same digest
webhookguard.VerifyHMAC computes, so a refusal here is the receiver's
policy rather than a mismatch in the tool.

--url now names the intake a send goes to (dashboard for capture, receiver
for --forge) and --api names the dashboard for the read-back, which is a
different host once the receiver has one of its own.
2026-09-22 03:42:23 +10:00
sam 1103b4f1e6 feat(tools): a capture-intake sender for exercising the Events surfaces
Posts to /webhooks/capture/{source} with a realistic GitHub, Sentry, form or
large payload (or an exact body), reads the capture back so a silent drop is
visible immediately, and names the intake's rate and size limits when it
hits them. Wired as task webhook:send.
2026-09-21 01:10:30 +10:00