From 7e96da5da55bc9237971fb902e30196eaf830294 Mon Sep 17 00:00:00 2001 From: Cooper-X-Oak Date: Sat, 2 May 2026 01:46:49 +0800 Subject: [PATCH] =?UTF-8?q?docs(windows):=20=E8=B7=9F=E8=B8=AA=20startup?= =?UTF-8?q?=20visible-ready=20=E7=94=9F=E5=91=BD=E5=91=A8=E6=9C=9F?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../issue-98-startup-visible-ready.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 docs/windows-lifecycle-tracking/issue-98-startup-visible-ready.md diff --git a/docs/windows-lifecycle-tracking/issue-98-startup-visible-ready.md b/docs/windows-lifecycle-tracking/issue-98-startup-visible-ready.md new file mode 100644 index 00000000..ba61903b --- /dev/null +++ b/docs/windows-lifecycle-tracking/issue-98-startup-visible-ready.md @@ -0,0 +1,27 @@ +# Issue #98 Tracking + +Scope: Windows startup `visible` / `ready` lifecycle contract + +Current stage: + +- This branch is a draft PR placeholder. +- No runtime fix is included yet. +- The goal is to freeze the problem boundary before implementation. + +Problem statement: + +- The main window can become visible before hotkey/runtime readiness is truly established. +- Backend and frontend both participate in first-show ownership. +- Windows is the currently observed symptom surface, but the ownership split is architectural. + +Implementation target to converge before coding: + +- Decide a single owner for initial main-window visibility. +- Define the relation between `created`, `shown`, `startup`, `ready`, and `first usable state`. +- Decide whether startup shell and ready shell remain separate concepts. + +Non-goals in this draft: + +- No Tauri window behavior change yet +- No frontend gate refactor yet +- No smoke implementation yet