Not supported - audit search is POST-only

THIS OPERATION ALWAYS RETURNS 405, and it is documented because it is registered deliberately rather than by accident.

Audit search takes a JSON criteria body, so it is POST-only. Without an explicit GET registration the request fell through to the greedy GET /api/v1/audit/{id} with id="search" and answered audit record not found - a 404 that lies about the resource and sends anyone probing the API hunting for a data problem that does not exist.

A working query-string mirror is deliberately NOT offered: it would be a second, silently diverging spelling of a contract the SDKs and plugins already drive over POST.