Please address the comments from this code review:

## Overall Comments
- In the zip/auto-install branch, `clearPendingUpdateInfo()` is now only called when `!isAutoStartModeNow`; if an auto-started session detects a completed update, you may want to clear the pending-update state regardless and only defer the UI/confirm modal, to avoid leaving stale pending-update info around.
- The logic that sets `justUpdatedInfo` and shows the install confirm modal is now duplicated in both the version-verified branch and the direct-complete branch; consider extracting this into a small helper to keep the update-complete flow easier to maintain.

Please address the comments from this code review:

## Overall Comments
- In `peekUpdateCompleteInfo`, consider handling malformed JSON by clearing the stored value (similar to `consumeUpdateCompleteInfo`) so that a single bad `localStorage` entry doesn't cause repeated parse warnings or inconsistent behavior.
- The effect that dispatches pending auto tasks only triggers when `downloadStatus === 'failed'`, but the comment mentions both failure and cancellation; if cancellations are represented by a different status, you may want to include that explicitly or adjust the comment to match the actual behavior.

## Individual Comments

### Comment 1
<location path="src/services/updateService.ts" line_range="1159-1162" />
<code_context>
+/**
+ * 读取更新完成信息（不清除）
+ */
+export function peekUpdateCompleteInfo(): UpdateCompleteInfo | null {
+  try {
+    const data = localStorage.getItem(UPDATE_COMPLETE_STORAGE_KEY);
+    if (!data) return null;
+    return JSON.parse(data) as UpdateCompleteInfo;
+  } catch (error) {
+    log.warn('读取更新完成信息失败:', error);
</code_context>
<issue_to_address>
**suggestion:** Consider clearing the stored value when JSON parsing fails to avoid repeated warnings on every launch.

Right now a failed parse leaves the bad value in `localStorage`, so every subsequent call will keep throwing and logging until someone manually clears it. To avoid this persistent failure mode, you could call `localStorage.removeItem(UPDATE_COMPLETE_STORAGE_KEY)` in the `catch` block.

```suggestion
  } catch (error) {
    log.warn('读取更新完成信息失败:', error);
    // 当解析失败时清除存储的异常数据，避免下次继续报错
    localStorage.removeItem(UPDATE_COMPLETE_STORAGE_KEY);
    return null;
  }
```
</issue_to_address>

### Comment 2
<location path="src/App.tsx" line_range="933" />
<code_context>

+  // 下载失败或取消时，如果有等待中的自动任务，立即分发
+  useEffect(() => {
+    if (pendingAutoTasksRef.current && downloadStatus === 'failed') {
+      pendingAutoTasksRef.current = false;
+      log.info('下载失败/取消，分发挂起的自动任务');
</code_context>
<issue_to_address>
**question:** The effect only reacts on `failed`, but the comment mentions download cancellation as well; clarify or align with the actual download status values.

Given the comment text, cancellation should also trigger this effect, but the condition only matches `downloadStatus === 'failed'`. If cancel maps to a different status (e.g. `idle` or `canceled`), pending auto tasks will never be dispatched on cancel. Either include the cancellation status in the condition or update the comment to match the actual behavior.
</issue_to_address>