The change to Project instead of Job has had a significant and detrimental impact on our business processes. Your statement that "The renaming won’t break existing integrations and customizations because we’re only updating the captions in the user interface and the terms in our documentation. We aren’t touching the names of the underlying table and field objects." is untrue. The Purchase Header table, for instance has had the fields changed which causes integrations like Jet Reports to break. This change is causing significant problems since our reports would all have to be rewritten to accommodate this change. This should not have been done without consultation.