Add Terminal to the Dock - #3808

Summary

Adds a Terminal tool to the Playground Dock for working interactively with the currently active Playground.

This was reimplemented on top of the new Dock UI from trunk. Instead of adding a tab to the old site manager sidebar, Terminal is now a first-class Dock destination alongside Database, Files, and Logs.

The terminal provides separate PHP and WP-CLI sessions, persistent command history, execution timing, concise error reporting, and PHP syntax highlighting.

Screenshots

How It Works

PHP mode loads WordPress and evaluates each submitted snippet independently. Snippets may omit the opening <?php tag, and incomplete code remains in the editor so it can be completed and run again. The input reuses Playground's CodeMirror editor in plain-PHP mode for syntax highlighting.

WP-CLI mode downloads the WP-CLI executable on first use when needed, then runs each command directly against the connected Playground with the existing wpCLI() client helper. Commands may be entered with or without the leading wp; the input is normalized before execution.

The Blueprint WP-CLI launcher now uses a fail-fast STDIN stream. Commands that attempt to read interactive input abort before treating missing input as an empty value and mutating WordPress.

Developer Experience

• PHP and WP-CLI have independent tabs, drafts, and command histories.
• Command history persists across browser sessions in localStorage and can be cleared per mode.
• Previous and next controls navigate results; edited input is protected by an inline discard/cancel confirmation.
• Every completed command displays its wall-clock execution time.
• Result actions remain visible in a sticky header while long output scrolls.
• PHP parse/runtime errors and WP-CLI output are normalized for terminal display.
• PHP input has syntax highlighting, line numbers, and Ctrl/Cmd+Enter execution.
• The input and Run button remain disabled with an inline progress state while WordPress boots.
• Non-terminating WP-CLI commands such as shell and server are rejected.

Compatibility

The wp-cli Blueprint step now rejects commands that read from STDIN. Blueprint WP-CLI commands must provide all required arguments explicitly. This changes the previous behavior where unavailable STDIN could be interpreted as an empty value and cause an unintended mutation.

Testing

• npm run format:uncommitted
• npm exec nx test playground-website (385 tests passed)
• WP-CLI Blueprint step tests (6 tests passed, including verification that a failed STDIN read does not mutate the option)
• npm exec nx run playground-website:typecheck
• npm exec nx run playground-blueprints:typecheck
• npm exec nx lint playground-website
• npm exec nx lint playground-blueprints
• npm exec nx -- run-many -t typecheck -p playground-components playground-website
• npm exec nx -- run-many -t lint -p playground-components playground-website

The broader Blueprint test run also encountered six unrelated network-dependent translation fetch failures in set-site-language.spec.ts.