Run the web app: package.json scripts beside the app's schemes (roadmap 5.3) - #3

…age product or a web app's package.json script. The scheme menu (and Choose Scheme…, ⌃0; Next / Previous Scheme step through them too) has a section per web app, named for its folder ("web"), listing its scripts in package.json's order; choosing one makes ⌘R run it, the toolbar reads "dev › web (pnpm)" and the destination menu says a script has no run destination instead of listing simulators. A plain folder with a package.json is runnable this way (its first script chosen) instead of "No Scheme". Build, Test, Profile and Archive keep the project's scheme. The choice comes back with the session (ProjectSession::run_script); Edit Scheme… with a script chosen opens package.json at it. A script runs with the package manager its packageManager field or lockfile implies (bun.lock/bun.lockb, pnpm-lock.yaml, yarn.lock, package-lock.json, in its folder or a folder above it in the project; npm otherwise), as `exec <pm> run <script>` in its folder, with its node_modules/.bin (and a monorepo's above it) before the login shell's PATH, on a PTY in a terminal of the debug area's Terminal tab named "web: dev", shown without taking the keyboard; running it again ends the earlier run and takes its terminal's place, and run terminals aren't restored as shells. It runs beside the scheme's build and app: running the app doesn't touch a dev server and running a script doesn't stop the app. Stop (⌘.) ends the chosen target's run: a running chosen script's, otherwise the build, app and debugger, and only when none of those is going, the scripts; closing a run's terminal ends it too. The activity view says "Running web: dev" when a script is what's going on, and shows running scripts' URLs as chips that open them again. What a script prints is read as it comes: the PTY alacritty_terminal reads is wrapped (TapPty, through the polling crate's types it registers with, already built) so its output also goes, as plain lines (terminal/lines.rs: ANSI stripped, carriage returns and moves to column 1 resolved), to the workspace; build/web.rs takes the first local URL (Vite's Local:, Next, webpack-dev-server's Loopback:, astro dev, any http://localhost:NNNN or 127.0.0.1; 0.0.0.0 and [::] made localhost) and opens it in the browser once per window (web.open_dev_server_url, on by default; ZCODE_OPEN_URL_LOG records it instead), and reads errors and warnings as build issues: tsc's file(line,col) and pretty file:line:col - error TS…, esbuild's ✘ [ERROR] with its location on a later line, Vite's Internal server error with the path inline or a File: line below (or the importer of a failed import), ESLint's stylish and unix formats, and path:line:col: error:/ERROR:, relative paths against the web app's folder. They join the Issue navigator and the editors' inline diagnostics until the script runs again, clear when a watcher starts over (tsc's File change detected, Vite's hmr update and page reload), and a run that fails adds its exit code (127: the package manager isn't on the PATH). Terminals now fork with no signals blocked: GCD's threads block SIGHUP, a child inherits that, and a program that doesn't reset it (a dev server, unlike a shell) never got the hang-up, so quitting zcode left it running under launchd; Stop also SIGKILLs whatever of the group outlives the leader by a second. MCP: XcodeListSchemes lists the scripts after the schemes ("web: dev") with run_targets giving each one's kind (xcode_scheme, swift_package_product, web_script, with its folder, command and package manager); XcodeSwitchScheme and the tools' scheme argument take them; RunProject runs a chosen script and returns its first output, URL and errors after wait_seconds; StopProject takes an optional scheme; GetConsoleOutput lists running scripts and reads one's output with scheme. dump has web and scheme_menu; control commands scheme <name> and web-url <n>. Unit tests: discovery (order, node_modules and script-less files skipped), the package manager from lockfiles, packageManager and a monorepo's root, PATH folders, URLs, every issue format and a watcher starting over, line splitting, a tapped PTY with the asked-for PATH, a SIGHUP-ignoring child ended by Stop, no signals blocked in the child. e2e (Running web apps, a copy of HelloWeb with a fake pnpm and npm on PATH and a fake Vite in node_modules/.bin that prints its URL in Vite's colors and a TypeScript error, then serves with a child): the scheme menu's web section and pnpm from the lockfile; ⌘R running pnpm run dev in web/ with node_modules/.bin first on PATH in a terminal named web: dev while the package's app keeps running; the URL opened once and again from the activity view; the error at counter.ts:3:11 in the Issue navigator and the editor; the app run again and stopped with the dev server untouched; ⌘. ending the dev server and its child; MCP's run targets, RunProject, GetConsoleOutput and StopProject on the script; the choice after a relaunch and quitting ending its run; a plain folder with npm, a failing script's error and exit code, and ⌘. stopping what runs. Docs: roadmap 5.3 ✅, a parity row, features, MCP, limitations, testing, architecture, README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>