feat: stream debug logs from go bridge

[snyk-will]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Stream debug logs from the internal go command to the calling typescript when the debug flag is passed.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

	Warnings
⚠️	There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 7fcaad6

[CatalinSnyk]

Looks like this one needs a format.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Potential Loss of Error Context 🟡 [minor] Once isStderrTruncated is set to true (after stderr exceeds 50MB), the code stops accumulating any further chunks into the stderr variable returned in GoCommandResult. If the Go process produces a large volume of debug logs followed by a terminal error message, that error message will be present in the streamed output (if --debug is active) but missing from the stderr property of the result object. This could lead to poor error reporting by callers who rely on the result object to extract specific error details from the Go bridge. While 50MB is a generous limit, a strategy that preserves the tail of the output (e.g., keeping the last few KB after truncation) would be more robust for error diagnostics. if (isStderrTruncated) { return; }

📚 Repository Context Analyzed This review considered 6 relevant code sections from 6 files (average relevance: 1.02) src/lib/go-bridge.ts (lines 1-198) src/cli/main.ts (lines 1-516) cliv2/cmd/cliv2/errorhandling.go (lines 1-104) cliv2/cmd/cliv2/exitcode.go (lines 1-196) cliv2/cmd/cliv2/debug.go (lines 1-72) CONTRIBUTING.md (lines 301-400)