Relax Mixed Case constraint on "customer-facing text strings"?

### Introduce yourself

Hi, I'm Sylvain Lesage, I'm one of the maintainers of a GTFS in La Paz, Bolivia (https://mobilitydatabase.org/feeds/gtfs/mdb-3491 / https://github.com/datosbolivia/gtfs)

### Ask a question

The reference currently reads:

> All customer-facing text strings (including stop names, route names, and headsigns) should use Mixed Case (not ALL CAPS), following local conventions for capitalization of place names on displays capable of displaying lower case characters (e.g. “Brighton Churchill Square”, “Villiers-sur-Marne”, “Market Street”).

(in https://gtfs.org/documentation/schedule/reference/#file-requirements)

But I faced an issue in La Paz (https://files.mobilitydatabase.org/mdb-3491/mdb-3491-202608210055/report_8.0.1.html - see `mixed_case_recommended_field` warning: `stop_name` is `YATIÑA UTA - UPEA`). I put the stop name ALL CAPS because I understand we have to show the same capitalization as what is in the field:

> The stop_name should match the agency's rider-facing name for the location as printed on a timetable, published online, or represented on signage

https://gtfs.org/documentation/schedule/reference/#stopstxt

What is the recommendation in this case? Could we help GTFS producers understand the priority between the two rules:
- *All customer-facing text strings (including stop names, route names, and headsigns) should use Mixed Case (not ALL CAPS)*
- *The stop_name should match the agency's rider-facing name for the location as printed on a timetable, published online, or represented on signage*

Review the linked GTFS reference sections for file requirements and stop_name, along with the reported mixed_case_recommended_field warning. Determine how the mixed-case recommendation should relate to the requirement to match rider-facing names, including the ALL CAPS example. Done means the documentation clearly states the priority or exception for such cases.

Written by the indexing model from the issue text.