Remove debug logging from production pipeline

[Copilot]

Debug console.log statements used during development were polluting production execution logs in the main branch. This PR strips standard output logging across the core pipeline to ensure a clean production environment.

Changes

• Core Pipeline Cleanup: Removed all console.log debugging statements across backend/src (specifically targeting issueAnalyzer, issuePipeline, snippetFetcher, and related pipeline components) and frontend/app.
• AST-based Extraction: Leveraged an AST transformation script (ts-morph) to safely prune exact ExpressionStatement nodes, avoiding regex-based partial deletions.
• Error & Test Retention: Preserved console.error and console.warn statements for structured telemetry. Retained standard logging in test files (e.g., testIssueMapper.ts) to maintain test suite visibility.

Example

// Before
console.log(`\x1b[32m[issuePipeline] loaded retrieval index: ${index.files.length} files\x1b[0m`);
const files = (parsed.requestedFiles ?? []).slice(0, 15);
console.log(`\x1b[34m[issueAnalyzer] Gemini graph navigation returned ${files.length} files\x1b[0m`);

// After
const files = (parsed.requestedFiles ?? []).slice(0, 15);

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
code-map-ai	Ready	Preview, Comment	Jun 10, 2026 5:59am