Complete Context Loss and Conversation Failure

## Problem
When attempting to make a relatively large change to my code base the Amazon Q conversation agent looses context and basically terminates the conversation. This issue is extremely frustrating because the conversation context is completely lost and it is as if you are starting anew.

- I have turned indexing off in the Q settings and configured .vscode ignore directories and my .gitignore file to limit the workspace to a 150 files.
- I noticed this file does not exist in the distribution
/Users/[username]/.vscode/extensions/amazonwebservices.amazon-q-vscode-1.100.0/resources/language-server/servers/indexing/dist/extension.js
- the issue happens with both sonnet 4.0 and sonnet 4.5
- it also happens with many version of the integration. I tested back to 1.91.

2025-10-22 16:37:11.568 [info] [Error - 4:37:11 PM] [2025-10-22T20:37:11.567Z] lserver: Vector library failed to initialize:Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/[username]/.vscode/extensions/amazonwebservices.amazon-q-vscode-1.100.0/resources/language-server/servers/indexing/dist/extension.js' imported from /Users/[username]/.vscode/extensions/amazonwebservices.amazon-q-vscode-1.100.0/resources/language-server/servers/aws-lsp-codewhisperer.js

2025-10-22 16:38:10.628 [info] [Warn - 4:38:10 PM] [2025-10-22T20:38:10.624Z] lserver: Error processing context command update: Error: Failed to get LocalProjectContextController instance: Error: LocalProjectContextController initialization timeout after 60 seconds

## Expected behavior
- conversation should not be lost on failure.
- maybe even a warning message if number in files in workspace is to large

- OS: Mac OS 15.6
- Visual Studio Code version: 1.105.1
- AWS Toolkit version: 3.81.0
- Amazon Q version: 1.91 - 1.100

Reproduce the failure with a relatively large workspace using the reported Mac OS, VS Code, and Amazon Q versions, then inspect the language-server indexing path and aws-lsp-codewhisperer.js import for the missing resources/language-server/servers/indexing/dist/extension.js. Use the reported Vector library and LocalProjectContextController errors as the starting logs. Done means the conversation remains available after context failure and, if applicable, a workspace-size warning is shown.

Written by the indexing model from the issue text.