feat(parser): comprehensive PHP/Laravel support — fix infrastructure + Laravel semantic edges

[Minidoracat]

Summary

• Fix PHP parsing infrastructure: _get_call_name(), _get_bases(), and _extract_import() all had no PHP-specific branches, making CALLS / INHERITS / IMPORTS edges completely non-functional for PHP codebases
• Add Laravel semantic edges: Route→Controller CALLS, Eloquent relationship REFERENCES, Blade template directive IMPORTS_FROM, PSR-4 namespace resolution
• Add language-scoped entry points: PHP-specific patterns (handle, boot, register, up/down) don't pollute other languages

Motivation

PHP is listed as a supported language, but the parser produced zero CALLS edges and zero INHERITS edges for PHP files. The root cause: tree-sitter-php uses name as the AST node type for identifiers (not identifier like other grammars), so _get_call_name() could never match PHP call expressions. Similarly, _get_bases() and _extract_import() had no PHP branches, falling through to defaults that produced no useful edges.

Tested on real Laravel 9, 12, and 13 projects:

Metric	Laravel 9 (before → after)	Laravel 12 (before → after)	Laravel 13 (before → after)
CALLS	4,962 → 35,771 (7.2x)	0 → 9,369	25,773 → 27,008 (+1,235)
INHERITS	0 → 346	0 → 481	0 → 49
REFERENCES	9 → 54 (6x)	2 → 74 (37x)	273 → 278
TESTED_BY	0 → 4,800	0 → 681	68 → 135
Total edges	13,525 → 49,527 (+266%)	4,703 → 15,338 (+226%)	35,455 → 36,813 (+3.8%)

Laravel 13 project has JS/TS frontend code (hence non-zero baseline CALLS), but INHERITS was still 0→49 — Filament resource inheritance chains now correctly detected.

All edges spot-checked for accuracy — Route→Controller mappings, Eloquent relationships, Filament resource inheritance, and Blade directives all correspond to real code relationships.

Changes

Phase 1 — PHP infrastructure fix (parser.py)

• _get_call_name(): PHP-specific branches for 4 call expression types (function_call_expression, member_call_expression, scoped_call_expression, object_creation_expression)
• _get_bases(): PHP branch for base_clause (extends) + class_interface_clause (implements)
• _extract_import(): PHP branch handling simple, grouped (use Foo\{A, B}), and aliased imports
• _CLASS_TYPES["php"]: add trait_declaration, enum_declaration
• _CALL_TYPES["php"]: add scoped_call_expression, object_creation_expression

Phase 2 — Entry points + Blade detection

• flows.py: _LANG_ENTRY_NAME_PATTERNS dict for language-scoped patterns; _matches_entry_name() accepts optional language parameter
• parser.py: detect_language() checks .blade.php compound extension before generic suffix lookup

Phase 3 — Laravel semantic edges (parser.py)

• _extract_php_constructs(): Route definitions (Route::get('/path', [Controller::class, 'method'])) → CALLS edge to controller method
• Detect Eloquent relationships (hasMany, belongsTo, etc. — 11 methods) → REFERENCES edge to target model
• _php_class_from_class_access(): handles both short (Post::class) and FQCN (\App\Models\Post::class) forms

Phase 4 — Blade templates + PSR-4 (parser.py)

• _parse_blade(): regex-based extraction of @extends, @include, @component, @livewire as IMPORTS_FROM / REFERENCES edges
• _find_php_composer_psr4(): resolve namespaces to file paths via composer.json autoload PSR-4 mappings with caching

Docs (README.md)

• Update flow detection limitation to include PHP/Laravel
• Add "Framework-aware parsing" row to features table

Test plan

• 26 new test methods across test_multilang.py (TestPHPParsing: 14, TestLaravelParsing: 5, TestBladeParsing: 6) and test_flows.py (1)
• 761 total tests pass, 0 regressions (2 pre-existing async test failures unrelated to this PR)
• ruff check clean
• Verified on real Laravel 9 project — CALLS 0→35k, INHERITS 0→346
• Verified on real Laravel 12 project — HasMiddleware, PHP 8.1 Enums, Eloquent relationships
• Verified on real Laravel 13 project — Filament resources, Route→Controller, INHERITS 0→49
• Non-PHP languages unaffected — all PHP-specific code gated by language == "php" or in PHP-only methods

🤖 Generated with Claude Code

[tirth8205]

This PR now has merge conflicts with main after recent merges to parser.py and related files. Could you rebase on the latest main?

[Minidoracat]

Rebased onto latest main (5360a6d). Resolved conflicts in code_review_graph/parser.py:

• PHP call kinds: unioned both lists so nullsafe_member_call_expression (upstream Fix PHP CALL extraction: add support for method, static, and unqualified function calls #297 #298) and object_creation_expression (this PR) coexist.
• detect_language: checked compound extension (.blade.php) first, then delegated to the new extension-then-shebang lookup added by feat: .ksh extension + shebang-based language detection for extension-less scripts (#235, #237) #276.
• Import resolution: Java import-to-file (upstream feat(java): resolve Java imports to file paths #280) and PHP PSR-4 (this PR) now live as separate elif language == … branches.
• Import extraction: GDScript extends clause (upstream feat: add GDScript (Godot) as a supported language #316) and PHP use … declarations coexist.

On top of the textual rebase, one additional test-only commit fix(tests): reconcile with upstream #298 PHP CALL format:

• TestPHPParsing::test_finds_static_calls: upstream Fix PHP CALL extraction: add support for method, static, and unqualified function calls #297 #298 keeps :: as the scoped-call separator (User::find) rather than normalizing to . — assertion updated. Functionality is preserved, just the edge-target format changed.
• TestPHPParsing::test_finds_calls_comprehensive: upstream Fix PHP CALL extraction: add support for method, static, and unqualified function calls #297 #298 added a thorough call-extraction test that Git auto-merged into TestBladeParsing (wrong class — its setup parses sample.blade.php, so assertions on sqlQuery/xl/text failed). Moved back into TestPHPParsing and renamed to avoid collision with the existing minimal test_finds_calls.
• Removed unused sources local in test_finds_inheritance (F841).

Verified:

• uv run pytest tests/ — 907 passed, 2 xpassed
• uv run ruff check on the files this PR touches — clean
• uv run python -c 'from code_review_graph import parser; print("ok")' — imports clean

Ready for another look.

[Minidoracat]

Pushed another round:

1. Re-rebased onto main (d7e61d8) after the recent merges (feat(embeddings): OpenAI-compatible embedding provider #321, fix: hooks.json schema validation fails with "Expected array, but received undefined" #288, fix: merge-based hook installation preserves existing user hooks #203, fix: CLI build/update/watch now run post-processing (signatures, FTS, flows, communities) #98, docs: add MCP tools documentation for code-review-graph #306, fix: resolve Windows stdio JSON parsing errors and add Claude configuration docs #292). Clean this time — no conflicts.
2. Codex post-rebase review caught that _get_call_name() had two PHP blocks: upstream Fix PHP CALL extraction: add support for method, static, and unqualified function calls #297 #298's block (function/member/nullsafe/scoped) returns first, making the feat-branch block unreachable for those node types and leaving only object_creation_expression live — plus the two blocks disagreed on scoped-call formatting (:: vs .). Merged object_creation_expression into the upstream block with consistent _normalize_php_name handling and removed the shadowed duplicate (commit refactor(parser): remove shadowed PHP branch in _get_call_name).

uv run pytest tests/ — 973 passed, 2 xpassed.
uv run ruff check on touched files — clean.

[Minidoracat]

@tirth8205 heads up — CI is failing here (and on all other open PRs, and on main itself since 6d80d1a) because commit cc82d3f ("chore: resolve merge conflicts with main") accidentally added macOS Finder-style duplicate files — the filename 2.py / filename 3.py pattern Finder generates when you copy into a directory that already has that name. It looks like these slipped in during a manual conflict resolution on that branch, and the same pattern has been repeated in the subsequent chore: resolve merge conflicts commits on main (d1611e4, dfcbcc4, 186fa3c, cb9d25a).

Affected files:

• Python modules (fail ruff N999 "Invalid module name" because of the space): code_review_graph/analysis 2.py, enrich 2.py, enrich 3.py, exports 2.py, exports 3.py, graph_diff 2.py, jedi_resolver 2.py, memory 2.py, memory 3.py, token_benchmark 2.py (~2,800 untested lines)
• Binary coverage artifacts: .coverage 2, .coverage 3
• Doc duplicates: AGENTS 2.md, GEMINI 2.md, README.ja-JP 2.md, README.ja-JP 3.md, README.zh-CN 2.md
• Test fixtures: tests/fixtures/MarkdownMsg 2.tsx, sample 2.ex

Net effect on CI:

• lint: 10 × N999 Invalid module name failures
• test (3.10–3.13): coverage drops to 60% because the duplicated Python files are untracked code — fails --cov-fail-under=65

My branch touches none of these; once they're removed from main this PR's CI will go green on the next run (no rebase needed on my side — the bad files are in my tree only because they're on main). Happy to open a separate cleanup PR if that's easier than patching main directly.