Discussing ocsf/ocsf-schema#1146 during the community call brought up the possibility of enforcing the "See Specific Usage" convention more rigorously.
The server already emits a warning if descriptions with "See Specific Usage" aren't overridden in their specific usage.
The assertion is that enums with only the default "0"/"99" values defined in dictionary.json should have "See Specific Usage" in their description.
So an additional check should be added to ensure non-specific enums have this string in their description.