back out the two-pane list-detail deck — June's call, it looked awful. Kept the harmless modifier params on VaultListScreen/EntryDetailScreen (idiomatic Compose, no behaviour change) and deleted VaultDeck.kt; the EntryDetail route renders EntryDetailScreen directly again, exactly as before. Foldable width remains an open question: the blanket 480dp cap wasted the margins and the two-pane was wrong, so the right answer is neither and needs June's steer before a third attempt.

@@ -106,6 +106,7 @@106106     // is primary, not a child of the vault list) — there's genuinely nothing107107     // to go "back" to, so the top chrome shows a lock affordance instead.108108     onBack: (() -> Unit)?,109+    modifier: Modifier = Modifier,109110     vm: EntryDetailViewModel = hiltViewModel(),110111 ) {111112     val entry by vm.entry.collectAsState()@@ -127,7 +128,7 @@127128     SecureFlagEffect()128129 129130     val e = entry130-    ShellBackground {131+    ShellBackground(modifier) {131132         Box(132133             Modifier.fillMaxSize().statusBarsPadding()133134                 // C1: swipe left/right between deck entries, mirroring the

@@ -118,6 +118,7 @@118118     // the notes filter pill so the list opens already scoped to notes, the119119     // closest equivalent to the browser's dedicated secure-notes overlay.120120     startNoteOnly: Boolean = false,121+    modifier: Modifier = Modifier,121122     vm: VaultListViewModel = hiltViewModel(),122123 ) {123124     LaunchedEffect(Unit) {@@ -154,7 +155,7 @@154155         if (result == SnackbarResult.ActionPerformed) vm.restoreEntries(ev.ids)155156     }156157 157-    ShellBackground {158+    ShellBackground(modifier) {158159         Box(Modifier.fillMaxSize()) {159160         Column(Modifier.fillMaxSize()) {160161             if (isMultiSelect) {