Debug messages from KWin script (using console.log()) not present in the journal in spite of setting Full Debug in KDebugSettings

Help
1

I have Kröhnkite KWin script (GitHub - anametologin/krohnkite: A dynamic tiling extension for KWin) installed and activated.
As seen at krohnkite/res/main.qml at 0.9.8.2 · anametologin/krohnkite · GitHub it outputs log message using console.log():
console.log("KROHNKITE: starting the script");

However after setting KWin Scripting log level to Full Debug and removing *.debug=false rule from Custom Rules in KDebugSettings I don’t see this message (and other log messages from this script) in KSystemLog.

Originally I raised this problem at No log entries after turning "Debug new Windows" option on · Issue #94 · anametologin/krohnkite · GitHub
Related:
https://www.reddit.com/r/kde/comments/15jm7me/debug_printing_in_kwin_scripts/
https://www.reddit.com/r/Fedora/comments/15kiv2c/kde_or_fedora_issue_print_in_kwin_script_not/
Wayland and Plasmashell are spamming my syslog

[piotr@demon]~% kinfo
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Kernel Version: 6.11.3-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 14.8 GiB of RAM
Graphics Processor: AMD Radeon Graphics

2

Use print() in kwin scripts, not console.log().

3

In KWin scripting tutorial in KWin scripting basics’ Output section it’s written:

print(QVariant...): prints the provided arguments to stdout. Takes an arbitrary number of arguments. Comparable to console.log() which should be preferred in QML scripts.

I take it to mean that in QML script (and this is what we have here as the console.log() is used in the main.qml file) it’s console.log() which should be used, not print().