[BUG] workspace scripts do not propagate exit codes

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Minimal Setup

package.json

{
  "workspaces": ["child"],
  "scripts": {
    "exit-100": "exit 100"
  }
}

child/package.json

{
  "scripts": {
    "exit-100": "exit 100"
  }
}

Repro Steps

Behavior in root:

npm run exit-100
echo $? # correctly returns 100

Behavior in workspace:

npm run exit-100 --workspace child
echo $? # incorrectly returns 1

# OR

cd child
npm run exit-100
echo $? # incorrectly returns 1

Also note, if you amend the root package.json to remove the workspaces and then repeat those final steps:

cd child
npm run exit-100
echo $? # (now without workspaces config in the level above) correctly returns 100

Environment

• npm: 9.5.0
• Node.js: 18.15.0
• OS Name: macOS 13.3.1

Start by reproducing the workspace commands from the issue with npm 9.5.0 and Node.js 18.15.0, comparing root and child execution. Trace the workspace script execution and exit-status handling in the npm CLI entry points. Done means a child script exiting with 100 propagates exit code 100 both from the workspace flag and from the child directory.