Correctly detect all exceptions in method body

Author: AJenbo

docs/todo.md

@@ -21,9 +21,13 @@ within the same impact tier.
 
 ## Sprint 3 — Bug fixes
 
-| #   | Item                                              | Impact | Effort |
-| --- | ------------------------------------------------- | ------ | ------ |
-| B13 | [Stop showing dummy symbols in hover](todo/bugs.md#b13--hover-shows-dummy-symbols) | Medium | Low    |
+| #   | Item                                                                                                              | Impact | Effort |
+| --- | ----------------------------------------------------------------------------------------------------------------- | ------ | ------ |
+| B13 | [Stop showing dummy symbols in hover](todo/bugs.md#b13--hover-shows-dummy-symbols)                                | Medium | Low    |
+| B14 | [Add @throws action inserts misaligned docblock](todo/bugs.md#b14--add-throws-action-inserts-misaligned-docblock) | Medium | Low    |
+| B15 | [Completion after `->()` should not insert parentheses](todo/bugs.md#b15--completion-after---should-not-insert-parentheses) | Medium | Low    |
+| B16 | [PHPStan stale-diagnostic clearing is overly aggressive](todo/bugs.md#b16--phpstan-stale-diagnostic-clearing-is-overly-aggressive) | Medium | Medium |
+|     | **Release 0.6.0**                                                                                                 |        |        |
 
 ## Sprint 4 — Refactoring toolkit
 
@@ -35,6 +39,7 @@ within the same impact tier.
 | A4  | [Inline variable](todo/actions.md#a4-inline-variable)                              | Medium | Medium |
 | A6  | [Generate constructor](todo/actions.md#a6-generate-constructor)                    | Medium | Medium |
 | A7  | [Promote constructor parameter](todo/actions.md#a7-promote-constructor-parameter)  | Medium | Low    |
+|     | **Release 0.7.0**                                                                  |        |        |
 
 ## Sprint 5 — Polish for office adoption
 
@@ -48,6 +53,7 @@ within the same impact tier.
 | D1  | [Unknown class diagnostic](todo/diagnostics.md#d1-unknown-class-diagnostic)   | Medium      | Medium |
 | D3  | [Unknown method / property diagnostic](todo/diagnostics.md#d3-unknown-member) | Medium      | Medium |
 | D4  | [Unused variable warning](todo/diagnostics.md#d4-unused-variable)             | Medium      | Medium |
+|     | **Release 0.8.0**                                                             |             |        |
 
 ## Sprint 6 — Type intelligence depth
 

docs/todo/bugs.md

@@ -71,3 +71,67 @@ output.
 
 **Fix:** Filter out dummy symbols before building the hover response
 so only real, user-relevant information is shown.
+
+---
+
+## B14 — Add `@throws` action inserts misaligned docblock
+
+| Impact | Effort |
+| ------ | ------ |
+| Medium | Low    |
+
+When the "Add `@throws`" code action creates a new docblock (no
+existing docblock is present), the inserted block is not aligned with
+the function/method it annotates. The opening `/**` and closing `*/`
+use incorrect indentation, producing code that is visually broken and
+fails style checks.
+
+**Fix:** Detect the indentation of the target function/method line and
+use it as the base indentation for every line of the generated
+docblock (`/**`, ` * @throws …`, ` */`).
+
+---
+
+## B15 — Completion after `->|()` should not insert parentheses
+
+| Impact | Effort |
+| ------ | ------ |
+| Medium | Low    |
+
+When completing a method call where the cursor is immediately before
+existing parentheses (e.g. `$obj->|()` with the cursor at `|`), the
+completion item still inserts its own parentheses, producing
+`$obj->method()()`. The completion engine should detect that
+parentheses already follow the cursor and suppress the snippet
+suffix in that case.
+
+**Fix:** Before attaching the `()` (or `($1)`) snippet suffix to a
+callable completion item, check whether the character immediately
+after the completion range is `(`. If so, emit a plain text insert
+without parentheses.
+
+---
+
+## B16 — PHPStan stale-diagnostic clearing is overly aggressive
+
+| Impact | Effort |
+| ------ | ------ |
+| Medium | Medium |
+
+`is_stale_phpstan_diagnostic()` in `src/diagnostics/mod.rs` sometimes
+clears diagnostics that are still valid. For example, adding a
+`@throws` tag for one exception may cause an unrelated diagnostic on
+a nearby line to be treated as stale if the simple substring check
+matches text that happens to appear elsewhere in the file. The
+heuristic-based approach (checking whether a short name appears after
+`@throws` anywhere in the file content) has false positives.
+
+**Fix:** Audit each branch of `is_stale_phpstan_diagnostic()` and
+tighten the checks:
+
+1. Scope `content_has_throws_tag` to the docblock enclosing the
+   diagnostic line rather than searching the entire file.
+2. For `@phpstan-ignore` coverage, verify that the ignore comment is
+   on the exact diagnostic line (or the line immediately before it),
+   not just any line in the file.
+3. Add regression tests for the false-positive scenarios.