fix(server): honor the debug parameter in the STP trigger macros

[sasjs-dev]

Fixes the one surviving review finding from #382, and closes it as superseded.

What happened to #382

Its macro, ms_triggerstp, landed on main via #442 in finished form - together with the test file the reviewer asked for. I verified each of the reviewer's 7 findings against main's version:

Finding	Status on main
1. &boundary never defined	fixed - %let boundary=%mf_getuniquename();
2. &outref never defined	fixed - %let outref=%mf_getuniquefileref();
3. orphaned DATA step (data work.%mf_getuniquename(); ... input with no run;)	fixed - replaced with libname &libref JSON parsing
4. &outlogds undefined	fixed - the parameter is gone entirely
6. @brief said /code/trigger, URL used /stp/trigger	fixed - both say /SASjsApi/stp/trigger
7. outds declared but never written	fixed - proc append base=&outds
5. debug= accepted but ignored, URL hardcodes _debug=131	still present on main

Finding 5 is what this PR fixes - in both macros that have it.

The fix

ms_runstp and ms_triggerstp both take debug=, documented as the _debug value to send, and both hardcoded _debug=131 in the URL. ms_testservice forwards debug=&debug to ms_runstp, so its callers were silently ignored too:

ms_runstp        url now uses _debug=&debug
ms_triggerstp    url now uses _debug=&debug
ms_testservice   signature default 0 -> 131, matching its documented default

Why the default stays 131 and existing callers see no change: the server appends the session log to the response only when _debug is 131 or above (isDebugOn in sasjs/server), and ms_runstp's outlogds chopping depends on the log separator being present. So 131 is load-bearing for the documented outlogds contract, not an arbitrary constant.

The one caller passing a non-default value - ms_testservice's own test, with debug=log - is corrected to use the default. The server validates _debug as a number (Joi.number() in triggerProgramValidation), so log was working only because the parameter was ignored; the macro's own doc header already claimed 131 as the default while its signature said 0.

Also picked up by the regeneration

all.sas is CI-generated, so build.py was rerun. That surfaced a pre-existing drift: #456 changed proc sql to proc sql noprint in mp_jsonout.sas, which is embedded into mm_createwebservice.sas and ms_createwebservice.sas inside their /* WEBOUT BEGIN */ blocks - and the regeneration had not been run for those two files. The diff includes that propagation.

Verified

• sasjs lint exit 0, 0 errors; warnings identical to main (bisected: same 3 mp_abort header warnings on a clean main checkout)
• build.py rerun; all.sas carries the fix at both URL sites

[github-actions]

🎉 This PR is included in version 5.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀