perf(server): skip parsing plain terminal history output

[StiensWout]

Plain terminal output is copied one character at a time while the server filters replay-unsafe terminal queries. This wastes CPU on build logs even when no client is attached.

Return ordinary chunks directly when there is no unfinished sequence or sequence introducer. Control-bearing chunks keep the existing parser, including queries split across writes.

All 89 terminal manager tests pass, including Unicode/control preservation around a split query. Server typecheck, targeted lint and formatting pass, with one existing lint warning. A standalone probe of the actual source on Node 24.19.0 processed 20 MiB of plain text in 16 KiB chunks in median 424 ms before and 1.59 ms after across seven runs. This measures the sanitizer alone, not end-to-end terminal performance.

_{Prepared for Wout by gpt-6.1-sol in the Codex harness through T3 Code.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a focused terminal-history performance optimization with a regression test, but it adds a line-level ESLint suppression for the control-regex diagnostic. That static-analysis override requires human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Advanced
• Run ID: 9fe5fa7d-6ed1-47c9-ae02-0caff43f2bb2

📥 Commits

Reviewing files that changed from the base of the PR and between a4c9494 and f8f9d8d.

📒 Files selected for processing (2)

• apps/server/src/terminal/Manager.test.ts
• apps/server/src/terminal/Manager.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

sanitizeTerminalHistoryChunk now returns chunks unchanged when they have no pending control sequence or recognized terminal-sequence introducer. A test checks persisted history when an OSC query spans two output chunks.

Changes

Terminal history sanitization

Layer / File(s)	Summary
Sanitize chunks and verify persisted history apps/server/src/terminal/Manager.ts, apps/server/src/terminal/Manager.test.ts	sanitizeTerminalHistoryChunk returns chunks unchanged when no sequence is pending and no recognized introducer is present. The test verifies that history retains surrounding Unicode and control characters while omitting a query split across output chunks.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Refactor

Suggested reviewers: juliusmarminge

Merge Risk: ⚪ Minimal · up to f8f9d

The change preserves the existing handling of recognized terminal sequences while bypassing parsing for ordinary chunks. No actionable merge risk is established.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main performance change: skipping parsing for plain terminal history output.
Description check	✅ Passed	The description clearly explains the problem, implementation, verification results, performance measurement, and test scope. It does not include the template's Scope and approval section or explain wh…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}