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

Inline comments:
In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/providers/CompletionProvider.java`:
- Line 283: The code computes scriptVariant via
documentContext.getScriptVariantLanguage() but filterNamesByLanguage(...) still
uses configuration.getLanguage(); update the call site so that
filterNamesByLanguage and any helper isInConfiguredLanguage reference the
scriptVariant (the per-document script variant) instead of
configuration.getLanguage(), i.e. pass or use scriptVariant where language
selection for no-dot alias filtering occurs (look around the variable
scriptVariant, filterNamesByLanguage(...), and isInConfiguredLanguage to
replace/globalize the language source).

In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/providers/SignatureHelpProvider.java`:
- Around line 574-577: argCount currently counts all parser-produced callParam
nodes including empty ones; update argCount(DoCallContext doCall) to iterate
over paramList.callParam() and count only those entries that are non-empty
(e.g., filter out params whose getText().trim().isEmpty() or that lack an
expression child) so signature help uses the true number of provided arguments;
modify the method to return 0 when callParamList is null and otherwise return
the count of callParam elements passing the non-empty check.

In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/types/model/ParameterDescriptor.java`:
- Around line 69-72: The compat constructor for ParameterDescriptor can NPE
because it calls bilingualName.isEmpty() before record-level normalization;
change that check to be null-safe (e.g., treat null the same as empty) so the
ternary becomes (bilingualName == null || bilingualName.isEmpty()) ?
BilingualString.of(name) : bilingualName and keep the rest of the parameters the
same (types, optional, BilingualString.of(description), defaultValue) to ensure
null bilingualName is handled consistently in the constructor.

In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/types/registry/ConfigurationTypesProvider.java`:
- Around line 473-476: The helper registerWithAlias currently registers an empty
English alias when callers pass ""—prevent this by checking the alias string
before calling typeRegistry.registerConfigurationTypeAlias: in
registerWithAlias(String qualifiedRu, String qualifiedEn) only call
typeRegistry.registerConfigurationTypeAlias(qualifiedEn, ref) if qualifiedEn is
not null and not blank (e.g., !qualifiedEn.isBlank() or !qualifiedEn.isEmpty()
after trimming); leave the original
typeRegistry.registerConfigurationType(qualifiedRu) behavior unchanged.

In
`@src/main/resources/com/github/_1c_syntax/bsl/languageserver/types/registry/builtin-platform-types.json`:
- Around line 433-436: The overload for "Скопировать/Copy" only includes Russian
parameter names ("Строки", "Колонки"); add English equivalents by supplying
nameEn for the signature and for each parameter in that overload (use nameEn:
"Rows" and nameEn: "Columns"), or replace the parameter objects to include both
nameRu and nameEn fields so the parser can show English names in fallback mode;
update the parameters array in the existing overload entry (the objects
containing "Строки" and "Колонки") to include nameEn properties accordingly.

---

Outside diff comments:
In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/types/registry/BuiltinPlatformTypesProvider.java`:
- Around line 435-463: readSignatures currently only reads mono "description"
and so always produces a single-language signature; update it to parse
"descriptionRu" and "descriptionEn" (using the existing stringField helper
similar to pNameRu/pNameEn) and construct a BilingualString for the signature
description, then pass that bilingual description into the SignatureDescriptor
(use the overload/constructor that accepts a BilingualString or setDescription
accordingly) instead of the mono description variable so both Russian and
English signature help are emitted.

In
`@src/main/java/com/github/_1c_syntax/bsl/languageserver/types/util/SignatureSelection.java`:
- Around line 51-68: pickIndexByArity currently rejects calls that exceed the
fixed total parameter count even when a signature is variadic; update the logic
to detect a variadic parameter (e.g., check the last parameter's variadic flag
via parameter.variadic() or similar) and allow argCount >= required when the
signature is variadic (treat total as unbounded in that case). Adjust the
matching condition in pickIndexByArity to accept signatures when (argCount >=
required && (argCount <= total || hasVariadic)), and ensure the fallback
assignment (fallback = i when total == argCount) does not override a variadic
match—only use fallback for non-variadic exact-total matches.