[ghcpuman902]

The README now opens with a short recording of the tfl CLI, a screenshot of the Board, and a comparison against the other public TfL clients. package.json homepage is https://tfl.manglekuo.com. Version is 2.15.1. Nothing is published to npm, and this pull request is not merged.

README images use absolute raw.githubusercontent.com URLs on main, so they render on npm after merge. The comparison was checked against each repo's source and the package.json on npm (16 October 2026). Coverage is the 84 operations in the committed OpenAPI snapshot (ENDPOINT_COUNT, pathCount). No cell is marked ?.

Good first issues

Ideas only. This pull request does not open them.

1. Offline station-hub example. Add examples/station-hub.ts that loads STATION_HUBS and resolveArrivalsStopId for Liverpool Street (940GZZLULVT resolves Elizabeth line arrivals to 910GLIVST). No API key. examples/ currently covers the tube/bus mapping and a live arrivals CLI.

2. River-bus pier example. Add a short example that polls the pier (NaptanFerryPort, ids starting 930G) and explains why a berth id (9300…) comes back empty. The README already states this. There is no file to copy.

3. Stop compass example. Add examples/stop-compass.ts for stopPoint.get lifting towards, compassPoint, and compassBearingDegrees (the 490013766E stop in the README). Prediction bearing is the vehicle heading. A painted stop letter W is Stop W.

4. Quieter tfl check failure. In src/bin/tfl.ts, runCheck prints the report and then throws CliError with the same fix sentence, so a bad slug such as Central prints the hint twice. Print the report once.

5. Offline station-order script. Add examples/station-order.ts that prints Bakerloo outbound Regular station ids from LINE_STATION_SEQUENCES, so someone can run the package before they have a TfL key. The snippet lives in the README only.