cebe2168ab
visibleClarifyCard() bottomed out in queryVisible(), which only drops [data-pane-hidden] and then returns the first remaining DOM match. That is enough to tell a foreground tab from a background one, but a split layout has two chat surfaces on screen at once: both cards survive the hidden-pane filter, so the winner is decided by document order. The earlier zone owns Enter and 1..N permanently and the other visible card can never receive its own shortcut — worse than the mount-order behaviour it replaced, because mount order at least changed as panes came and went. Break the tie on the ladder the app already has instead of inventing a second notion of which surface is "the" one: tree/store's tabTargetGroup walks hovered zone, then focused zone, and every tab verb (Cmd+1..9, Ctrl+Tab, the Cmd+W family) targets through it; composerTargetInHoveredZone (#74447) mirrors it for the model hotkey. visibleClarifyCard now does the same, matching each visible card's closest [data-tree-group] against those rungs. The single-card path short-circuits before any store read, so the common case costs nothing extra. The final fallback stays document order rather than null on purpose. When neither rung names a zone holding a card — pointer off every zone, nothing interacted with yet — returning null would leave Enter doing nothing at all, a strictly worse regression than answering the first visible card. Regression coverage pins both halves: the resolver unit tests assert the active zone selects either card (not just the later one), that hover overrides focus, that a hovered zone with no card falls through to the focused one, and that neither rung resolving still yields a card; the ClarifyTool integration tests render two visible cards in two zones and assert exactly one clarify.respond fires, carrying whichever zone is focused. All four order-sensitive assertions fail against the previous resolver.