Collapse mode and layer onto one picker row; fix renderer diagnosis

Only one layer is ever active, so neither mode nor layer needs a scrolling
row. Two pickers side by side cost one 44px row instead of two.

The panel needed that space: .pads uses minmax(34px,1fr) rows and sat
exactly at the 34px floor, so the SP-404 illustration clipped at the
bottom. Measured on device:

  strip   96px -> 44px
  panel  433px -> 485px
  pads   142px -> 194px, rows 34px -> 44.75px
  unit overflow 1px -> 0

The layer list is read out of the reference's own chips at render time,
so its set, ordering and counts cannot drift from renderExplore().

Also corrects the renderer-denial root cause. It is not screen state: a
denial was observed with Reason[screen_on & caller care]. Every failure
followed 'adb install -r' and an immediate relaunch has always succeeded,
so device.sh now retries the force-stop/start cycle instead of blaming
the lockscreen.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

native/native.css

@@ -42,6 +42,13 @@
      single .ctxbtn below, leaving one chip row with real touch targets.
      Phase 2 must carry this - see CLAUDE.md. */
 
+  /* Mode and layer pickers share one row: only one layer is ever active, so
+     neither needs a scrolling row of its own. One 44px row instead of two gives
+     the panel back 52px, which it needs - its pad rows sit at their
+     minmax(34px,1fr) floor, so anything less clips the illustration. */
+  .stripbar{ display: flex; gap: 8px; }
+  .stripbar .ctxbtn{ flex: 1 1 0; min-width: 0; font-size: 1rem; padding: 8px 12px; }
+
   .ctxbtn{
     display: flex; align-items: center; justify-content: space-between; gap: 10px;
     width: 100%; min-height: 44px; padding: 8px 14px;