Naiyuan Qing 28b6f368b9 fix(editor): index @mention selection by rendered order (MUL-3607) ...

The @mention popup navigated and committed by indexing the flat
`displayItems` array, but rendered rows in the re-bucketed order from
`groupItems()` (current → recent → search → users → issues). In chat
(context mode) the async server-search results are appended to the end
of `displayItems` yet tagged `group:"search"`, so `groupItems()` hoists
them near the top. The highlighted row and the committed item then point
at different entries — you select one target but mention its neighbour
(the reported "@bohan picks the next one" off-by-one).

Make the flattened grouped order (`orderedItems`) the single index space
for `selectedIndex`, arrow keys, Enter, and clicks, so the highlighted
row is always the committed item. Plain issue-comment mentions (default
mode) were already safe — no group tags means `groupItems()` is
order-preserving — and stay unchanged.

Adds a regression test asserting highlighted row == committed item when
the list is reordered by a hoisted search result.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

2026-06-24 09:37:42 +08:00

..

core

fix(transcript): live-update issue/agent transcript dialog from shared cache (#4452)

2026-06-23 16:35:29 +08:00

eslint-config

fix(deps): add eslint phantom dep detection + fix existing violations (MUL-2654) (#3249)

2026-05-26 09:42:29 +08:00

tsconfig

…

ui

fix(views): gate right sidebar motion to toggles (#4335)

2026-06-19 16:40:49 +08:00

views

fix(editor): index @mention selection by rendered order (MUL-3607)

2026-06-24 09:37:42 +08:00