Find tarbaby on the PATH from bin/tpsgi's shebang

#!bin/tarbaby resolved against the working directory, so bin/tpsgi ran
only from the top of a checkout.  Installed from CPAN, tarbaby is in a bin
directory on the PATH and bin/tpsgi is nowhere near it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.perlcriticrc

@@ -70,9 +70,9 @@ info_level = 30
 [PreferredModules]
 config = .preferred_modules.ini
 # bin/tpsgi is the PSGI application, and starts the server that runs it when it
-# is run itself, from the top of the installation.
+# is run itself.
 [logicLAB::RequireSheBang]
-formats = #!/usr/bin/env perl || #!bin/tarbaby
+formats = #!/usr/bin/env perl || #!/usr/bin/env tarbaby
 # Performance
 [logicLAB::ProhibitShellDispatch]
 [ProhibitPipeOpen]

README.md

@@ -28,11 +28,11 @@ sub hello {
 
 # DESCRIPTION
 
-Start it with the Starman options you want, from the directory it is installed
-in:
+Start it with the Starman options you want, from the directory of the
+application, with tarbaby on the PATH:
 
 ```
-bin/tpsgi ... [starman args]
+tpsgi ... [starman args]
 ```
 
 A PSGI server built to migrate old mod\_perl/apache stacks onto psgi, and that powers tCMS.

bin/tpsgi

@@ -1,4 +1,4 @@
-#!bin/tarbaby
+#!/usr/bin/env tarbaby
 
 # PODNAME: tpsgi
 # ABSTRACT: PSGI application which simplifies migrating legacy/cgi applications to PSGI, but also has advanced features for normal psgi apps

lib/TPSGI.pm

@@ -1690,10 +1690,10 @@ A router module, which C<routers> in F<~/.tpsgi.ini> names:
 
 =head1 DESCRIPTION
 
-Start it with the Starman options you want, from the directory it is installed
-in:
+Start it with the Starman options you want, from the directory of the
+application, with tarbaby on the PATH:
 
-    bin/tpsgi ... [starman args]
+    tpsgi ... [starman args]
 
 A PSGI server built to migrate old mod_perl/apache stacks onto psgi, and that powers tCMS.