[Bug]: Mobile: an expanded group of thoughts has no bottom margin, so a clipped thought runs into the next reply#25283

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/mobile

Steps to reproduce

1. On mobile, open a thread where the agent wrote several thoughts in a row, long enough together to fill more than the capped thought box.
2. Expand the group of thoughts in the work log.
3. Look at where the box ends and the next reply starts.

Expected behavior

The thought box ends with the same bottom gap as the other work log rows, and it is clear the thought continues inside the box.

Actual behavior

The clipped thought ends flush against the reply below it, so it reads as part of the reply.

In apps/mobile/src/features/threads/thread-work-log.tsx (main @ f88b33a16d), a group made only of reasoning rows renders as a bare <ScrollView nestedScrollEnabled className="ml-7 max-h-96 py-1">. Every other row goes through WorkLogBlock (work-log-layout.tsx), which adds mb-1 unless the row continues into the next one. The box also gives no cue that its content is clipped.

Impact

Cosmetic issue

Version or commit

main @ f88b33a16d (code trace). Seen on a fork build based on 0b42aa9476.

Environment

Android app built from source. No capture attached.

For reference, our fork wraps the box in WorkLogBlock and fades its bottom edge while the thought is clipped and not scrolled to the end: https://github.com/jason5545/t3code/commit/4651080f77