It's definitely there. Yesterday as a test I duplicated the content fragment itself, deleted the old one, then renamed the duplicate content fragment to be the same as the original one. That one published without issue. So it has to be something else, like a permissions issue or some setting that is...