Install/build logs run at maximum verbosity into renderer state that is never rendered

What happens

Install and build output is produced at maximum verbosity and then accumulated in renderer memory that is never shown, taxing the UI during the heaviest phases of setup.

Root cause

Several compounding pieces:

• npm log level defaults to verbose in both runners (src/install-runner.js:34, src/script-runner.js:80) — tens of MB of text, every byte crossing IPC. Audit and funding checks also add a full extra registry round trip after install.
• The renderer accumulates the entire install/build log into a state string on every chunk (src/renderer/index.jsx:825) — but that state is attached to no element; only the runtime log ref is rendered. Growing a string by concatenation per chunk re-renders the whole site row each time, purely to be discarded.
• Other log buffers (runtime logs, setup logs, terminal messages) are likewise unbounded, while the terminal itself already caps scrollback.
• Clone progress sends one IPC message per progress event (src/main.js:479-483), each re-rendering the app, while the main process is simultaneously CPU-bound on the clone itself.

Idea

Default npm to notice-level logging with audit/funding off, delete the never-rendered log state, cap the remaining buffers to a trailing window, and coalesce clone progress to a few updates per second. Mostly deletions.

Read src/install-runner.js:34, src/script-runner.js:80, src/renderer/index.jsx:825, and src/main.js:479-483 to trace verbosity, log accumulation, and clone progress updates. Check how runtime, setup, and terminal buffers are rendered and capped. Done means unnecessary logs and IPC updates no longer burden the UI while the remaining buffers retain only a trailing window.