Core tests fail on Adobe ColdFusion: `DirectoryCreate()` called with unsupported arguments in `BrowserTest.cfc`

[zainforbjs]

Describe the bug
When running the Wheels test suite on Adobe ColdFusion, the tests fail with the following error:

Parameter validation error for the DIRECTORYCREATE function.
The function takes 1 parameter.

The error occurs in:
/vendor/wheels/wheelstest/BrowserTest.cfc: line 265

This indicates that DirectoryCreate() is being called with additional arguments that are supported in Lucee but not in Adobe ColdFusion.

To Reproduce
Steps to reproduce the behavior:

1. Run the Wheels test suite on Adobe ColdFusion.
2. Execute tests that use BrowserTest.cfc.
3. Observe the DirectoryCreate() parameter validation error.

Expected behavior
The test suite should run successfully on Adobe ColdFusion without function compatibility errors.

Screenshots

Desktop:

• OS: Any
• CFML Engine: Adobe Coldfusion

[wheels-bot]

Wheels Bot — Triage

Classified as bug.

Suspected layer

testing (browser-test infrastructure) — see .ai/wheels/testing/ for canonical patterns. The failing call lives in vendor/wheels/wheelstest/BrowserTest.cfc rather than user-facing test code, so the fix targets the framework's browser test base class.

Fix sketch

vendor/wheels/wheelstest/BrowserTest.cfc:265 invokes directoryCreate(artifactDir, true) positionally. Adobe ColdFusion's positional signature is directoryCreate(path, mode) where mode is a string permission like "777" — passing the boolean true trips parameter validation. The fix is to use the named-argument form directoryCreate(artifactDir, createPath=true), which works on Lucee, Adobe CF, and BoxLang. One-line change, no other call sites need touching.

Confidence: medium

Fix is mechanical and the layer is unambiguous, but the medium cap applies because this is a cross-engine compatibility issue (Lucee accepts the positional boolean, Adobe does not) and the auto-downgrade rule for cross-engine concerns fired.

<!-- wheels-bot:triage:2614 -->
<!-- wheels-bot:triage-class:bug -->

[bpamiri]

Draft PR opened: #2616

The fix routes both BrowserTest.cfc:265 (the call site this issue called out) and the matching McpServer.cfc:1115 through java.io.File.mkdirs() — the same canonical engine-agnostic workaround already used by ManifestCache.$ensureDir from #2567. The PR is TDD-first: failing spec at vendor/wheels/tests/specs/wheelstest/BrowserTestArtifactDirSpec.cfc flips from err=2 to pass=2 once the $ensureArtifactDir helper lands on BrowserTest. Local core suite stays at 3463 pass / 0 fail (12 unrelated pre-existing connection-refused errors in BrowserLogin/BrowserRouteSpec).