chore: use terser for bundle minification

chore: upgrade dependencies

fix: close floating popups during navigation

fix: send valid video metadata hints when starting an upload

refactor: prioritize handles across the interface

feat: preview Tangled strings in composer

fix: keep Tangled string previews at a fixed height

fix: align post placeholder content

fix: correct regressions from the list state component migration

refactor!: retire ListFooter and ListMaybePlaceholder

refactor: move the remaining tail-only lists onto ListTail

refactor: let dialog lists compose their own pagination tail

refactor: migrate the profile collection lists to the new list state components

refactor: migrate messages and notifications lists to the new list state components

refactor: migrate list-replacing screens to the new list state components

refactor: migrate profile feedgens to the new list state components

drops the sentinel-row machinery in favour of the whole-surface components, and fixes two defects it was hiding: `isEmpty` is true whenever there is no data, failure included, so an initial error pushed `ERROR_ITEM` and then `EMPTY` — the screen told the user the request had failed and that they had no feeds, stacked. it now renders a single `ListError`. `LOAD_MORE_ERROR_ITEM` was unreachable: its branch required `!isEmpty`, which implies `data?.pages` is truthy, so the preceding branch always won. `LoadMoreRetryBtn` never rendered here. also drops two inert props on the way past. `hasNextPage` is only read as `!hasNextPage && showEndMessage`, and `showEndMessage` was never passed; `height={180}` restated the css default. the footer additionally rendered during the initial load, since `isEmpty` is gated on `!isPending`, putting a bordered 180px box under the skeleton. Claude-Session: https://claude.ai/code/session_01DZRW2fBuJdbQENW4Rq9fy8

fix: stop skeleton card rows stretching to fill leftover space

refactor: split list loading and error states into distinct components

fix: handle query network failures

fix: expire persisted query cache entries

refactor: persist queries individually

fix: keep history header visible while scrolling

fix: prevent tangled embed footer overflow

refactor: configure scroll-away lead-in

refactor: parse dates once in isStatusStillActive

fix: keep tangled string embed height on load failure

Claude-Session: https://claude.ai/code/session_0138rjvapq5AKYNuvdnZYrMG

chore: make Vite bundled dev mode work again

chore: upgrade dependencies

chore: use bundled dev mode by default

chore: upgrade to pnpm 12

feat: embed Tangled code files

feat: give the starter pack page a scroll-away header

fix: let header content shrink instead of overflowing

feat: move the profile overflow menu into the sticky header

docs: advance the reviewed upstream tip to 5eb5ac4800

refactor: read the message draft through an effect event

the render-synced ref was doing what useEffectEvent is for. same behaviour — the cleanup still sees the last committed message — with one fewer effect, and it matches how the rest of the codebase reaches non-reactive values from an effect.

refactor: hoist finally blocks out of the way of React Compiler

React Compiler cannot lower a `try` with a `finalizer` clause, so it silently skipped optimizing every component and hook containing one — 13 sites, confirmed by running the compiler over `src/`. none of the guarded bodies return or rethrow, so running the cleanup after the `try`/`catch` is equivalent. three of the sites were empty `finally {}` leftovers and are just gone.

fix: check every loaded page before calling a list empty

these lists only looked at the first page, so a profile whose first page of feeds, lists, or starter packs came back empty rendered the empty state even after later pages loaded.

fix: stop feeds from stalling on filtered-out pages

a feed gave up whenever a page's items were all filtered out client-side, and `CustomFeedAPI` suppressed the cursor on an empty page, so a feed could report itself exhausted while more pages existed upstream. one empty page is the wrong predicate for exhaustion — the appview legitimately returns an empty page with a cursor when hydration drops everything. extract the paginator both feeds had copied into `useAutoPagination`, and make exhaustion the concern of `getNextPageParam`, which is where the next page param is minted and where a cursor the server has already served can be recognised. `hasNextPage` then tells the truth for manual scrolling too, not just for the auto-paginator.

chore: use own vanilla extract plugin

refactor: tend to the profile search page

chore: allow bundled dev to work

refactor: move layered helper out of layers.css.ts

fix: hide empty profile collection placeholders

fix: align scroll-away border with header edge

fix: state header edge slots explicitly

feat: add scroll-away headers

chore: avoid running build

fix: show bottom border on the list header when no tab bar follows

chore: advance upstream marker