Fix Mobile page layout and the profile editor grid

[enaboapps]

Closes #888. Stacked on #897, tracked in #891.

What changed

• The "Optional" note under the connection band no longer overlaps the QR figure.
• Install Switchify for mobile and Connect your mobile are two equal cards. They sit side by side when there is room and stack otherwise.
• The install card shows its heading, then the QR code, then the Google Play link, in both the markup and the visual order.
• The pairing steps have more space between items, and the Pair a mobile device demonstration sits inside its card.
• The profile editor's binding rows give the action select and its value control equal shares, instead of a fixed 140px action column. Rows drop to two columns when the dialog is narrower than 560px, using a container query. Errors span both control columns.
• Profile rows at narrow widths keep their icon tile. An older rule hid every span except the last, which caught the tile once it became a span in Unify list rows, page headers and the sidebar #893.

Validation

On this head:

• npm run lint passed
• npm test passed: 238 Vitest tests and 5 Node tests
• npm run build passed
• cargo fmt --check, cargo clippy --all-targets -D warnings and cargo test passed (566 tests, 1 ignored). No Rust changes in this stack.
• Rendered Mobile connection, paired devices, forwarding profiles, and new and built-in profile editors in headless Chrome at 920px and 620px, light and dark.

Review follow-up

An independent review of this layer's head raised these points, now addressed:

• The install card's markup now reads heading, intro, QR code, then store link, so display: contents and flex order are gone.

🤖 Generated with Claude Code

Rebase validation (2026-09-25)

Rebased onto current main (7fb8fce, including #881) in stack order. git range-diff shows every commit in this PR is patch-equivalent to its previous head, and the intended parent remains its PR base. On the final stack tip (40c75cc), Node 24.19.0 lint, tests and build passed; Rust 1.97.1 format check, Clippy and tests passed. An independent review of the updated PR heads found no actionable findings. CI is rerunning on each new head.