[rush] fix: wire ProblemCollector correctly into the terminal pipeline

[Copilot]

ProblemCollector in OperationExecutionRecord had three issues: it was missing preventAutoclose: true, it received raw ANSI-colored output (causing regex mismatches), and it was silently dropped from the pipeline when no log file was being written.

Changes

OperationExecutionRecord.ts

• Add preventAutoclose: true to ProblemCollector construction, consistent with StdioSummarizer
• Inject a TextRewriterTransform { removeColors: true } stage between the splitter and problemCollector to strip VT/ANSI escape codes before pattern matching
• Fix oversight: problemCollector is now always connected via an unconditional SplitterTransform, even when projectLogWritable is absent

Updated pipeline topology:

normalizeNewlineTransform --1--> stderrLineTransform --2--> projectLogWritable?
                                                       |
                                                       +--> stdioSummarizer
                                                       |
                                                       +--> removeColorsTransform --> problemCollector

---

⚡ Quickly spin up Copilot coding agent tasks from anywhere on your macOS or Windows machine with Raycast.

[dmichon-msft]

Let's scope this PR down to just the changes to OperationExecutionRecord. Be sure to add a change file for @microsoft/rush of type path describing the change.

[Copilot]

Let's scope this PR down to just the changes to OperationExecutionRecord. Be sure to add a change file for @microsoft/rush of type path describing the change.

Done in 3cfd6ed. Reverted FileError.ts, FileError.test.ts, and rush-vscode-extension/package.json — the PR now only contains changes to OperationExecutionRecord.ts. Added a patch change file at common/changes/@microsoft/rush/fix-problem-collector-pipeline_2026-03-20-22-38.json.