yoi/.yoi/tickets/00001KV5MRH6D/thread.md

作成

LocalTicketBackend によって作成されました。

---

State changed

Ticket を workspace-panel が queued にしました。

---

Decision

Routing decision: implementation_ready

Reason:

• Panel Queue により routing が明示的に許可され、Ticket は queued。
• Ticket body / thread / relations / OrchestrationPlan / Orchestrator workspace state を確認した。blocking relation はなく、planning に戻す concrete missing information はない。
• Work item は Panel startup latency の measurement / E2E budget / concrete wait-point improvement に限定され、Ticket workflow / Pod authority / Orchestrator queue semantics を変更しない invariant が明確。
• 同時 queued の Plugin resolver work とは source surface が大きく異なるため並行開始可能。

Evidence checked:

• Ticket body/thread: startup wait points、first visible vs full ready distinction、E2E acceptance criteria、binding decisions、escalation conditions、validation を確認。
• Ticket relations: blocker なし。
• OrchestrationPlan: 既存 record なし。
• Orchestrator workspace: /home/hare/Projects/yoi/.worktree/orchestration は clean、425a6c66 上。
• Visible Pods: implementation child Pod なし。
• Related context: 00001KTFMMZP0 prior non-blocking transition work、00001KV3BQ7Q3 Panel/TUI E2E behavior evidence work は closed/done context として参照。

IntentPacket:

Intent:

• yoi panel startup path を E2E/fixture PTY で計測し、first visible render と background/full-ready wait を分けて可視化し、実ユーザーに効く startup latency を改善・基準化する。

Binding decisions / invariants:

• focused/unit/code review だけで startup latency 改善済み扱いにしない。
• E2E pass と manual/live terminal confirmation を混同しない。
• first visible render と all background work complete を同一 metric にしない。
• 起動を速く見せるために Ticket / Pod / Orchestrator state authority を偽らない。
• Background reload / observation 完了後は正しい state / diagnostics を反映する。
• Provider/network/secret dependency を導入しない。
• Broad TUI runtime rewrite / scheduler / lease 導入は non-goal。

Requirements / acceptance criteria:

• Real yoi binary + PTY path の E2E で startup time を測る。
• 少なくとも initial visible panel/render 到達時間を assert する。
• First visible budget を明示する（提案: <= 1500ms; 実測で妥当でない場合は理由付き調整）。
• Full ready/background reload complete を測るなら別 metric/budget として扱う。
• Before/after 測定結果、major wait point、削減/非同期化/遅延実行した wait、E2E が保証する範囲、live/manual gap を実装報告に記録する。
• Existing E2E fixture-local HOME/XDG/runtime/workspace isolation and no-provider/no-network を維持する。

Implementation latitude:

• E2E-only observer / timing marker / PTY output marker / structured diagnostic event の選択は実装判断。
• Wait point breakdown の粒度は実装判断だが報告で説明可能にする。
• If fixture does not reproduce 7s latency, record what is guaranteed and what remains live/manual gap。
• Startup improvement can use existing PendingReload / background observation / loading state。

Escalate if:

• 7s latency is live/workspace-specific and not fixture reproducible。
• Stable timing test requires broader harness redesign。
• Wait cause is storage corruption / huge metadata / provider / filesystem stalls outside fixture。
• Fix requires Pod authority / Ticket workflow / Orchestrator lifecycle semantic changes。
• Meaningful latency threshold cannot be made non-flaky。

Validation:

• cargo test -p yoi-e2e --features e2e or narrow scenario plus full if feasible。
• cargo test -p yoi-e2e --features e2e --no-run。
• cargo fmt --check。
• git diff --check。
• Depending changes: cargo check -p yoi-e2e -p yoi -p tui and focused tui tests。

Critical risks / reviewer focus:

• E2E actually measures first visible render, not just process start。
• first visible vs full ready distinction。
• threshold not overly flaky and not permissive of 7s regression。
• no authority/state falsification for speed。
• fixture isolation / no-provider / no-network。
• before/after evidence and residual live gap clarity。

---

State changed

Routing decision と accepted implementation/evidence plan を記録済み。blocking relation / unresolved OrchestrationPlan blocker はなく、Panel startup latency work は同時に開始する Plugin resolver work と主対象が異なるため、implementation side effects の前に queued -> inprogress acceptance を記録する。

---

Implementation report

E2E measurements (real target/debug/yoi + PTY)

Scenario	Before	After	Budget	Notes
Fixture first visible panel render (panel_full_ready_has_separate_startup_budget)	20.342 ms	20.384 ms	1500 ms	Warm fixture did not reproduce 7 s latency; after path keeps first draw separate from reload work.
Fixture full-ready rows (panel_full_ready_has_separate_startup_budget)	120.576 ms	120.552 ms	5000 ms	Separate metric; fixture full-ready remains well below budget after the first-frame deferral.
Held-reload ordering (panel_first_visible_render_arrives_before_background_reload)	background_task_started before panel_ready	panel_ready before held background_task_started; first visible 20.396 ms	1500 ms	Guarantees initial visible frame is not blocked by reload/observation.
Pre-change ad-hoc Panel run from existing fixture artifact	background_task_started@76 ms, panel_ready@80 ms, full rows @182 ms	latest held/full tests above	n/a	Used to identify wait ordering; fixture still did not reproduce live 7 s.

Wait points identified

• Synchronous before first draw: CLI/process startup, run_panel workspace/cwd setup, load_app construction of an empty/loading WorkspacePanelViewModel, raw-mode/bracketed-paste/alternate-screen/mouse setup, and the first terminal.draw.
• Previously scheduled before first draw: initial Panel reload/observation task (PendingReload::start(Ensure { ... })), which can scan Tickets/Pods/orchestrator state and perform socket/status probing before fixture rows are fully ready.
• Background/full-ready after first draw: load_multi_pod_snapshot, Ticket list/detail loading, Pod metadata/status checks, orchestrator lifecycle observation, row selection/re-render, and background diagnostics.

Changes

• Added PTY E2E startup coverage for yoi panel:
  • panel_first_visible_render_arrives_before_background_reload asserts panel_ready arrives within 1500 ms and before the held reload task starts.
  • panel_full_ready_has_separate_startup_budget asserts first visible render within 1500 ms and full fixture rows within 5 s as a separate metric.
• Deferred the initial Panel reload start until after the first loading frame is drawn, preserving later background reload correctness.
• Kept Panel/terminal mouse capture to SGR + normal tracking (?1006h + ?1000h) and avoided drag-capture (?1002h/?1003h) so existing PTY tests can confirm no drag-capture regression.

Guaranteed scope / residual gaps

• Guaranteed by E2E fixture: real binary, PTY, first visible frame budget, held-reload ordering, separate full-ready row budget, no provider/network/secret dependency.
• Residual live/manual gap: the reported ~7 s live Panel startup did not reproduce in this fixture. This change prevents initial reload/observation from blocking or contending with the first visible frame, but live-terminal confirmation is still needed if the remaining cause is workspace-specific (for example a large real Ticket/Pod set or slow live socket/status probe).

---