fix(laravel): prevent migration discovery from hanging the server

[sidux]

Existing bug

Laravel migration discovery currently starts before PHPantom determines whether the workspace uses Laravel. It therefore runs in every Composer project, including Symfony applications.

The recursive discovery also walks ignored and generated directories and follows directory symlinks. In large workspaces this can keep initialization stuck at 100% CPU indefinitely, leave orphaned PHPantom processes after editor restarts, and block every LSP request until the editor times out. Go to Definition, completion, hover, diagnostics, and other features then appear completely broken.

Fix

• classify the workspace from Composer before starting Laravel schema and migration features
• register Laravel SQL/database watchers and run refresh handlers only for Laravel or Illuminate projects
• make default migration discovery respect ignore rules and skip vendor, hidden, and symlinked directories
• retain traversal hardening for real Laravel projects as defense in depth

Tests

• cargo test non_laravel_projects_ignore_schema_watch_changes
• cargo test default_migration_discovery_skips_ignored_and_symlinked_directories
• cargo test discovers_direct_non_vendor_migrations_only
• cargo clippy --fix --allow-dirty -- -D warnings
• cargo fmt

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!