Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

src/main/java/com/github/_1c_syntax/bsl/languageserver/inlayhints/PlatformMethodCallInlayHintCollector.java (1)

53-56: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Javadoc describes a calling scenario instead of the class contract.

"Коллектор используется единым {@link MethodCallInlayHintSupplier}" documents who invokes this class rather than what it does/contracts.

As per path instructions for src/main/java/**/*.java: "Javadoc should describe the contract of a class or method (what it does, inputs/outputs, invariants, side effects), not calling scenarios or who invokes it."

📝 Suggested rewording

- * Коллектор используется единым {`@link` MethodCallInlayHintSupplier} и отвечает за
- * резолв вызова; построение меток и tooltip делегируется
+ * Резолвит вызов метода/конструктора через систему типов и делегирует построение
+ * меток и tooltip
   * {`@link` PlatformMethodCallHintRenderer}. Резолв члена выполняется через
   * {`@link` TypeService#memberAt}, что покрывает три кейса:

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/inlayhints/PlatformMethodCallInlayHintCollector.java`
around lines 53 - 56, Update the Javadoc for
PlatformMethodCallInlayHintCollector so it describes the class’s responsibility
and contract, not who uses it or the calling scenario. Reword the comment to
focus on what the collector does: resolving method-call targets, building the
inlay hint data, and delegating rendering details to
PlatformMethodCallHintRenderer, while keeping the TypeService#memberAt behavior
description if relevant.

Source: Coding guidelines

src/test/java/com/github/_1c_syntax/bsl/languageserver/inlayhints/PlatformMethodCallInlayHintCollectorTest.java (1)

58-59: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Field name supplier is stale after the Supplier→Collector rename.

The field type was retyped to PlatformMethodCallInlayHintCollector, but the variable is still named supplier, which is confusing given this PR's whole point is splitting the old supplier into collectors + a separate aggregating MethodCallInlayHintSupplier.

✏️ Suggested rename

-  `@Autowired`
-  private PlatformMethodCallInlayHintCollector supplier;
+  `@Autowired`
+  private PlatformMethodCallInlayHintCollector collector;

(and update all supplier.getInlayHints(...) call sites in this file accordingly)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@src/test/java/com/github/_1c_syntax/bsl/languageserver/inlayhints/PlatformMethodCallInlayHintCollectorTest.java`
around lines 58 - 59, The test field name `supplier` in
`PlatformMethodCallInlayHintCollectorTest` is stale after the Supplier→Collector
rename. Rename the injected `PlatformMethodCallInlayHintCollector` field to a
collector-appropriate name and update all `supplier.getInlayHints(...)` call
sites in this test to use the new identifier so the test matches the refactored
`PlatformMethodCallInlayHintCollector`/`MethodCallInlayHintSupplier` split.