fix: expand Chronicle session_files/refs tracking to match VS Code tool names

[digitarald]

Problem

The session_files and session_refs tables in the Chronicle local session history store are always empty (0 rows across 460+ sessions).

Root cause: FILE_TRACKING_TOOLS only recognized CLI-agent tool names (str_replace_editor, create) but VS Code emits model-facing names (replace_string_in_file, insert_edit_into_file, etc). Similarly, isGitHubMcpTool() only matched the github-mcp-server- prefix, not VS Code's mcp_github_ prefix.

Fix

• Expand FILE_TRACKING_TOOLS from 4 to 11 entries matching VS Code's ToolName enum
• Add extraction for multi_replace_string_in_file (nested replacements array)
• Add apply_patch input text parsing (*** Update/Add/Delete File: lines)
• Update isGitHubMcpTool() to match both mcp_github_ and github-mcp-server- prefixes
• 29 new tests, all 119 chronicle tests pass

Fixes #312281

[Copilot]

Pull request overview

Expands Chronicle’s session history extraction so session_files/session_refs are populated for VS Code-hosted Copilot sessions by recognizing VS Code tool names and GitHub MCP tool prefixes.

Changes:

• Expand file-tracking tool-name coverage to include VS Code’s model-facing tool names and add apply_patch input parsing.
• Update GitHub MCP tool detection to accept both mcp_github_ (VS Code) and github-mcp-server- (CLI) prefixes.
• Add new focused unit tests for file/ref/repo extraction behavior.

Show a summary per file

File	Description
extensions/copilot/src/extension/chronicle/common/sessionStoreTracking.ts	Adds broader tool-name recognition and patch parsing for file/ref tracking.
extensions/copilot/src/extension/chronicle/common/test/sessionStoreTracking.spec.ts	New unit tests for file path extraction, GitHub MCP tool detection, repo/ref extraction, and terminal ref extraction.
extensions/copilot/src/extension/chronicle/common/test/standupPrompt.spec.ts	Updates existing expectations to reflect read_file now being tracked for file paths.

Copilot's findings

Comments suppressed due to low confidence (2)

extensions/copilot/src/extension/chronicle/common/sessionStoreTracking.ts:52

• multi_replace_string_in_file can apply replacements across multiple files (per tool schema). Returning only the first replacement’s filePath will under-report affected files in session_files. Consider extracting all unique filePaths from args.replacements and recording one session_files row per path (likely by adjusting the tracker to accept multiple paths).

	// multi_replace_string_in_file stores filePath in each replacement item
	if (toolName === 'multi_replace_string_in_file' && Array.isArray(args.replacements)) {
		const first = args.replacements[0];
		if (typeof first === 'object' && first !== null) {
			const fp = (first as Record<string, unknown>).filePath;
			if (typeof fp === 'string') { return fp; }
		}
	}

extensions/copilot/src/extension/chronicle/common/sessionStoreTracking.ts:68

• apply_patch supports patching multiple files in a single input (multiple *** Update/Add/Delete File: sections). Extracting only the first match means session_files will miss additional touched files. Consider extracting all file paths from the patch input and recording each one (deduping if needed).

	// apply_patch encodes file paths in the patch input text
	if (toolName === 'apply_patch' && typeof args.input === 'string') {
		return extractFirstFileFromPatch(args.input);
	}

	return undefined;
}

/**
 * Extract the first file path from an apply_patch input string.
 * Matches lines like `*** Update File: /path/to/file` or `*** Add File: /path`.
 */
function extractFirstFileFromPatch(input: string): string | undefined {
	const match = input.match(/^\*\*\*\s+(?:Update|Add|Delete)\s+File:\s*(.+)$/m);
	return match?.[1]?.trim();

• Files reviewed: 3/3 changed files
• Comments generated: 1