[Bug Fix] Dispatch exceptions through the router so 500s aren't masked as 404

config.exceptions_app pointed at a lambda that always rendered the
not_found action, so every unhandled error (including 500s such as a
raising view) surfaced as a 404. That masked the DropdownMenu render
error behind a misleading 'not found' page.

Point exceptions_app at the router instead; the /404 and /500 routes
already exist, so the response status now matches the actual error and
ErrorsController#internal_server_error is finally reachable.

Author: djalmaaraujo

docs/config/application.rb

@@ -24,6 +24,9 @@ class Application < Rails::Application
     # config.time_zone = "Central Time (US & Canada)"
     # config.eager_load_paths << Rails.root.join("extras")
 
-    config.exceptions_app = ->(env) { ErrorsController.action(:not_found).call(env) }
+    # Dispatch exceptions through the router (see the /404 and /500 routes) so the
+    # response status matches the actual error. A bare lambda to a single action
+    # rendered every failure as 404, masking 500s (e.g. a raising view) as "not found".
+    config.exceptions_app = routes
   end
 end