Host a staff export of this collateral's risks, under Kobalt's own S3 prefix.

The customer route reaches the same renderer, but keys the object by Depends(get_company_id) — which follows a masquerade. A staffer masquerading as one tenant while exporting another's collateral would file that PDF under the masqueraded tenant's prefix. An internal artifact about a customer does not belong in any customer's export prefix, so this names Kobalt as the owner outright, the way the requirement-applicability bench does for its CSVs.