docs(todo): separate WBS 9.x current vs target Tauri status

[john33fiao]

Motivation

• Clarify the WBS 9.x Tauri migration tracking by explicitly separating the current implementation (As-Is) from the intended target state (To-Be) so the TODO list does not mix in-progress items with goal descriptions.

Description

• Added a 9.x 상태 구분 (2026-02-28 재점검 기준) section under 9.0 Tauri 데스크톱 앱 전환 in TODO/TODO.md that documents As-Is and To-Be bullets for the Tauri transition and marked the P2 checklist item for status/goal separation as completed ([x]).

Testing

• Ran automated content checks including a Python assertion that the new header and updated checklist state exist (python - <<'PY' ...), inspected the git diff -- TODO/TODO.md, and verified repository status (git status --short), and all checks passed.

---

Codex Task

[Copilot]

Pull request overview

Updates the WBS 9.x Tauri migration tracking documentation to clearly separate the current implementation state from the intended target state, so in-progress TODOs don’t get mixed with goal descriptions.

Changes:

• Added a new “9.x 상태 구분 (2026-02-28 재점검 기준)” section under “9.0 Tauri 데스크톱 앱 전환” with “As-Is” vs “To-Be” bullets.
• Marked the related P2 checklist item for separating current vs target status as completed ([x]).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.