Issue Summary:

forge tunnel --debug breaks all backend function invocations. The resolver fails to load, so breakpoints never bind and the app's backend does not run. Reproduced on Forge CLI 13.4.0 with a stock jira-full-page-ui-kit app, following the documented VS Code debugging guide. Affects both nodejs22.x and nodejs24.x runtimes.

Steps to Reproduce

1. forge create -t jira-full-page-ui-kit
2. forge deploy and forge install
3. Add .vscode/launch.json per the VS Code debugging docs
4. forge tunnel --debug --debugFunctionHandlers index.handler --debugStartingPort 9229
5. Set a breakpoint in src/resolvers/index.js
6. Open the app in Jira

Expected Results

The resolver executes and the breakpoint is hit.

Actual Results

The breakpoint shows "Unbound breakpoint" and is never hit. The resolver does not run — the tunnel logs:

invocation: 47bd153b02b84bfc9d3c57cdf5770006 index.handler
ERROR   Error: Cannot find module '<app>/.forge/tunnel-output/index.js'

The CLI still reports ✔ Functions bundled and Debugger attached, so the failure is silent until the first invocation.

Workaround

Downgrade to Forge CLI 13.3.0 with

npm install --global @forge/cli@13.3.0

will allow you to run the VS Code debugger.