tina4 routes: exits 1 under the CLI, tells you to cargo install, and with the override boots a server and kills the port holder

[andrevanzuydam]

CLI 3.8.58, tina4-python 3.13.87. tina4 routes is advertised in https://tina4.com/llms.txt and tina4 --help ("List all registered routes").

Actual

Run from inside a project, through the CLI:

$ tina4 routes
Tina4 must be started with the tina4 CLI:
  tina4 serve
Install: cargo install tina4

Exit code 1.

Two problems in that message alone:

1. It refuses while being run by the very CLI it demands.
2. cargo install tina4 directly contradicts the documented install path ("no Rust toolchain, no package-manager dependency" - the installer ships prebuilt binaries).

Worse: the documented escape hatch is destructive

Applying TINA4_OVERRIDE_CLIENT=true does not list routes. It boots a full server:

Port 7146 in use - killing existing process...
Port 7146 freed

A read-only introspection command should never start a server, and should certainly never kill whatever else is listening on the default port. On a dev machine running other projects this is a genuine hazard.

Expected

tina4 routes prints the route table and exits 0, without binding a port or killing anything.

I have removed tina4 routes from llms.txt until this is fixed. Worth checking the same command on php/ruby/nodejs.