#3867: the deprecated generate-http-hooks CLI is gone
Channel 1 was a per-event HTTP hook generator that double-sent every event next to the HMAC-signed sink. It was deprecated in #1861, warned on every run, and shipped zero type:"http" entries in hooks.json for its whole life. It was still not zero-ref. This PR deletes the file and every entry point.
Before and after
Entry points, re-derived at execution time
The issue listed a hypothesis. The real set came from git grep -n 'generate-http-hooks\|generate:http-hooks\|warnDeprecated' across src, scripts, package.json, tests and docs/site/content. Six of the eleven source hits were not in the issue.
| Path | Was | Now | In issue? |
|---|
Why hook-token-check stays
The old header said
scripts/generate-http-hooks writes 19 type:http entries; this hook pairs with the generator's --write refusal.
The new header says
The generator is gone, but entries a pre-#3867 install wrote sit in per-user settings.local.json files nothing regenerates, and a hand-written entry has the same shape. The hook is now the only guard for those leftovers. Behaviour unchanged, 51 unit tests still pass.
What the wizards do now
The "Full streaming" versus "Summary only" split in /ork:setup Phase 9 and /ork:configure Step 10 only existed because channel 1 did. Both collapse to one option, and the option does exactly what channel 4 always needed:
.claude/orchestration/config.json -> { "webhookUrl": "https://your-api.com/hooks" }
export ORCHESTKIT_HOOK_TOKEN=... # in the shell that launches Claude Code
lib/sink-registry.ts registers the built-in HttpSink when both are present; lifecycle/usage-summary-reporter posts the SessionEnd summary to the same URL.