What happened

The content scanner rejects TSV (Tab-Separated Values) files with the following error:

Content scanner rejected table.tsv: MIME type 'text/tab-separated-values' is not supported by the content scanner.

Expected behavior

TSV files should be accepted by the content scanner, just like CSV files. Since TSV and CSV are fundamentally the same format (delimited text data, just with tabs vs. commas), there's no security or functional reason to support one and not the other.

Why this matters

• Users naturally produce TSV files from spreadsheets, databases, and export tools
• If the scanner supports text/csv, supporting text/tab-separated-values is a trivial addition and a user-expectation match
• Currently, users hit a hard rejection error when providing TSV files

Suggested fix

Add text/tab-separated-values to the list of supported MIME types in the content scanner, alongside text/csv.

Steps to reproduce

1. Create a .tsv file (tab-delimited text)
2. Provide it to Netclaw as a file attachment / upload
3. Observe the content scanner rejection error