664e563fca
Opening a conversation used to start at the top, so the operator first had to scroll down past everything already said to find the current turn. The transcript now opens at its newest message, follows it while the operator reads the newest part, and offers a jump-to-latest affordance when they have deliberately scrolled up instead. - Opening at the newest message. The transcript's list state is created the moment the conversation first has content, with its first visible item set by chatFirstScroll (ui/chat/ChatScroll.kt): a position the operator left is restored and clamped with the app's shared rule (restoredScrollAnchor), and every other conversation starts at its newest item. "A position of their own" is explicit now: ChatThread.scroll is nullable, null meaning the operator has never left a position here, so a chat left at the very top (ChatScrollPosition(0, 0)) is restored rather than mistaken for "new", and a list state that never held content saves nothing. Placement is unanimated, on the list's first measure, and goes through the one scroll path below. - One scroll path, changed deliberately. The existing follow scroll, the app bar's approval jump and the new jump-to-latest all go through LazyListState.scrollToEnd(itemCount, animated); when the newest item sits entirely below the fold it is brought in first, and any part still below is then closed by exactly that distance (closeBottomGap). An item already partly visible is only gap-closed, so following a growing stream never bounces. The distance is measured against the transcript's content count (chatBottomDistancePx), not the layout's stale count, so an item appended ahead of the measure that shows it actually arrives in view. - Follow while reading the newest part. Only the operator's own drag changes following (a DragInteraction.Start stops it, a settling Stop/Cancel resumes it at or within the threshold, chatFollowsAt); while it holds, an arriving message, a streamed delta, a tool chip, a freshly arrived approval card, a grown composer or the appearing keyboard re-follows smoothly. The item count is read at use time (rememberUpdatedState) so a captured count cannot go stale. Programmatic scrolls never touch the list's interactionSource. - Threshold. CHAT_FOLLOW_THRESHOLD_DP (ui/theme/Dimens.kt) is 32dp: about one comfortable line of text. - Jump to latest. A small Material 3 SmallFloatingActionButton (the already-declared KeyboardArrowDown icon, on the shared gutter token) is offered only while the view is not following and there is genuinely something below the fold (chatShowJumpToLatest), hidden at the bottom or for an empty transcript; tapping it re-engages the follow. A pending permission/approval is still brought into view as the existing code did - it is the transcript's last item, so the follow brings it in while the operator reads the newest part, and the app bar's approval action still jumps straight to it. android/ only: no dependency added beyond the already-declared material-icons-extended, no run is started from the app, and no Pipelines server, Go source, installer or Docker file is touched. Checks: the packaged authoring skill references need no update - they document the Pipelines server's own contract, not the Android client, and this change is app-side only, so nothing in them became stale. There are no packaged templates in this repository. The repository's topic doc for the client, android/README.md, is updated in this change with the flow, the threshold, the one scroll path and what remains unverified on a device. Verified by the review stage on this tree: gradle --no-daemon :app:testDebugUnitTest :app:assembleDebug -> BUILD SUCCESSFUL, 50 suites / 458 tests / 0 failures / 0 errors / 0 skipped (including the new ChatScrollTest, 11 cases), and the published APK matches the freshly built app-debug.apk byte-for-byte.