fix(mobile): enlarge compact icon tap targets to the 28dp audit floor

[iscekic]

Changelog for users

• Icon-only controls on the Agents and PR discussion screens are easier to tap.
• Filter sessions, Clear search, Resolve thread, and Comment actions each measure at least 28dp on a side.
• Each control still does its job: opens filters, clears the search query, resolves the thread, or opens comment actions.
• The visible icons and circles keep their compact size; only the tappable frame grew.
• The search field keeps its height when the X appears, so the list does not jump.

Changelog for maintainers

• lib/a11y/touch-target.ts is new: it records the 28dp audited floor, the 38.5pt h-11 frame, and the 3pt slop that reaches 44pt.
• Audited controls now size the Pressable frame (h-11 w-11); the glyph or circle stays small inside it.
• Filter sessions, Clear search, and Resolve thread share the 3pt slop; their rows and the search field reserve the frame's height.
• Resolve thread's header row switched to items-center and holds the full frame; a negative margin would leave part of the target outside the touchable parent.
• Comment actions keeps its full frame in the author row, and its left tap band is recomputed from the frame inset plus slop so clearance from the Fix with Kilo pill is preserved.
• The filter badge stays pinned to the 20pt glyph corner rather than the enlarged frame.
• Review the search field first: py-1.5 was removed and min-h-[44px] added, which changes the header's layout.
• Risk to watch: NativeWind's 14pt rem renders h-7 at 24.5pt, so audited controls must use explicit px or h-11.

E2E proof

[e1] Agents tab, live sessions (agents-live), dark mode: run the control-size audit — the 'Filter sessions' control measures at least 28dp on both sides, and tapping it opens the filter sheet. — android emulator-5554 in Dark: the agents-live 'Filter sessions' control renders bounds [922,172][1023,273] in e1-hierarchy.txt = 101x101 px = 38.5dp at the 2.625 density, at least 28dp on both sides, and tapping it opened the filter sheet (e1-scene.log ends with 'SCENE e1 OK' on the PLATFORM/CLI/PROJECT/Apply sheet, matching e1-filter-sheet-digest.log); no UX-DEFECT observed.

[e3] Agents history search with a query typed (sessions-search-empty): 'Filter sessions' and 'Clear search' each measure at least 28dp on both sides; the search field does not change height when the first… — android emulator-5554: with the query typed, 'Filter sessions' bounds [942,149][1043,250] and 'Clear search' bounds [900,293][1001,394] in e3-search-hierarchy.txt are each 101x101 px = 38.5dp (at least 28dp on both sides), the search field measures 109px tall in both the empty state ([163,289][984,398], e3-empty-hierarchy.txt) and the typed state ([163,289][883,398], e3-search-hierarchy.txt) so the first keystroke causes no layout shift, and tapping the X cleared the field (e3-cleared-digest.log shows the list and no Clear search button); no UX-DEFECT observed.

[e2] Agents history list (sessions-all): the 'Filter sessions' control measures at least 28dp on both sides and opens the filter sheet when tapped. — android emulator-5604: Filter sessions node bounds="[942,149][1043,250]" = 101x101px at dpi: 420x420 = 38.5dp on both sides (>=28), and tapping it opened the filter sheet (text="PLATFORM", content-desc="Cloud"); screenshots e2-sessions-all.png, e2-filter-sheet.png; no UX-DEFECT.

[e2] Agents history list (sessions-all): the 'Filter sessions' control measures at least 28dp on both sides and opens the filter sheet when tapped.

[e4] PR discussion with an unresolved thread (pr-discussion-comment): 'Resolve thread' and 'Comment actions' each measure at least 28dp on both sides, the thread header label stays vertically aligned with… — android emulator-5604, github-stub fixture kilo-stub/discussion-mixed#1: Resolve thread bounds="[908,499][1009,600]" and both Comment actions bounds="[908,1183][1009,1284]" / "[908,1554][1009,1655]" = 101x101px at dpi: 420x420 = 38.5dp on both sides (>=28); label bounds="[132,528][889,571]" center y=549.5 equals resolve center y=549.5; taps moved the thread to content-desc="Unresolve thread" + text="RESOLVED" and opened the sheet (content-desc="Report content", "Mute"); screenshots e4-pr-discussion.png, e4-action-sheet.png; no UX-DEFECT.

[e4] PR discussion with an unresolved thread (pr-discussion-comment): 'Resolve thread' and 'Comment actions' each measure at least 28dp on both sides, the thread header label stays vertically aligned with…

E2E proof — log excerpts

[e1] Agents tab, live sessions (agents-live), dark mode: control-size audit + fi -> pass :: android emulator-5554 in Dark: the agents-live 'Filter sessions' control renders bounds [922,172][1023,273] in e1-hierarchy.txt = 101x101 px = 38.5dp at the 2.625 density, at least 28dp on both sides, and tapping it opened the filter sheet (e1-scene.log ends with 'SCENE e1 OK' on the PLATFORM/CLI/PROJECT/Apply sheet, matching e1-filter-sheet-digest.log); no UX-DEFECT observed.
[e3] Agents history search with a query typed (sessions-search-empty) -> pass :: android emulator-5554: with the query typed, 'Filter sessions' bounds [942,149][1043,250] and 'Clear search' bounds [900,293][1001,394] in e3-search-hierarchy.txt are each 101x101 px = 38.5dp (at least 28dp on both sides), the search field measures 109px tall in both the empty state ([163,289][984,398], e3-empty-hierarchy.txt) and the typed state ([163,289][883,398], e3-search-hierarchy.txt) so the first keystroke causes no layout shift, and tapping the X cleared the field (e3-cleared-digest.log shows the list and no Clear search button); no UX-DEFECT observed.
[e2] Agents history list (sessions-all) -> pass :: android emulator-5604: Filter sessions node bounds="[942,149][1043,250]" = 101x101px at dpi: 420x420 = 38.5dp on both sides (>=28), and tapping it opened the filter sheet (text="PLATFORM", content-desc="Cloud"); screenshots e2-sessions-all.png, e2-filter-sheet.png; no UX-DEFECT.
[e4] PR discussion with an unresolved thread (pr-discussion-comment) -> pass :: android emulator-5604, github-stub fixture kilo-stub/discussion-mixed#1: Resolve thread bounds="[908,499][1009,600]" and both Comment actions bounds="[908,1183][1009,1284]" / "[908,1554][1009,1655]" = 101x101px at dpi: 420x420 = 38.5dp on both sides (>=28); label bounds="[132,528][889,571]" center y=549.5 equals resolve center y=549.5; taps moved the thread to content-desc="Unresolve thread" + text="RESOLVED" and opened the sheet (content-desc="Report content", "Mute"); screenshots e4-pr-discussion.png, e4-action-sheet.png; no UX-DEFECT.

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e1-hierarchy.txt

<redacted>
                                        </com.horcrux.svg.GroupView>
                                      </com.horcrux.svg.SvgView>
<redacted>
                                    </android.view.View>
                                  </android.view.ViewGroup>
                                </android.view.ViewGroup>
                              </android.view.ViewGroup>
                            </android.widget.ScrollView>
                          </android.view.ViewGroup>
                        </android.view.ViewGroup>
                      </android.view.ViewGroup>
<redacted>
                    </android.view.ViewGroup>
                  </android.view.ViewGroup>
                </android.view.ViewGroup>
              </android.widget.FrameLayout>
            </android.widget.FrameLayout>
          </android.widget.FrameLayout>
        </android.widget.LinearLayout>
      </android.widget.FrameLayout>
    </android.widget.LinearLayout>
  </android.widget.FrameLayout>
</hierarchy>

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e1-scene.log

android.widget.TextView PLATFORM tappable [101,355][979,392]
android.widget.CheckBox CLI tappable [101,401][979,493]
android.widget.TextView CLI tappable [202,423][952,469]
android.widget.TextView PROJECT tappable [101,530][979,567]
android.widget.CheckBox Kilo-Org/cloud tappable [101,576][979,668]
android.widget.TextView Kilo-Org/cloud tappable [202,598][952,644]
android.widget.Button Cancel tappable [613,704][794,820]
android.widget.TextView Cancel tappable [652,738][754,784]
android.widget.Button Apply tappable [821,704][979,820]
android.widget.TextView Apply tappable [857,738][941,784]
SCENE e1 OK
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.view.ViewGroup Filter sessions tappable [55,216][1025,866]
android.view.View Filter sessions tappable [100,261][978,317]
android.widget.TextView PLATFORM tappable [101,355][979,392]
android.widget.CheckBox CLI tappable [101,401][979,493]
android.widget.TextView CLI tappable [202,423][952,469]
android.widget.TextView PROJECT tappable [101,530][979,567]
android.widget.CheckBox Kilo-Org/cloud tappable [101,576][979,668]
android.widget.TextView Kilo-Org/cloud tappable [202,598][952,644]
android.widget.Button Cancel tappable [613,704][794,820]
android.widget.TextView Cancel tappable [652,738][754,784]
android.widget.Button Apply tappable [821,704][979,820]
android.widget.TextView Apply tappable [857,738][941,784]

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e1-filter-sheet-digest.log

# e1 evidence — device accessibility digest captured by the sim tools on
# emulator-5554 (android), app in Dark appearance, Agents tab (agents-live,
# 1 LIVE), immediately after tapping the "Filter sessions" control.
# The tap opened the filter sheet below.
android.view.ViewGroup "Filter sessions" [ref=e1]
android.view.View "Filter sessions" [ref=e2]
TextView "PLATFORM" [ref=e3]
CheckBox "CLI" [ref=e4]
TextView "CLI" [ref=e5]
TextView "PROJECT" [ref=e6]
CheckBox "Kilo-Org/cloud" [ref=e7]
TextView "Kilo-Org/cloud" [ref=e8]
Button "Cancel" [ref=e9]
TextView "Cancel" [ref=e10]
Button "Apply" [ref=e11]
TextView "Apply" [ref=e12]

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e3-search-hierarchy.txt

<redacted>
<redacted>
                                        </com.horcrux.svg.GroupView>
                                      </com.horcrux.svg.SvgView>
                                    </android.view.View>
                                  </android.view.ViewGroup>
                                </android.view.ViewGroup>
                              </android.view.ViewGroup>
                            </android.widget.ScrollView>
                          </android.view.ViewGroup>
                        </android.view.ViewGroup>
                      </android.view.ViewGroup>
<redacted>
                    </android.view.ViewGroup>
                  </android.view.ViewGroup>
                </android.view.ViewGroup>
              </android.widget.FrameLayout>
            </android.widget.FrameLayout>
          </android.widget.FrameLayout>
        </android.widget.LinearLayout>
      </android.widget.FrameLayout>
    </android.widget.LinearLayout>
  </android.widget.FrameLayout>
</hierarchy>

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e3-empty-hierarchy.txt

<redacted>
                                        </com.horcrux.svg.GroupView>
                                      </com.horcrux.svg.SvgView>
<redacted>
                                    </android.view.View>
                                  </android.view.ViewGroup>
                                </android.view.ViewGroup>
                              </android.view.ViewGroup>
                            </android.widget.ScrollView>
                          </android.view.ViewGroup>
                        </android.view.ViewGroup>
                      </android.view.ViewGroup>
<redacted>
                    </android.view.ViewGroup>
                  </android.view.ViewGroup>
                </android.view.ViewGroup>
              </android.widget.FrameLayout>
            </android.widget.FrameLayout>
          </android.widget.FrameLayout>
        </android.widget.LinearLayout>
      </android.widget.FrameLayout>
    </android.widget.LinearLayout>
  </android.widget.FrameLayout>
</hierarchy>

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e3-cleared-digest.log

# e3 evidence — device accessibility digest captured by the sim tools on
# emulator-5554 (android), the same history screen after tapping the Clear
# search X: the query is gone (the X button no longer renders) and the two
# sessions are listed again.
Button "Go back" [ref=e1]
android.view.View "Agents" [ref=e2]
Button "Filter sessions" [ref=e3]
EditText "Search sessions" [ref=e4]
TextView "TODAY" [ref=e5]
TextView "2" [ref=e6]
Button "60-message pagination fixture, CLOUD AGENT, and cost 3 cents, 1 minute ago" [ref=e7]
TextView "CLOUD AGENT" [ref=e8]
TextView "$0.03 · 1 MINUTE AGO" [ref=e9]
TextView "60-message pagination fixture" [ref=e10]
Button "New session - 2026-09-19T20:28:54.092Z, LIVE, kwf/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10, CLOUD, and cost 1 cent, 3 minutes ago" [ref=e11]
TextView "CLOUD" [ref=e12]
TextView "$0.01 · 3 MINUTES AGO" [ref=e13]
TextView "New session - 2026-09-19T20:28:54.092Z" [ref=e14]
TextView "kwf/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10" [ref=e15]
android.view.View "Home, tab, 1 of 3" [ref=e16]
android.view.View "Agents, tab, 2 of 3" [checked] [ref=e18]
android.view.View "Profile, tab, 3 of 3" [ref=e20]

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e2-measure.log

# e2 evidence: sessions-all (Agents history list)
# node from e2-sessions-all.txt:
<redacted>
# device density from emulator-shard2.log:
Setting display: 0 configuration to: 1080x2400, dpi: 420x420
# tap Filter sessions -> filter sheet opened (node from e2-filter-sheet.txt):
<redacted>
<redacted>
<redacted>

/home/igor_kilocode_ai/.local/share/kwf/sections/explorer-a-control-is-too-small-to-tap-reliably-8678dfa6-6b10/e2e-mobile-app/e4-measure.log

# e4 evidence: pr-discussion-comment (kilo-stub/discussion-mixed#1)
# nodes from e4-pr-discussion.txt:
<redacted>
<redacted>
<redacted>
<redacted>
# device density from emulator-shard2.log:
Setting display: 0 configuration to: 1080x2400, dpi: 420x420
# tap Resolve thread -> thread state moved (nodes from e4-action-sheet.txt):
<redacted>
<redacted>
# tap Comment actions -> action sheet opened (nodes from e4-action-sheet.txt):
<redacted>
<redacted>

Owner request

Explorer finding: a control is too small to tap reliably

The user-agent explorer found this while using the app like a user.
One finding per item; the explorer never edits product code.

Flow: accessibility
Found on revision: 5327758

Repro:

1. set this state first: account e2e-firstrun-1789824457@example.com (brand-new first-run, $25 credits, second org e2e-org-1789843831@example.com, 4 Code Reviewer pull requests, one top-level busy session ses_f44fdefd0ffe1trJniRFsJnxhL); device portrait, system night mode.; the device in dark mode
2. open the app on emulator-5554
3. reach the screen named agents-live, pr-discussion-comment, sessions-all
4. the capture shows the defect named below

Observed: controls below 28dp on a side: agents-live: 1 small control(s): Filter sessions (52x52px) pr-discussion-comment: 2 small control(s): Resolve thread (64x64px); Comment actions (64x65px) sessions-all: 1 small control(s): Filter sessions (52x53px) sessions-search-empty: 2 small control(s): Filter sessions (52x53px); Clear search (42x42px)
Expected: every control is at least 28dp on a side

Evidence (from the device run):

Production record (automatic, 2026-09-19):

Production record for ses_f44fdefd0ffe1trJniRFsJnxhL

Axiom, last 72 h

No line carries this term in: vercel, cloudflare-logpush, supabase-production.

The session row, read replica

No row in cli_sessions_v2 carries ses_f44fdefd0ffe1trJniRFsJnxhL.

Log archives, R2 kilocode-sessions

NOT READ: R2 keys are indexed by the agent id, not the session id; take the agent_* from the worker logs above and query that.

Sentry, last 72h

No Sentry issue carries this term.

Open findings (not fixed here)

• not proved live: agents-live.png is no longer on the host that took it, so no publish can carry it
• not proved live: pr-discussion-comment.png is no longer on the host that took it, so no publish can carry it
• not proved live: sessions-all.png is no longer on the host that took it, so no publish can carry it
• not proved live: sessions-search-empty.png is no longer on the host that took it, so no publish can carry it

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The current head re-verifies the compact-control geometry change: the previously reported clearance/rem inconsistency is resolved (gap-3 measures 10.5dp at NativeWind's 14pt rem, and commentTrailingControlsClearanceDp() returns 5.5dp), and the only delta since the last reviewed commit in PR-owned files is an inert reason-string tweak in case-guard.test.ts (its value is not read by the guard). No new issues found in the changed code.

Files Reviewed (14 files)

• apps/mobile/src/components/agents/session-filter-button.tsx
• apps/mobile/src/components/agents/session-filter-button.mounted.test.tsx
• apps/mobile/src/components/agents/session-list-search-header.tsx
• apps/mobile/src/components/agents/session-list-search-header.touch-target.test.tsx
• apps/mobile/src/components/pr-review/discussion/comment-row.tsx
• apps/mobile/src/components/pr-review/discussion/comment-row.touch-target.test.tsx
• apps/mobile/src/components/pr-review/discussion/discussion-thread.tsx
• apps/mobile/src/components/pr-review/discussion/discussion-thread.touch-target.test.tsx
• apps/mobile/src/components/pr-review/discussion/pr-comment-fix-with-kilo.tsx
• apps/mobile/src/lib/a11y/touch-target.ts
• apps/mobile/src/lib/a11y/touch-target.test.ts
• apps/mobile/src/lib/case-guard.test.ts
• apps/mobile/src/lib/pr-review/comment-trailing-controls.ts
• apps/mobile/src/lib/pr-review/comment-trailing-controls.test.ts

Previous Review Summaries (2 snapshots, latest commit 995e3a7)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 995e3a7)

Status: No Issues Found | Recommendation: Merge

Executive Summary

The incremental change re-derives the trailing-control clearance from the frame-to-frame gap-3 (10.5pt at NativeWind's 14pt rem) minus the two facing hit slops, resolving the previous review's clearance/rem inconsistency with no new issues in the changed files.

Files Reviewed (5 files)

• apps/mobile/src/components/pr-review/discussion/comment-row.tsx
• apps/mobile/src/components/pr-review/discussion/pr-comment-fix-with-kilo.tsx
• apps/mobile/src/lib/case-guard.test.ts
• apps/mobile/src/lib/pr-review/comment-trailing-controls.test.ts
• apps/mobile/src/lib/pr-review/comment-trailing-controls.ts

Previous review (commit 981ddbb)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
apps/mobile/src/lib/pr-review/comment-trailing-controls.ts	54	commentTrailingControlsClearanceDp() no longer returns the tap-area separation its doc describes, and COMMENT_TRAILING_CONTROLS_GAP_DP = 12 is inconsistent with the rem=14 model this PR establishes (gap-3 = 10.5pt).

Files Reviewed (12 files)

• apps/mobile/src/lib/a11y/touch-target.ts - new geometry constants; no issues
• apps/mobile/src/lib/a11y/touch-target.test.ts - no issues
• apps/mobile/src/lib/pr-review/comment-trailing-controls.ts - 1 issue
• apps/mobile/src/lib/pr-review/comment-trailing-controls.test.ts - no issues
• apps/mobile/src/components/agents/session-filter-button.tsx - no issues
• apps/mobile/src/components/agents/session-filter-button.mounted.test.tsx - no issues
• apps/mobile/src/components/agents/session-list-search-header.tsx - no issues
• apps/mobile/src/components/agents/session-list-search-header.touch-target.test.tsx - no issues
• apps/mobile/src/components/pr-review/discussion/comment-row.tsx - no issues
• apps/mobile/src/components/pr-review/discussion/comment-row.touch-target.test.tsx - no issues
• apps/mobile/src/components/pr-review/discussion/discussion-thread.tsx - no issues
• apps/mobile/src/components/pr-review/discussion/discussion-thread.touch-target.test.tsx - no issues

Fix Link

Fix these issues in Kilo Cloud

---

_{Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0}

_{Review guidance: REVIEW.md from base branch main}

[iscekic]

This description names a scenario the proof did not capture:

• not proved live: agents-live.png is no longer on the host that took it, so no publish can carry it

A repeated proof run rebuilds the same evidence, so no proof run is dispatched for a named gap. Merging with this gap open is your decision.