fix: keep name-less accounts usable and count held balance as the add-money milestone

[bmc08gt]

Three fixes that shipped in the 2026.8.3 rebuild, brought back to main so they aren't stranded on the release branch.

fix(you) — keep the You tab usable without a display name

TipCardTab swapped YouScreen out entirely for a bare setup prompt, so an account with no display name could not reach Settings — and therefore could not log out. YouScreen now always renders; only the card slot changes. Where the card would be, a blurred stand-in card carries the invitation, and the share affordances drop out until there is a name.

The card's own fill is black over a frosted backdrop, so on the black page it can only subtract brightness — the stand-in gets a pale base underneath instead, clipped back to the card's outline so the blur reads as a card rather than a smudge.

The CTA routes to .changeDisplayName, not .profileName: the latter's submit path guards on the sheet being on the .tips stack, so pushing it from .you saves the name and strands the user.

fix(chats) — stop gating the Chats tab on a tip card

TipsScreen swapped the whole Chats tab for the tip-card intro when the profile wasn't tippable. That hid existing conversations, and put a second copy of the invitation behind a tab that already has one next door. A name-less account can still send tips, so it can still hold conversations — the embedded tab now always renders TipConversationsScreen with its own "No Chats Yet" empty state.

The v1 sheet keeps the intro: it is that flow's only door into profile creation.

The You tab's copy is now word-for-word the Chats tab's, since the same account hits both and two different asks for one thing read as two different jobs.

fix(wallet) — count money in hand as the add-money milestone

hasEverAddedMoney() read only the activity table. On the affected account that table had 0 rows against a balance of 17452 quarks, so an account visibly holding $0.02 was being told to go add money. A balance cannot exist without having arrived, and the history feed does not always carry the arrival that put it there — so money in hand now settles the milestone before history is consulted. History still answers the spent case, where the balance is gone but the milestone must stay met.

Dust counts: the check is quarks > 0, not the giveable-balance check — too-small-to-spend still proves money arrived.

The second half is re-evaluation. The check was one-shot, so WalletScreen now recomputes the milestone and pulls history when the balance moves; onAppear alone fires once per launch and never again after a deposit lands.