"+ Add else branch" and "Remove else branch" on a condition step drop keyboard focus to <body>: each one is unmounted by the change it makes (the add button is replaced by the Else list, the remove button goes with the branch), and nothing puts focus back. "Remove branches" does the same when it turns a branch into a gate. Their names ("Add else branch", "Remove else branch", "Remove branches") are also the same on every condition step, so a screen-reader user cannot tell which condition they belong to.
How I know: in a happy-dom test rendering AutomationForm with one condition step that has a Then branch, focusing and clicking "+ Add else branch", then "Remove else branch", left document.activeElement as BODY after each, and both buttons were disconnected.
Where to start: renderConditionBody in app/islands/AutomationForm.tsx (the conditionRow buttons) and removeBranches. The focusAfterRender helper and data-focus-key tags added for the step move/indent/insert controls can be reused, and the stepLabels map gives each step a name such as "step 2 (Condition)" for the accessible names.
Found by the loop while working on #61, rkey 61, branch loop/61, merged onto main as a36717445fdd.