Retire a reference table you own. Soft delete -- the row is kept.

Refused with 409 while any detection rule still references the table, in any
organization: retiring a curated list out from under another tenant's rule breaks that
tenant. The message names only your own rules, and reports others as a count.

The slug is released by renaming the retired row to
<slug>_deleted_reference_table, so the original name is immediately available for a
new table. The response reports the renamed slug. Retiring the same name more than once
appends _2, _3, and a name long enough to overflow the 64-character limit is
truncated to fit -- so a restore that strips the suffix recovers the original name only
when neither happened.

The row, its items and its history are all kept, which is what leaves a restore
possible; it simply no longer appears in any read path.