Why

Flight::path() stopped loading namespaced app classes in 3.19.0 / 3.19.1. 3.18.3 still works. flightphp/docs hit this on app\middleware\... after bumping core.

This breaks a Flight rule: upgrades should not break the project.

Cause

PR #709 (autoload-rework):

1. composer.json dropped "files": ["flight/autoload.php"], so Composer never includes the file that calls Loader::autoload().
2. flight/autoload.php started returning when vendor/autoload.php exists, so a Composer install never registers Loader::loadClass().

Flight::path() still calls Loader::addDirectory(). Nothing is listening.

Fix

• Put the files autoload back. Keep classmap + flight\\ PSR-4.
• Always call Loader::autoload(true, [dirname(__DIR__)]). Do not return early just because Composer is present.
• Regression test: Flight::path() then class_exists(\app\middleware\Something::class) for a class that is not in Composer PSR-4.

After merge, docs can unpin ^3.15 <3.19 once there is a 3.19.2 (or whatever you tag).