Fix: surface the failing grunt task/error instead of the whole build transcript

[taylortom]

Fix

• When a grunt build task fails, adaptBuild rejected with the entire grunt transcript as the error message (the >> Error: regex only matched grunt's own task warnings, so anything else — e.g. a rollup "Could not load …" failure from the javascript task, which prints a bare Error: line — fell through to dumping all of stdout). It now extracts just the salient failure: a >> Error: task message, else a bare Error: line, else the failing-task Warning: Task "…" failed line, falling back to full stdout only when none is present. The full transcript is preserved on error.stdout for debugging.

Testing

1. Run a build whose javascript/rollup task fails (e.g. a module import that can't be resolved).
2. The rejected error's .raw is now the concise root-cause line instead of the whole grunt transcript; .stdout still contains the full log.

[Copilot]

Pull request overview

Improves adaptBuild’s grunt failure reporting by extracting a concise, root-cause-oriented error string instead of rejecting with the entire grunt stdout transcript, while preserving the full stdout log on the error object for debugging.

Changes:

• Update stdout parsing to prefer >> Error: task messages, then bare Error: lines, then Warning: Task "…" failed lines.
• Attach the full stdout transcript to the thrown error (error.stdout) while keeping the concise message on error.raw.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.