Replace console.log with VS Code output channel for better user visibility

[Copilot]

This PR addresses the feedback to replace console.log usage in production extension code with a proper VS Code output channel, making diagnostic messages visible to users through the VS Code Output panel.

Changes Made

New Output Channel Implementation

• Created src/logging.ts utility with centralized output channel management
• Added logInfo(), logError(), and logDebug() functions with proper log level formatting
• Integrated output channel lifecycle with extension activation/deactivation

Replaced console.log Usage

Updated all production code files to use the new logging system:

• src/extension.ts - Model selection and error logging (22 instances)
• src/github/gitHub.ts - Git repository operations (6 instances)
• src/llmBasedParser.ts - GitHub context operations (1 instance)
• src/addCommand.ts - Error handling (1 instance)
• src/azd/azd.ts - Azure DevOps operations (2 instances)
• src/azd/workitems/azDevOpsWorkItemFunctions.ts - Added the suggested authentication message

Example Implementation

The specific suggestion from the issue is now implemented:

// Before (hidden in console)
console.log("Microsoft authentication not available, falling back to PAT token");

// After (visible in VS Code Output panel)
logInfo("Microsoft authentication not available, falling back to PAT token configuration required");

Benefits

• User Visibility: Diagnostic messages now appear in VS Code's "VOCE DevOps" output channel
• Better Debugging: Users and developers can see extension behavior without opening DevTools
• Professional UX: Maintains existing user-facing notifications while adding transparency
• Centralized Logging: All extension logging goes through a single, manageable system

Verification

• ✅ All builds pass (npm run compile)
• ✅ Linting passes (npm run lint)
• ✅ No functionality broken - all existing features preserved
• ✅ Messages accessible via View > Output > VOCE DevOps

The extension now provides better visibility into its operations while maintaining the same user experience for all existing features.

Fixes #53.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull Request Overview

This PR introduces a centralized VS Code output channel for logging and replaces all console.log/console.error calls in production code with structured logging functions, improving visibility in the VS Code Output panel.

• Added src/logging.ts with initializeOutputChannel, logInfo, logError, logDebug, showOutputChannel, and disposeOutputChannel.
• Updated all modules (extension.ts, GitHub/Azure DevOps utilities, LLM parser, addCommand) to use logInfo/logError.
• Integrated output channel lifecycle in activate/deactivate and added basic import tests in src-tests/.

Reviewed Changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/logging.ts	New logging utility managing a shared VS Code output channel
src/extension.ts	Initialized/disposed output channel and replaced console logs
src/github/gitHub.ts	Swapped console.log/error with logInfo/logError
src/llmBasedParser.ts	Replaced a diagnostic console.log with logInfo
src/azd/azd.ts	Replaced console.log/error with logInfo/logError
src/azd/workitems/azDevOpsWorkItemFunctions.ts	Added logInfo for PAT fallback diagnostics
src/addCommand.ts	Changed console.log to logError in error handler
src-tests/loggingTest.ts	Basic import-only script to verify logging function exports
src-tests/loggingTest.js	Duplicate JavaScript test for logging imports

Comments suppressed due to low confidence (1)

src-tests/loggingTest.ts:7

• This test only verifies import availability. To improve coverage, add unit tests that mock vscode.OutputChannel and assert that logInfo/logError/logDebug produce correctly formatted output lines.

import { initializeOutputChannel, logInfo, logError, logDebug, showOutputChannel, disposeOutputChannel } from "../src/logging";

[Copilot]

The logging functions silently drop messages if the output channel isn't initialized. Consider automatically calling initializeOutputChannel() when outputChannel is null or logging a warning to alert developers of premature use.

Suggested change

	export function logInfo(message: string): void {
	if (outputChannel) {
	outputChannel.appendLine(`[INFO] ${message}`);
	export function logInfo(message: string): void {
	if (!outputChannel) {
	initializeOutputChannel();
	}
	if (outputChannel) {
	outputChannel.appendLine(`[INFO] ${message}`);
	} else {
	console.warn("logInfo: Output channel is not initialized. Message dropped:", message);

[Copilot]

This JavaScript test duplicates the TypeScript version in loggingTest.ts. Consolidate into a single test file to remove redundancy and simplify maintenance.

Suggested change

	"use strict";
	// File removed. Functionality consolidated into loggingTest.ts.