[Rule] Resource naming rules should not change

This could result in failures which would have earlier succeeded. Even if the rules become less strict, clients relying on earlier name constraints to perform local validation will fail.

The issue names no files, tests, or entry points. Start by locating the resource naming comparison rules in the openapi-diff command-line tool and determine where compatibility is checked. Done means an existing resource name remains accepted when comparing specifications, with tests covering the naming constraint behavior.

Written by the indexing model from the issue text.