fix(mobile): center the guided tour step content vertically

[iscekic]

Changelog for users

• Every guided tour step now centers its icon, title, subtitle, and options between the header and the footer action.
• The block no longer sits against the header, so the empty lower half of the screen is gone.
• Content taller than the screen still scrolls, so the footer action stays reachable on short screens or with a large system font.
• The "Where would you like to run Kilo?" step keeps the icon, title, and subtitle in the same centered band while the computer list loads, is empty, or fails to load.

Changelog for maintainers

• ForkStep and TourRemoteStep ScrollView content containers now use grow items-center justify-center gap-* px-6 py-6.
• grow (flex-grow: 1) fills the viewport so justify-center distributes the children; it is a minimum, so taller content scrolls instead of clipping.
• Vertical padding becomes symmetric (py-6); the previous top-aligned pt-4 first-run rhythm is dropped.
• The mounted tests for both tour steps assert the new content-container classes and that CenteredState is not rendered.
• Review first: the centering depends on the parent giving the ScrollView height; check both tour steps at short and tall device heights and with a long connected-computer list.

E2E proof

[e1] Open the tour (Profile -> Tutorial replay) and land on "Where would you like to run Kilo?": the icon, title, subtitle and the Cloud Agent / Your computer cards sit vertically centred in the band… — android emulator-5554, 1080x2400: the Profile -> Tutorial replay lands on the fork step (SCENE e1 OK, e1-open.log) and e1-tall-hierarchy.xml puts the body ScrollView at [0,218][1080,2203] with the icon box [448,767][632,951] and the last card [55,1441][1025,1654] - 549 px above and 549 px below the block - title [147,988][933,1062], Skip tour [55,2221][1025,2336]; centring appearance is the visual reviewer's. NOTE: the pack's scenario line for e1 is truncated mid-sentence, so the scenario text was taken from the PR description's own E2E proof block.

[e2] On the same fork, tap "Your computer": the icon/title/subtitle block stays centred in the same band while the computer list is loading, after it resolves empty ("No computer connected yet" + Check… — android emulator-5554, 1080x2400: SCENE e2 OK (e2.log) taps Your computer and lands on the empty state 'No computer connected yet' [279,1261][800,1326] + Check again; e2-loading.log (hold from e2-fault-stall.log: 'fault.sh: stalled pids [34092] for 120s') shows the busy Check-again button [374,1593][706,1709]; e2-error.log shows 'Network error. Please try again.' [308,1520][772,1566] + Retry; SCENE e2-recovery OK (e2-recovery.log) shows tap Retry returns to 'No computer connected yet' [279,1261][800,1326]; the title [178,920][903,994] and subtitle [56,1003][1025,1115] are identical in…

[e3] On a short screen or with a large system font, the tour body starts at the top padding and scrolls to the Skip bar: nothing is clipped under the header and the cards are reachable. — android emulator-5554 at wm size 1080x1200: e3-short-entry.log shows title [147,430][933,504] with the second card [55,883][1025,1003] clipped by the viewport, and e3-short-entry-hierarchy.xml puts the body ScrollView at [0,154][1080,1003] below the QUICK TOUR header with the first child icon box at [448,209][632,393], so nothing sits under the header; one swipe up (SCENE e3-short-scrolled OK) moves the title to [147,282][933,356] with both cards [55,494][1025,707] and [55,735][1025,948] fully above Skip tour [55,1021][1025,1136]; wm size restored to 1080x2400 afterwards; scroll appearance is…

[e1] Open the tour (Profile -> Tutorial replay) and land on "Where would you lik -> pass :: android emulator-5554, 1080x2400: the Profile -> Tutorial replay lands on the fork step (SCENE e1 OK, e1-open.log) and e1-tall-hierarchy.xml puts the body ScrollView at [0,218][1080,2203] with the icon box [448,767][632,951] and the last card [55,1441][1025,1654] - 549 px above and 549 px below the block - title [147,988][933,1062], Skip tour [55,2221][1025,2336]; centring appearance is the visual reviewer's. NOTE: the pack's scenario line for e1 is truncated mid-sentence, so the scenario text was taken from the PR description's own E2E proof block.
[e2] On the same fork, tap "Your computer": the icon/title/subtitle block stays  -> pass :: android emulator-5554, 1080x2400: SCENE e2 OK (e2.log) taps Your computer and lands on the empty state 'No computer connected yet' [279,1261][800,1326] + Check again; e2-loading.log (hold from e2-fault-stall.log: '<internal>[34092] for 120s') shows the busy Check-again button [374,1593][706,1709]; e2-error.log shows 'Network error. Please try again.' [308,1520][772,1566] + Retry; SCENE e2-recovery OK (e2-recovery.log) shows tap Retry returns to 'No computer connected yet' [279,1261][800,1326]; the title [178,920][903,994] and subtitle [56,1003][1025,1115] are identical in e2-loading.log, e2-error.log, e2-empty2.log and e2-recovery.log, so the block does not shift.
[e3] On a short screen or with a large system font, the tour body starts at the  -> pass :: android emulator-5554 at wm size 1080x1200: e3-short-entry.log shows title [147,430][933,504] with the second card [55,883][1025,1003] clipped by the viewport, and e3-short-entry-hierarchy.xml puts the body ScrollView at [0,154][1080,1003] below the QUICK TOUR header with the first child icon box at [448,209][632,393], so nothing sits under the header; one swipe up (SCENE e3-short-scrolled OK) moves the title to [147,282][933,356] with both cards [55,494][1025,707] and [55,735][1025,948] fully above Skip tour [55,1021][1025,1136]; wm size restored to 1080x2400 afterwards; scroll appearance is the visual reviewer's.

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e1-open.log

SCENE e1 OK
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,2400]
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.widget.TextView QUICK TOUR tappable [37,149][1045,186]
android.view.View Where would you like to run Kilo? tappable [147,988][933,1062]
android.widget.TextView Pick where Kilo runs for your first session. tappable [191,1071][888,1127]
android.widget.RadioButton Cloud Agent, Run Kilo in a sandboxed cloud environment with nothing to install. tappable [55,1200][1025,1413]
android.widget.TextView Cloud Agent tappable [223,1230][911,1286]
android.widget.TextView Run Kilo in a sandboxed cloud environment with nothing to install. tappable [223,1290][911,1382]
android.widget.RadioButton Your computer, Run Kilo on your own machine through the `kilo remote` CLI. tappable [55,1441][1025,1654]
android.widget.TextView Your computer tappable [223,1471][911,1527]
android.widget.TextView Run Kilo on your own machine through the `kilo remote` CLI. tappable [223,1531][911,1623]
android.widget.Button Skip tour tappable [55,2221][1025,2336]
android.widget.TextView Skip tour tappable [473,2255][606,2301]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e2-loading.log

SCENE e2-loading OK
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,2400]
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.widget.Button Go back tappable [0,149][101,250]
android.widget.TextView QUICK TOUR tappable [111,179][1044,216]
android.view.View Start your first remote session tappable [178,920][903,994]
android.widget.TextView Connect your computer, then choose it below to start a new session. tappable [56,1003][1025,1115]
android.widget.TextView No computer connected yet tappable [279,1261][800,1326]
android.widget.TextView Run `kilo remote` on your computer to connect it. tappable [178,1335][901,1381]
android.widget.TextView Run `kilo remote` on your computer, or `/remote` in a running CLI session, to control a local kilo process. tappable [55,1417][1024,1555]
android.widget.Button busy [374,1593][706,1709]
android.widget.TextView Check again tappable [484,1627][666,1673]
android.widget.Button Skip tour tappable [55,2221][1025,2336]
android.widget.TextView Skip tour tappable [473,2255][606,2301]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e2.log

SCENE e2 OK
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,2400]
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.widget.Button Go back tappable [0,149][101,250]
android.widget.TextView QUICK TOUR tappable [111,179][1044,216]
android.view.View Start your first remote session tappable [178,920][903,994]
android.widget.TextView Connect your computer, then choose it below to start a new session. tappable [56,1003][1025,1115]
android.widget.TextView No computer connected yet tappable [279,1261][800,1326]
android.widget.TextView Run `kilo remote` on your computer to connect it. tappable [178,1335][901,1381]
android.widget.TextView Run `kilo remote` on your computer, or `/remote` in a running CLI session, to control a local kilo process. tappable [55,1417][1024,1555]
android.widget.Button busy tappable [410,1593][670,1709]
android.widget.TextView Check again tappable [449,1627][631,1673]
android.widget.Button Skip tour tappable [55,2221][1025,2336]
android.widget.TextView Skip tour tappable [473,2255][606,2301]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e2-fault-stall.log

<internal>[34092] for 120s

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e2-error.log

SCENE e2-error MISS tap 'Check again'
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,2400]
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.widget.Button Go back tappable [0,149][101,250]
android.widget.TextView QUICK TOUR tappable [111,179][1044,216]
android.view.View Start your first remote session tappable [178,920][903,994]
android.widget.TextView Connect your computer, then choose it below to start a new session. tappable [56,1003][1025,1115]
android.view.View Something went wrong tappable [323,1446][756,1511]
android.widget.TextView Network error. Please try again. tappable [308,1520][772,1566]
android.widget.Button Retry tappable [461,1603][619,1718]
android.widget.TextView Retry tappable [500,1637][579,1683]
android.widget.Button Skip tour tappable [55,2221][1025,2336]
android.widget.TextView Skip tour tappable [473,2255][606,2301]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e2-recovery.log

SCENE e2-recovery OK
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,2400]
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.widget.Button Go back tappable [0,149][101,250]
android.widget.TextView QUICK TOUR tappable [111,179][1044,216]
android.view.View Start your first remote session tappable [178,920][903,994]
android.widget.TextView Connect your computer, then choose it below to start a new session. tappable [56,1003][1025,1115]
android.widget.TextView No computer connected yet tappable [279,1261][800,1326]
android.widget.TextView Run `kilo remote` on your computer to connect it. tappable [178,1335][901,1381]
android.widget.TextView Run `kilo remote` on your computer, or `/remote` in a running CLI session, to control a local kilo process. tappable [55,1417][1024,1555]
android.widget.Button Check again tappable [410,1593][670,1709]
android.widget.TextView Check again tappable [449,1627][631,1673]
android.widget.Button Skip tour tappable [55,2221][1025,2336]
android.widget.TextView Skip tour tappable [473,2255][606,2301]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e2-empty2.log

SCENE e2-empty2 OK
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,2400]
android.widget.FrameLayout android:id/content tappable [0,0][1080,2400]
android.widget.Button Go back tappable [0,149][101,250]
android.widget.TextView QUICK TOUR tappable [111,179][1044,216]
android.view.View Start your first remote session tappable [178,920][903,994]
android.widget.TextView Connect your computer, then choose it below to start a new session. tappable [56,1003][1025,1115]
android.widget.TextView No computer connected yet tappable [279,1261][800,1326]
android.widget.TextView Run `kilo remote` on your computer to connect it. tappable [178,1335][901,1381]
android.widget.TextView Run `kilo remote` on your computer, or `/remote` in a running CLI session, to control a local kilo process. tappable [55,1417][1024,1555]
android.widget.Button busy tappable [410,1593][670,1709]
android.widget.TextView Check again tappable [449,1627][631,1673]
android.widget.Button Skip tour tappable [55,2221][1025,2336]
android.widget.TextView Skip tour tappable [473,2255][606,2301]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e3-short-scrolled.log

SCENE e3-short-scrolled OK
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,1200]
android.widget.FrameLayout android:id/content tappable [0,0][1080,1200]
android.widget.TextView QUICK TOUR tappable [37,85][1045,122]
android.view.View Where would you like to run Kilo? tappable [147,282][933,356]
android.widget.TextView Pick where Kilo runs for your first session. tappable [191,365][888,421]
android.widget.RadioButton Cloud Agent, Run Kilo in a sandboxed cloud environment with nothing to install. tappable [55,494][1025,707]
android.widget.TextView Cloud Agent tappable [223,524][911,580]
android.widget.TextView Run Kilo in a sandboxed cloud environment with nothing to install. tappable [223,584][911,676]
android.widget.RadioButton Your computer, Run Kilo on your own machine through the `kilo remote` CLI. tappable [55,735][1025,948]
android.widget.TextView Your computer tappable [223,765][911,821]
android.widget.TextView Run Kilo on your own machine through the `kilo remote` CLI. tappable [223,825][911,917]
android.widget.Button Skip tour tappable [55,1021][1025,1136]
android.widget.TextView Skip tour tappable [473,1055][606,1101]

/home/igor_kilocode_ai/.local/share/kwf/sections/kwf-fix-proof-e65bab1-2-8889/e2e-mobile-app/e3-short-entry.log

SCENE e3-short-entry MISS screen 'Start your first remote session' at capture
android.widget.LinearLayout com.kilocode.kiloapp:id/action_bar_root tappable [0,0][1080,1200]
android.widget.FrameLayout android:id/content tappable [0,0][1080,1200]
android.widget.TextView QUICK TOUR tappable [37,85][1045,122]
android.view.View Where would you like to run Kilo? tappable [147,430][933,504]
android.widget.TextView Pick where Kilo runs for your first session. tappable [191,513][888,569]
android.widget.RadioButton Cloud Agent, Run Kilo in a sandboxed cloud environment with nothing to install. tappable [55,642][1025,855]
android.widget.TextView Cloud Agent tappable [223,672][911,728]
android.widget.TextView Run Kilo in a sandboxed cloud environment with nothing to install. tappable [223,732][911,824]
android.widget.RadioButton Your computer, Run Kilo on your own machine through the `kilo remote` CLI. tappable [55,883][1025,1003]
android.widget.TextView Your computer tappable [223,913][911,969]
android.widget.TextView Run Kilo on your own machine through the `kilo remote` CLI. tappable [223,973][911,1003]
android.widget.Button Skip tour tappable [55,1021][1025,1136]
android.widget.TextView Skip tour tappable [473,1055][606,1101]

Owner request

kwf-fix: proof-e65bab1-2

kwf-fix-pr: #6229

Prove the behaviour of PR #6229 with a live end-to-end run, and make no code change.
The pull request description carries no evidence: the '## E2E proof' section links a file path, which 404s on GitHub.

Run the pull request's own scenarios on a device or a simulator, for every platform its diff touches. Capture the decisive log lines always, and a screenshot as well for a user-visible change. Never a recording: they are gone (owner, 2026-09-16).
Write the evidence under a '## E2E proof' heading in your own pull request description. Never run gh: the driver publishes.
If a scenario fails, name it and say why, and still change no product code: this section proves what the branch already carries.

The pull request description as it stands now

This is the live body; you never need to fetch it, and you must not edit it. The driver merges what your final summary says into it.

## Changelog for users

- Every guided tour step now centers its icon, title, subtitle, and options between the header and the footer action.
- The block no longer sits against the header, so the empty lower half of the screen is gone.
- Content taller than the screen still scrolls, so the footer action stays reachable on short screens or with a large system font.
- The "Where would you like to run Kilo?" step keeps the icon, title, and subtitle in the same centered band while the computer list loads, is empty, or fails to load.

## Changelog for maintainers

- `ForkStep` and `TourRemoteStep` ScrollView content containers now use `grow items-center justify-center gap-* px-6 py-6`.
- `grow` (flex-grow: 1) fills the viewport so `justify-center` distributes the children; it is a minimum, so taller content scrolls instead of clipping.
- Vertical padding becomes symmetric (`py-6`); the previous top-aligned `pt-4` first-run rhythm is dropped.
- The mounted tests for both tour steps assert the new content-container classes and that `CenteredState` is not rendered.
- Review first: the centering depends on the parent giving the ScrollView height; check both tour steps at short and tall device heights and with a long connected-computer list.

## E2E proof

**[e2] On the same fork, tap "Your computer": the icon/title/subtitle block stays centred in the same band while the computer list is loading, after it resolves empty ("No computer connected yet" + Check…** — android emulator-5604: loading (ProgressBar [413,1625][467,1679] inside the busy Check-again button, e2-loading-scene.xml), empty ("No computer connected yet" + "Check again", e2-empty.digest.txt) and failed load ("Network error. Please try again." + "Retry", e2-error.digest.txt) all keep the title at [178,920][903,994] and subtitle at [56,1003][1025,1115] with no shift, and tap Retry recovers to the empty state (e2-retry-recovery.digest.txt); the loading hold came from fault.sh stall nextjs --hold 90 (e2-fault-stall3.log). Layout/centring appearance on e2-tour-fork.png, e2-loading.png…

![](https://github.com/user-attachments/assets/e0acdab0-825b-4b2d-afb9-a6f36dba47ef)

**[e2] On the same fork, tap "Your computer": the icon/title/subtitle block stays centred in the same band while the computer list is loading, after it resolves empty ("No computer connected yet" + Check…** — android emulator-5604: loading (ProgressBar [413,1625][467,1679] inside the busy Check-again button, e2-loading-scene.xml), empty ("No computer connected yet" + "Check again", e2-empty.digest.txt) and failed load ("Network error. Please try again." + "Retry", e2-error.digest.txt) all keep the title at [178,920][903,994] and subtitle at [56,1003][1025,1115] with no shift, and tap Retry recovers to the empty state (e2-retry-recovery.digest.txt); the loading hold came from fault.sh stall nextjs --hold 90 (e2-fault-stall3.log). Layout/centring appearance on e2-tour-fork.png, e2-loading.png…

![](https://github.com/user-attachments/assets/12c96b8d-0c0a-4e26-93d3-5b513c6458ed)

## E2E proof — log excerpts

[e1] Open the tour (Profile -> Tutorial replay) and land on "Where would you lik -> pass :: Tall device 1080x2400, font scale 1.0: the replay lands on "Where would you like to run Kilo?" (e1-tall-tour.log) and the hierarchy puts the block - icon box [448,767][632,951] to last card [55,1441][1025,1654] - inside the body band [0,218][1080,2203] with 549 px above and 549 px below (e1-tall-hierarchy.xml); the second tour step measured 403 px above and 494 px below its block (e1-step2.xml), and the on-screen appearance belongs to the visual reviewer.
[e3] On a short screen or with a large system font, the tour body starts at the -> pass :: At wm size 1080x1200 the body starts under the QUICK TOUR header with the second card [55,883][1025,1003] running into the Skip bar [55,1021][1025,1136] (e3-short-entry.log) and one swipe up moves the title to [147,282][933,356] with both cards [55,494][1025,707] and [55,735][1025,948] fully above the Skip bar (e3-short-scrolled.log); the tour digest is unchanged at font scale 2.0 (e3-final1.log), so the short-screen branch carries the case, and wm size and font scale were restored afterwards.
[e2] On the same fork, tap "Your computer": the icon/title/subtitle block stays -> pass :: android emulator-5604: loading (ProgressBar [413,1625][467,1679] inside the busy Check-again button, e2-loading-scene.xml), empty ("No computer connected yet" + "Check again", e2-empty.digest.txt) and failed load ("Network error. Please try again." + "Retry", e2-error.digest.txt) all keep the title at [178,920][903,994] and subtitle at [56,1003][1025,1115] with no shift, and tap Retry recovers to the empty state (e2-retry-recovery.digest.txt); the loading hold came from (e2-fault-stall3.log). Layout/centring appearance on e2-tour-fork.png, e2-loading.png, e2-error.png, e2-empty.png is left to the visual reviewer.

## Follow-ups (not changed here)
- not proved live: On a short screen or with a large system font, the tour body starts at the top padding and scrolls to the Skip bar: nothing is clipped under the header and the cards are reachable. (no capture cited it)
- not proved live: Open the tour (Profile -> Tutorial replay) and land on "Where would you like to run Kilo?": the icon, title, subtitle and the Cloud Agent / Your computer cards sit vertically centred in the band between the header and the "Skip tour" bar, with equal space above and below the block, at a tall device height. (no capture cited it)

![e2-error](https://github.com/user-attachments/assets/34ba62ab-5078-4774-8c30-f01fde9dd8c9)

![e2-tour-fork](https://github.com/user-attachments/assets/eda62895-60e2-47ff-92d3-23533a94e58c)

![e1](https://github.com/user-attachments/assets/5c6c978b-fff9-4561-b9f7-5fa087239bf6)

<details>
<summary>Owner request</summary>

> Surface: the mobile app (apps/mobile).
> 
> One small adjustment to the guided tour, on top of PR 6191: the entire section is currently top aligned, it should be centered vertically.
> 
> The owner's screenshot of the "Where would you like to run Kilo?" step shows the icon, the title, the subtitle and the two cards ("Cloud Agent", "Your computer") sitting against the header, with the whole lower half of the screen empty above the "Skip tour" button. Center that block in the space between the header and the footer action, on every step of the tour, at every device height.

</details>

## Follow-ups (not changed here)

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The latest commit changes only the explanatory comment on ForkStep's ScrollView content container; the comment now matches the content this step actually renders, and no new issues were found in the changed lines.

Files Reviewed (1 file)

• apps/mobile/src/components/tour/tour-screen.tsx

Validation: static review only in a read-only, non-interactive session; no test, lint, or typecheck command was executed. The changed lines are comment text only, so no runtime or memory-leak risk was introduced.

Previous Review Summary (commit 7442b81)

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

Previous review (commit 7442b81)

Status: 1 Issue Found | Recommendation: Address before merge

Fix these issues in Kilo Cloud

Executive Summary

This is a class-only vertical-centering tweak in the two guided-tour steps, mirrored by mounted-test assertion updates; the single finding is a copy-pasted comment clause in tour-screen.tsx that references a computer list the fork step does not render.

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
apps/mobile/src/components/tour/tour-screen.tsx	89	Comment references a growing computer list that ForkStep does not render

Files Reviewed (4 files)

• apps/mobile/src/components/tour/tour-screen.tsx - 1 issue
• apps/mobile/src/components/tour/tour-remote-step.tsx - 0 issues
• apps/mobile/src/components/tour/tour-screen.mounted.test.tsx - 0 issues
• apps/mobile/src/components/tour/tour-remote-step.mounted.test.tsx - 0 issues

Validation: static review only in a read-only, non-interactive session; no test, lint, or typecheck command was executed. The added grow / justify-center classes match the mounted-test assertions exactly, and the flex-grow + justify-center content-container pattern already exists in login-screen.tsx, so no runtime or memory-leak risk was identified in the changed lines.

---

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

_{Review guidance: REVIEW.md from base branch kwf/guided-tour-ux-7b2e}

[iscekic]

This description names a scenario the proof did not capture:

• not proved live: On a short screen or with a large system font, the tour body starts at the top padding and scrolls to the Skip bar: nothing is clipped under the header and the cards are reachable. (no capture cited 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.