[Auto] [Update] Document JS type error preference and extended Diagnostic Report coverage (#551)

Co-authored-by: 4ian <1280130+4ian@users.noreply.github.com>

Author: github-actions[bot]

automated_updates_data.json

@@ -1,5 +1,5 @@
 {
-  "last_automated_updates_commit": "50afd05049bc87c288dc4c7ccbce55388522fe53",
+  "last_automated_updates_commit": "9cd06e4e71f45c80c1b566bd918b410e28a7dce1",
   "last_improved_things": [
     {
       "date": "2026-02-16",

docs/gdevelop5/events/js-code/index.md

@@ -101,6 +101,10 @@ Equivalent events would be:
 
 By writing the **annotation** `/** @type {gdjs.XXX} */` just before the declaration of a variable in JavaScript, you let the code editor know that the variable has the type gdjs.XXX. The editor will be able to assist you by providing **autocompletion** while you type (or when you hover over a word).
 
+!!! tip
+
+    You can enable **type error highlighting** in the code editor by going to **Preferences** and toggling "Show type errors in JavaScript events" (a restart is required). This helps catch type mismatches as you write code.
+
 Most of the time annotations are not needed. The methods that you are using are already setup with type annotations. But when you use a list of objects, you may want to access this object specific method (for example, methods to modify the animation of a sprite object). In this case, you could write `/** @type {gdjs.SpriteRuntimeObject} */`.
 
 If you don't do this, the code will still work, but the editor will only be able to provide you with the methods of [gdjs.RuntimeObject](https://docs.gdevelop.io/GDJS%20Runtime%20Documentation/classes/gdjs.RuntimeObject.html) (the base class).

docs/gdevelop5/interface/events-editor/index.md

@@ -143,4 +143,4 @@ You can open the diagnostic report by:
 - Pressing **F7** (default keyboard shortcut)
 - Opening the command palette (Ctrl+P) and searching for "diagnostic report"
 
-The diagnostic report scans your project and lists all detected issues. You can click on any error in the report to navigate directly to the problematic event, making it easier to fix issues quickly.
+The diagnostic report scans your project — including scene events and extension function events — and lists all detected issues. You can click on any error in the report to navigate directly to the problematic event, making it easier to fix issues quickly.