Best practices on stop_times.txt about internal timing points

### Introduce yourself

_No response_

### Ask a question

The best practice contains the following statement:

> On revenue trips, internal “timing points” for monitoring operational performance and other places such as garages that a passenger cannot board should be marked with pickup_type = 1 (no pickup available) and drop_off_type = 1 (no drop off available).

To my understanding, `stop_times.txt` should only contain "stops" for the trip. Examples of non-passenger stops include driver change points at service motorways, technical stops for refuelling, passing points on single-track railways, etc. where the service must stop.

I am seeing some GTFS generator / dataset putting some internal "pass points", which serves as timing points (and possibly validates tickets) but the service doesn't stop at all, into the `stop_times.txt` which has resulted in our frontend applications giving misleading instructions (showing them in the stop list).

I would like a clarification on the above matter.

Is it appropriate to put places, where a service passes through but do not actually stop, into `stop_times.txt`? Some of these places are relevant to passengers because they validate certain tickets.