From e9fa1b6ec9234b140dd97d0284417ed23393a554 Mon Sep 17 00:00:00 2001 From: Alan Silva Date: Tue, 10 Nov 2026 23:17:13 +0000 Subject: [PATCH] Record the floating-windows status and what the pipeline runs showed --- docs/plans/floating-windows.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/plans/floating-windows.md b/docs/plans/floating-windows.md index 11ee9d9c..4e811d9a 100644 --- a/docs/plans/floating-windows.md +++ b/docs/plans/floating-windows.md @@ -5,6 +5,21 @@ the shell that can host any content (terminal and chats first; runs, pipelines and anything else later), instead of a chat feature and a terminal feature each faking windows in their own way. +## Status (2026-11-11) + +Phases 0, 1, 2, 2b and 3 are on main (`aa6468dc`); not deployed. Details and +what was checked: `app/notes/floating-windows.md` and +`app/notes/chat-floating-pane.md`. Open: Phase 4, the items in section 6, and +these found on the way: + +- A tooltip of a window that is not on top can be covered by a window above it. +- The Cupertino code is still in the app; new work is Material only. +- "Pipelines app change" v6: a failed land gate ends the run instead of going + back to implement, transport errors use up the UI review's visit limit, and + implement runs only the task's named tests, so a removed Cupertino branch + breaks tests elsewhere that only the gate sees. Runs 303-306 all failed this + way and were finished by hand. + ## 1. Why the current floating chat is broken All findings below are from code reading (file:line on main at `1b698a12`) and