撤销 commits bbe262d and 7d0de8b

[CJKmkp]

Motivation

• Remove two recent changes that introduced PPT-module adjustments and a watchdog/restart change by reverting commits bbe262df7e0fdd766658c4b90fbbbcb1fbff6d82 and 7d0de8b5a3728825e1fc8dc6fb84c649725417df to restore the previous, stable behavior.
• Resolve a merge conflict encountered while reverting to ensure the application watchdog logic remains consistent and safe.

Description

• Created two revert commits on branch work: revert of bbe262df7e0fdd766658c4b90fbbbcb1fbff6d82 (recorded as fc4415b) and revert of 7d0de8b5a3728825e1fc8dc6fb84c649725417df (recorded as 938cce1).
• Resolved a conflict in Ink Canvas/App.xaml.cs by removing conflict markers and keeping the DateTime.Now-based watchdog checks and the inline startup timeout check (elapsedSinceStart.TotalMinutes >= 2).
• Restored PPT manager behavior by reverting changes in Ink Canvas/Helpers/PPTManager.cs and introducing UpdateCurrentPresentationInfo() to centralize and harden retrieval of current presentation/slide state and COM cleanup.
• Files changed: Ink Canvas/App.xaml.cs and Ink Canvas/Helpers/PPTManager.cs (revert commits updated those files and removed leftover conflict markers).

Testing

• Ran git status --short and confirmed working tree is clean and no uncommitted changes remain (success).
• Inspected history with git log --oneline -n 5 to confirm the two revert commits are present on work (success).
• Verified revert results and touched files with git show --stat --name-only and validated that Ink Canvas/App.xaml.cs and Ink Canvas/Helpers/PPTManager.cs reflect the intended revert changes (success).
• Searched for leftover conflict markers with rg -n "^(<<<<<<<|=======|>>>>>>>)" in the modified files and confirmed none remain (success).

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b575269972

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep startup grace period before watchdog restarts

This restart condition now triggers immediately after isStartupComplete once heartbeat lag exceeds 10s, but the previous guard that skipped watchdog restarts during the first 2 minutes after process start was removed. On slower machines or heavy startup paths, lastHeartbeat can still be stale when startup just finished, so this can cause false-positive “main thread unresponsive” restarts and restart loops right after launch. Please restore the startup grace check (or equivalent) before applying the 10s heartbeat rule.

Useful? React with 👍 / 👎.