Extract PassageRouteRegistry to deduplicate handler discovery

[morcen]

What was broken

PassageController::handle(), PassageHealthCommand::passageRoutes(), and PassageListCommand::handle() each independently implemented the same four steps: find Passage routes, read the _passage_handler route default, validate it against PassageControllerInterface, resolve it through the container, and merge config('passage.options') with the handler's getOptions().

Because this logic was duplicated three times instead of shared, the implementations had already drifted apart twice in the past:

• PassageListCommand used to resolve handlers with new $handler instead of going through the container, which broke for handlers with constructor dependencies (later fixed to match the other two call sites).
• PassageListCommand used to match routes by a partial action-name substring instead of the fully-qualified controller class (later fixed to match PassageHealthCommand's approach).

Nothing prevented a future change to any one of the three call sites from silently diverging from the other two again in the same way.

What changed

• Added Morcen\Passage\Support\PassageRouteRegistry, the single place that:
  • finds all routes registered through the Passage facade (routes())
  • reads a route's configured handler class (handlerClassFor())
  • validates a handler class against PassageControllerInterface (isValidHandler())
  • resolves a handler through the container (resolveHandler())
  • merges config('passage.options') with the handler's own options (optionsFor())
• Updated PassageController::handle(), PassageHealthCommand, and PassageListCommand to use the registry instead of their own copies of this logic.
• As part of unifying the three call sites, PassageListCommand's target resolution now merges config('passage.options') with the handler's own options the same way the controller and health command already did, instead of using the handler's raw getOptions() alone.
• Removed the now-unused Illuminate\Contracts\Foundation\Application $app dependency from PassageController's constructor, since handler resolution now goes through the registry.
• Added tests/Unit/PassageRouteRegistryTest.php covering the registry directly, and updated the existing controller tests that construct PassageController manually to pass the new PassageRouteRegistry dependency.

Testing

• vendor/bin/pint --dirty — passed, no changes needed
• vendor/bin/pest — 250 passed (631 assertions), full suite green

Fixes #88

🤖 Generated with Claude Code

https://claude.ai/code/session_01DGa5tuhzv66zYWhZ6PWXXr

---

Generated by Claude Code