Because only the names people see changed. The module underneath is still called Hooks, so everything a program addresses keeps the old word, and keeps working:

  • API routes. Jobs are managed at /cdna-api/hooks/hook/{id} and listed at /cdna-api/hooks/hooks. Their runs are read at /cdna-api/hooks/batches/{job id} and /cdna-api/hooks/batch/{id}, and a job is started with POST /cdna-api/hooks/hook/{id}/run. A web event answers at /cdna-api/webhook/{slug}.
  • Entity names. A job is Hooks\Entities\Hook and a run is Hooks\Entities\Batch. That is how they appear in the generated Reference and in another job's entity events.
  • Templates. Sites keep job templates (email bodies, request payloads) under templates/hooks/ by convention. Nothing requires the name, and nothing needs moving.

The MCP server uses the new names: coredna_list_jobs, coredna_list_job_runs, coredna_run_job. In code and integrations, keep the routes as they are: they are the only ones the API answers to.