refactor(webview): clarify throttled state semantics

Document the distinction between scheduling and flushing throttled state updates. Use the typed abort event in ordering coverage.

Signed-off-by: JunyongParkDev <jun94.park@samsung.com>

Author: JunyongParkDev

src/core/task/__tests__/Task.spec.ts

@@ -1907,7 +1907,7 @@ describe("Cline", () => {
 			await task.abortTask()
 
 			const taskAbortedCallIndex = (emitSpy.mock.calls as unknown[][]).findIndex(
-				([event]) => event === "taskAborted",
+				([event]) => event === RooCodeEventName.TaskAborted,
 			)
 			expect(taskAbortedCallIndex).toBeGreaterThanOrEqual(0)
 			expect(queuedMessagesAtFlush).toBe(1)

src/core/webview/ClineProvider.ts

@@ -2195,6 +2195,12 @@ export class ClineProvider
 		await this.postMessageToWebview({ type: "state", state: rest })
 	}
 
+	/**
+	 * Schedules a debounced state-post attempt. A call made while the debounce timer is active returns
+	 * the result of the most recent invocation, so awaiting this method does not wait for the trailing
+	 * invocation scheduled by that call. Use `flushPostStateToWebviewThrottled()` to force and await any
+	 * pending trailing invocation before continuing.
+	 */
 	async postStateToWebviewThrottled(): Promise<void> {
 		if (this._disposed) {
 			return