fix: remove await from startIndexing calls and update JSDoc

- startIndexing should never be awaited as it's a long-running background process
- Added JSDoc warning to never await this method
- Updated webviewMessageHandler to not await startIndexing calls

Author: daniel-lxs

src/core/webview/webviewMessageHandler.ts

@@ -2218,13 +2218,13 @@ export const webviewMessageHandler = async (
 					}
 
 					// startIndexing now handles error recovery internally
-					await manager.startIndexing()
+					manager.startIndexing()
 
 					// If startIndexing recovered from error, we need to reinitialize
 					if (!manager.isInitialized) {
 						await manager.initialize(provider.contextProxy)
 						// Try starting again after initialization
-						await manager.startIndexing()
+						manager.startIndexing()
 					}
 				}
 			} catch (error) {

src/services/code-index/manager.ts

@@ -168,6 +168,9 @@ export class CodeIndexManager {
 	/**
 	 * Initiates the indexing process (initial scan and starts watcher).
 	 * Automatically recovers from error state if needed before starting.
+	 *
+	 * @important This method should NEVER be awaited as it starts a long-running background process.
+	 * The indexing will continue asynchronously and progress will be reported through events.
 	 */
 	public async startIndexing(): Promise<void> {
 		if (!this.isFeatureEnabled) {