Use a neutral CLI log prefix instead of hard-coded 'site ID'

[gavande1]

Related issues

• Follow-up of Fix Windows E2E: combined status reporting, PHP INI tilde fixes, and per-command CLI shutdown #4082

How AI was used in this PR

Claude wrote the code, guided by the author. The author tested it locally and manually reviewed it before pushing.

Proposed Changes

The stdout echo prefix hard-coded the words "site ID", but logPrefix is also used for non-site contexts. For example, the CLI events subscriber passes "events", which produced the misleading line [CLI - site ID events]. The prefix is now the neutral [CLI - <prefix>], which matches the format CliServerProcess already uses for its own log lines.

Testing Instructions

• Run npm start and start a site. CLI stdout lines should be prefixed with [CLI - <site ID>], and events subscriber lines with [CLI - events].

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wpmobilebot]

📊 Performance Test Results

Comparing b9a8990 vs trunk

app-size

Metric	trunk	b9a8990	Diff	Change
App Size (Mac)	1411.96 MB	1411.96 MB	+0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	b9a8990	Diff	Change
load	739 ms	1062 ms	+323 ms	🔴 43.7%

site-startup

Metric	trunk	b9a8990	Diff	Change
siteCreation	6493 ms	6501 ms	+8 ms	⚪ 0.0%
siteStartup	2379 ms	2393 ms	+14 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[gcsecsey]

Thanks, this change looks good.

trunk	this branch