diff --git a/.yoi/tickets/00001KV5MRH6D/item.md b/.yoi/tickets/00001KV5MRH6D/item.md index 1aa0de2f..e09e4bb4 100644 --- a/.yoi/tickets/00001KV5MRH6D/item.md +++ b/.yoi/tickets/00001KV5MRH6D/item.md @@ -1,8 +1,8 @@ --- title: 'Panel 起動遅延の待ち要因を E2E 計測で特定し改善する' -state: 'done' +state: 'closed' created_at: '2026-06-15T12:40:33Z' -updated_at: '2026-06-15T14:31:28Z' +updated_at: '2026-06-19T05:44:09Z' assignee: null readiness: 'implementation_ready' risk_flags: ['panel', 'tui', 'e2e', 'latency', 'runtime-observation'] diff --git a/.yoi/tickets/00001KV5MRH6D/resolution.md b/.yoi/tickets/00001KV5MRH6D/resolution.md new file mode 100644 index 00000000..810dd206 --- /dev/null +++ b/.yoi/tickets/00001KV5MRH6D/resolution.md @@ -0,0 +1,9 @@ +Closed as completed by the subsequent Panel startup E2E and latency-improvement sequence. + +The initial work separated first visible frame readiness from background reload, but later review showed that user-visible startup latency must be measured at dashboard content-ready, not first frame or single-row readiness. The later Tickets added dashboard snapshot readiness, shell-enter launch-path coverage, live workspace measurements, and the actual startup fix for duplicate Pod probes/session-log scans. + +Relevant follow-ups: +- 00001KV62PF32: corrected readiness away from first frame / weak row count; +- 00001KVDETSN6: dashboard content-ready snapshot metric; +- 00001KVDQH839: shell-enter launch-path measurement; +- 00001KVF0ZJM5: fixed live startup by reusing initial Pod list presence and avoiding session-log reads before first rows. diff --git a/.yoi/tickets/00001KV5MRH6D/thread.md b/.yoi/tickets/00001KV5MRH6D/thread.md index 1ba9015e..d43e0e4d 100644 --- a/.yoi/tickets/00001KV5MRH6D/thread.md +++ b/.yoi/tickets/00001KV5MRH6D/thread.md @@ -215,4 +215,30 @@ Cleanup planned: Reviewer approved, implementation/evidence branch merged into the orchestration branch, and E2E-focused validation passed in the Orchestrator worktree. Marking Ticket done in the orchestration branch. +--- + + + +## State changed + +Ticket を closed にしました。 + + +--- + + + +## 完了 + +Closed as completed by the subsequent Panel startup E2E and latency-improvement sequence. + +The initial work separated first visible frame readiness from background reload, but later review showed that user-visible startup latency must be measured at dashboard content-ready, not first frame or single-row readiness. The later Tickets added dashboard snapshot readiness, shell-enter launch-path coverage, live workspace measurements, and the actual startup fix for duplicate Pod probes/session-log scans. + +Relevant follow-ups: +- 00001KV62PF32: corrected readiness away from first frame / weak row count; +- 00001KVDETSN6: dashboard content-ready snapshot metric; +- 00001KVDQH839: shell-enter launch-path measurement; +- 00001KVF0ZJM5: fixed live startup by reusing initial Pod list presence and avoiding session-log reads before first rows. + + --- diff --git a/.yoi/tickets/00001KV62PF32/item.md b/.yoi/tickets/00001KV62PF32/item.md index 185a55ce..cec1510b 100644 --- a/.yoi/tickets/00001KV62PF32/item.md +++ b/.yoi/tickets/00001KV62PF32/item.md @@ -1,8 +1,8 @@ --- title: 'Panel startup latency E2E を一覧データ描画完了基準に修正する' -state: 'done' +state: 'closed' created_at: '2026-06-15T16:44:06Z' -updated_at: '2026-06-18T13:30:51Z' +updated_at: '2026-06-19T05:44:09Z' assignee: null readiness: 'implementation_ready' risk_flags: ['panel', 'e2e', 'startup-latency', 'readiness-metric', 'ticket-list-rendering'] diff --git a/.yoi/tickets/00001KV62PF32/resolution.md b/.yoi/tickets/00001KV62PF32/resolution.md new file mode 100644 index 00000000..6e487e83 --- /dev/null +++ b/.yoi/tickets/00001KV62PF32/resolution.md @@ -0,0 +1,8 @@ +Closed as superseded/completed by the later dashboard content-ready and live startup latency work. + +This Ticket corrected the mistaken premise that first frame readiness represented usable Panel startup readiness, but its single fixture-row rows-ready metric was later judged insufficient for the user-visible delay. Follow-up work strengthened the metric to dashboard content-ready snapshot validation and then used live-path measurements to identify and fix the Pod status probe/session-log startup bottleneck. + +Relevant follow-ups: +- 00001KVDETSN6: user-visible dashboard content-ready metric and snapshot validation; +- 00001KVDQH839: shell-enter launch-path readiness measurement; +- 00001KVF0ZJM5: live startup latency fix by removing duplicate Pod probes and session-log reads from the initial list path. diff --git a/.yoi/tickets/00001KV62PF32/thread.md b/.yoi/tickets/00001KV62PF32/thread.md index 2447ee9e..0881891c 100644 --- a/.yoi/tickets/00001KV62PF32/thread.md +++ b/.yoi/tickets/00001KV62PF32/thread.md @@ -294,4 +294,29 @@ The current result still does not answer the user-facing latency problem. The pr Do not treat fixture first-frame or single-row readiness numbers as evidence that no improvement is needed. The acceptance criterion must be strengthened to a user-visible dashboard-content-ready point and paired with slow-source attribution/improvement for the live-like Panel startup path. +--- + + + +## State changed + +Ticket を closed にしました。 + + +--- + + + +## 完了 + +Closed as superseded/completed by the later dashboard content-ready and live startup latency work. + +This Ticket corrected the mistaken premise that first frame readiness represented usable Panel startup readiness, but its single fixture-row rows-ready metric was later judged insufficient for the user-visible delay. Follow-up work strengthened the metric to dashboard content-ready snapshot validation and then used live-path measurements to identify and fix the Pod status probe/session-log startup bottleneck. + +Relevant follow-ups: +- 00001KVDETSN6: user-visible dashboard content-ready metric and snapshot validation; +- 00001KVDQH839: shell-enter launch-path readiness measurement; +- 00001KVF0ZJM5: live startup latency fix by removing duplicate Pod probes and session-log reads from the initial list path. + + --- diff --git a/.yoi/tickets/00001KVDQH839/item.md b/.yoi/tickets/00001KVDQH839/item.md index 1600bf19..21912c1b 100644 --- a/.yoi/tickets/00001KVDQH839/item.md +++ b/.yoi/tickets/00001KVDQH839/item.md @@ -1,8 +1,8 @@ --- title: 'Panel E2E に shell Enter 起動経路の dashboard readiness 計測を追加する' -state: 'done' +state: 'closed' created_at: '2026-06-18T16:02:56Z' -updated_at: '2026-06-18T16:03:59Z' +updated_at: '2026-06-19T05:44:09Z' assignee: null readiness: 'implementation_ready' risk_flags: ['panel', 'e2e', 'startup-latency', 'shell-launch', 'dashboard-content-ready'] diff --git a/.yoi/tickets/00001KVDQH839/resolution.md b/.yoi/tickets/00001KVDQH839/resolution.md new file mode 100644 index 00000000..66a7a298 --- /dev/null +++ b/.yoi/tickets/00001KVDQH839/resolution.md @@ -0,0 +1,10 @@ +Closed as completed. + +Added E2E coverage for a Panel shell-enter launch path: +- PTY starts `/bin/sh` and sends `exec panel ...` as the command line; +- measurement starts immediately before sending the command line / Enter-equivalent input; +- the test waits for the existing dashboard content-ready snapshot rather than first frame or a single row; +- isolated HOME/XDG/runtime fixture remains in place and `YOI_POD_RUNTIME_COMMAND` is pinned to the tested binary; +- direct-spawn Panel readiness tests remain as separate coverage. + +Validation was recorded during implementation, including the focused shell-enter test, the full Panel E2E test set, relevant cargo check, formatting, diff check, ticket doctor, and Nix build. diff --git a/.yoi/tickets/00001KVDQH839/thread.md b/.yoi/tickets/00001KVDQH839/thread.md index 5f82d5fb..0c22ff7a 100644 --- a/.yoi/tickets/00001KVDQH839/thread.md +++ b/.yoi/tickets/00001KVDQH839/thread.md @@ -4,4 +4,31 @@ LocalTicketBackend によって作成されました。 +--- + + + +## State changed + +Ticket を closed にしました。 + + +--- + + + +## 完了 + +Closed as completed. + +Added E2E coverage for a Panel shell-enter launch path: +- PTY starts `/bin/sh` and sends `exec panel ...` as the command line; +- measurement starts immediately before sending the command line / Enter-equivalent input; +- the test waits for the existing dashboard content-ready snapshot rather than first frame or a single row; +- isolated HOME/XDG/runtime fixture remains in place and `YOI_POD_RUNTIME_COMMAND` is pinned to the tested binary; +- direct-spawn Panel readiness tests remain as separate coverage. + +Validation was recorded during implementation, including the focused shell-enter test, the full Panel E2E test set, relevant cargo check, formatting, diff check, ticket doctor, and Nix build. + + ---