From 5b6816956f611f4e79d8cd914acf51bb6c64097c Mon Sep 17 00:00:00 2001 From: PJ Date: Sun, 16 Aug 2026 00:50:06 +0530 Subject: [PATCH] docs(ci): the cross-fade wait does not fire on ci, say so --- docs/development/ci.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/development/ci.md b/docs/development/ci.md index cf38fd6..ad00e50 100644 --- a/docs/development/ci.md +++ b/docs/development/ci.md @@ -146,10 +146,13 @@ shorter budget would never see the bonus. A full run costs about five minutes. That step number was measured on a local emulator with animations ON, and the CI job sets `disable-animations: true`, so it does not describe the CI leg. The worry that follows is that zeroing the 700ms Compose fade would stop the leg -exercising the cross-fade wait entirely. The first real dispatch says otherwise: -its 200-step trace carries 4 `transitional` steps, so the wait still fires, just -far less often than it does locally. Treat the android number as an order of -magnitude, not a pin. It is a health gate, so nothing keys on it. +exercising the cross-fade wait entirely, and the traces say that worry is +largely right. The first dispatch, whose run was stuck on one screen, carried 4 +`transitional` steps in 200. The healthy runs since carry **zero**. So on CI the +wait almost never fires, and a leg that is green there is not evidence the wait +works. Local runs with animations on are where that gets exercised. Treat the +android number as an order of magnitude, not a pin. It is a health gate, so +nothing keys on it. Repeating the ios leg by hand needs nothing special now, because the run clears the app's state itself. It used to: `just ios` installs over the top without