mirror of
https://github.com/stablyai/orca.git
synced 2026-11-19 04:23:57 +00:00
* Show CI result lines on the phone, following the desktop setting The host now sends nativeChatCiResultLines resolved in settings.get, the ready snapshot and a nativeChatCiResultLinesChanged event, from one publisher that tracks each pushed chat preference separately. The phone keeps one store per desktop connection and preference, reads the CI value only from the paired desktop, and hides the lines until that desktop reports one. CI rows stay in the projection and are filtered after it, so a flip rebuilds nothing. The phone draws the line with links to the pull request and commit. * Let the phone CI line wrap and select like other notices Long repository names at large font scale no longer push the commit link past an ellipsis: the line wraps, centered, with the icon on its first line. Its text follows the system-notice selection policy, so iOS selects natively and Android keeps the long-press actions sheet. The CI strings are translated in every mobile locale, the filter copies only once it meets a CI row, and the tests drop a token assertion and a duplicate case. * Draw CI results as one-line cards on desktop and phone The CI result line becomes a one-line card in the same frame as the opened pull request card, with the Hide button inline at its right end on desktop, and in the phone's chat card frame without one. Only the lead and pull request name truncate, so the commit link and the Hide button stay reachable on narrow widths. The fixture uses real percent-encoded item ids so its links render. * Make the CI card's whole lead open its pull request A translated lead at large font scale can push the ellipsis before repo#N, which left no visible way to open the pull request. The truncating segment is now the pull request's target on desktop and phone, named for it, while "at <sha>" stays the commit's own target. The ja, zh and zh-Hant leads use a plain colon so the space after it isn't doubled. * Read the CI result lines setting only for structured chats CI result lines come only from structured sessions' journals, so a terminal chat no longer sends the setting read. The prompt-controller fixture stubs the setting hook: its tests count only the chat's prompt writes, and the structured chat's one read per desktop connection is expected.