Look up many jobs by exact name

The batched exact-name lookup's request body.

The names travel in a body rather than a query string because they do not fit in one: an exact name may be 200 characters, and the deployment stops accepting a URL well before a useful number of them, with a proxy-level 414 no handler can turn into a usable error. extra="forbid" so a misspelled field is refused rather than silently ignored.

The batched exact-name lookup: one row per name that resolved, and the names that did not.

A miss is reported per name rather than as the whole-request 400 a single-name lookup returns, because "which of these already exist" is the question this shape exists to answer -- a caller resuming an interrupted campaign needs the misses as data, not as an error.

Exactly one row per resolved name, the newest. Under organization=true a name can match once per visible member; this shape answers the most recent, and the single-name read is where every match is available. That is also what bounds the response: rows cannot outnumber the names asked for, and every JobName returned came from the request body.