runtime: return false from include() when the file fails, instead of rethrowing

[ResurrectedTrader]

d2bs behaviour

Script::Include (Script.cpp) compiles and executes the file. When either step fails it calls JS_ReportPendingException, which reports the error and clears it, and returns false. my_include (JSCore.cpp) hands that bool back to the script. A failing include never throws into the caller.

d2bsng before

Script::Include reported the exception, then called tryCatch.ReThrow() in both the compile-failure and the run-failure paths. The error went up into the calling script, and include() threw instead of returning false.

Fix

Drop both ReThrow() calls. The error is still reported through ReportException, which includes the QuitOnError handling, and include() returns false, as in d2bs. The binding's @returns doc now says so.

kolbot usage restored

libs/core/Loader.js loads each configured script with if (!include("scripts/" + script + ".js")) { Misc.errorReport(...); continue; }. With the rethrow, one broken script file threw out of the loader loop and ended the run. Now it is reported and skipped.

Not live-tested. It builds, and the unit tests and the format check pass.

🤖 Generated with Claude Code

[ResurrectedTrader]

Can we put this behind compatibility flag. Default to on, feels like a silent failure is a sad behaviour

[ResurrectedTrader]

Done: the behaviour is now the includeReturnsFalse compatibility flag, on by default. On: a failing include (compile error or a throw) is reported and include() returns false, as d2bs did. Off (Compatibility.set("includeReturnsFalse", false)): the error is reported and rethrown into the caller, as before this PR. It is checked live in Script::Include, documented in the flag catalog and in docs/compatibility.md, and the include() doc mentions it. Rebased onto main.