Update README.md

Author: AJenbo

README.md

@@ -14,24 +14,26 @@ PHPantom focuses on completion and go-to-definition and aims to do them really w
 | Completion | ✅ | ✅ | ✅ | ✅ | ✅ |
 | Auto-import | ✅ | 💰 | ✅ | ✅ | ✅ |
 | Go-to-definition | ✅ | ✅ | ✅ | ✅ | ✅ |
-| Go-to-implementation | ✅ | ✅ | ✅ | ✅ | ✅ |
-| `@mixin` completion | ✅ | 💰 | ✅ | ✅ | ✅ |
-| `@phpstan-assert` narrowing | ✅ | ❌ | ✅ | ❌ | ⚠️ partial |
-| Conditional return types | ✅ | ❌ | ✅ | ❌ | ✅ |
-| Array shape inference | ✅ | ❌ | ✅ | ❌ | ✅ |
-| Object shape completion | ✅ | ❌ | ✅ | ❌ | ✅ |
-| `@phpstan-type` aliases | ✅ | ❌ | ✅ | ❌ | ✅ |
+| Go-to-implementation | ✅ | ✅ | ❌ | ✅ | ✅ |
+| `@mixin` completion | ✅ | 💰 | ✅ | ✅ | ⚠️ |
+| `@phpstan-assert` narrowing | ✅ | ❌ | ⚠️ | ❌ | ⚠️ |
+| Conditional return types | ✅ | ❌ | ✅ | ❌ | ⚠️ |
+| Array shape inference | ✅ | ❌ | ✅ | ❌ | ⚠️ |
+| Object shape completion | ✅ | ❌ | ✅ | ❌ | ⚠️ |
+| `@phpstan-type` aliases | ✅ | ❌ | ⚠️ | ❌ | ❌ |
 | Hover | ❌ | ✅ | ✅ | ✅ | ✅ |
 | Signature help | ❌ | ✅ | ✅ | ✅ | ✅ |
 | Find references | ❌ | ✅ | ✅ | ✅ | ✅ |
-| Diagnostics | ❌ | ✅ | ✅ | ⚠️ limited | ✅ |
+| Diagnostics | ❌ | ✅ | ✅ | ✅ | ✅ |
 | Rename / refactoring | ❌ | 💰 | ✅ | ✅ | ✅ |
 | Time to ready | **10 ms** | 1 min 25 s | 3 min 17 s | 15 min 39 s | 19 min 38 s |
 | RAM usage | **7 MB** | 520 MB | 3.9 GB | 498 MB | 2.0 GB |
 | Disk cache | **0** | 45 MB | 0 | 4.1 GB | 551 MB |
 
 <sub>Performance measured on a production codebase: 21K PHP files, 1.5M lines of code (vendor + application).</sub>
 
+> **Want to verify?** Open [`example.php`](example.php) in your editor and trigger completion at the marked locations. It exercises every feature in the table, including edge cases where tools diverge.
+
 ## Context-Aware Intelligence
 
 - **Smart PHPDoc completion.** `@throws` detects uncaught exceptions in the method body, including those propagated from called methods. `@param` pre-fills with the name and type from the signature. Tags are filtered to context: `@var` only in property docblocks, `@param` only when there are undocumented parameters. Already-documented tags aren't suggested again.

docs/todo.md

@@ -195,6 +195,41 @@ native hint is the only concrete type information available. This also
 applies to method return types that use bare template parameters without
 a concrete substitution available.
 
+### 23. Match-expression class-string not forwarded to conditional return types
+**Priority: Medium**
+
+When a variable is assigned a `::class` value through a `match` expression
+and then passed to a function whose return type depends on that argument
+(e.g. `@template T @param class-string<T> @return T`), the resolver cannot
+trace the class-string back through the match arms:
+
+```php
+$requestType = match ($typeName) {
+    'creditnotes' => GetCreditnotesRequest::class,
+    'orders'      => GetOrdersRequest::class,
+};
+$requestBody = app()->make($requestType);
+$requestBody->enabled();  // ← no completion
+```
+
+The resolver already handles direct `::class` arguments at the call site
+(e.g. `app()->make(GetCreditnotesRequest::class)`), but when the
+class-string is stored in an intermediate variable whose value comes from
+a match expression, the link is lost.
+
+Two pieces are needed:
+
+1. **Track class-string values from match arms.** When the RHS of an
+   assignment is a `match` expression and every arm returns a `Foo::class`
+   literal, record the set of possible class-string values on the
+   variable (e.g. `$requestType` holds
+   `GetCreditnotesRequest|GetOrdersRequest`).
+2. **Resolve class-string variables at call sites.** When a variable is
+   passed as an argument to a function with a `@template` + conditional
+   return type, look up the variable's class-string value(s) and use them
+   for template substitution, producing a union of the possible return
+   types.
+
 ---
 
 ## Go-to-Definition Gaps