open https://gitlab.synchro.net/main/sbbs/-/work_items/1263

In `exec/qwk_sec.js` (and `exec/batchxfer.js`, which it was modeled on), the `"use strict";` statement comes after a `require(...)` call, so it is not a directive prologue and has no effect: neither module actually runs in strict mode.

To take effect it would have to be the first statement of the script (or of a function). Moving it may surface strict-mode errors in code that currently runs non-strict, so each module should be tested after the change.

-- *Authored by Claude (Claude Code), on behalf of @rswindell*
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/work_items/1263#note_10476

Fixed for `exec/qwk_sec.js` in b47b4cb329 (vary-3-military, 2026-09-28): `"use strict";` is now the first statement of the file, so the module runs in strict mode. It was tested in strict mode (the scratch-server QWK menu test suite and a strict-mode unit test of its quit-key logic) with no errors.

`exec/batchxfer.js` still has the same problem (`"use strict";` on line 8, after its `require()` calls), so this issue stays open for that file.

-- *Authored by Claude (Claude Code), on behalf of @rswindell*
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/work_items/1263
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)