Currently, ap_verify creates its metrics files in the caller's working directory. A more compartmentalized way to handle the output is to put it in the workspace created with the --output command-line argument. This will not interfere with the Butler (since the workspace is not a repository) or CI upload (which searches for files in the entire directory tree, see DM-16728).

The main complication is how to handle the --metrics-file argument. The best option is probably to include an {output} placeholder (making the default value "{output}ap_verify.{dataId}.verify.json"). This will avoid surprising behavior from making the directory implicit, and will be backwards-compatible with any scripts that already use --metrics-file.