0.3.06

2026-08-23 09:40:45 +12:00
parent 9a1f44da46
commit 766cea2199
19 changed files with 828 additions and 164 deletions
@@ -3338,6 +3338,14 @@ because a show's synopsis is already in the hero and what a show is *for* is its
  cached in the repository, so warming a detail page on D-pad focus and then opening it costs
  one request rather than two. The pane itself is the second half of that — while the hero is
  whole the pane is 34dp, so a grid composes one row until the viewer actually goes there.
+- **The open page owns its full item record, keyed by item id.** `HomeViewModel.focusedItem`
+  remains launcher state: Search can legitimately put its lightweight row object back there
+  when focus returns behind an overlay. `FocusedDetailsOverlay` therefore holds the raw
+  `getItemDetails` answer separately and merges only live user state from a matching focused
+  item. The bounded metadata cache also stores that raw answer rather than a row/detail merge;
+  a record with no `Overview` field is incomplete and joins or starts the shared detail load
+  instead of suppressing it. This is why Back → Open can reuse a complete answer without a
+  Search card permanently erasing the description.
 - `SeriesDetailsOverlay` and `MediaDetailsOverlay` only load (episodes, related, trailer,
  extras) and delegate; `SeriesDetailContent`/`MediaDetailContent` are parameter-driven so
  they can be screenshotted (`DetailPageScreenshotTest`, which drives the tab strip by