v0.8.1

fix(codex-ouronet): show virgin (never-funded) payment keys, don't hide them (v0.8.1)

The Ouronet account card hid an account's entire Payment Key section when the
chain's payment-key-existance flag was false. But every registered Ouronet
account is ASSIGNED a payment key at activation; payment-key-existance reports
only whether that payment-key ADDRESS has ever held STOA (has a coin-table row)
— i.e. virgin (never funded) vs funded — NOT whether a payment key exists. So a
virgin payment key vanished from the card entirely, even though it exists.

Fix: surface the payment-key address whenever URC_0027 returns one, regardless
of funding (hydrate no longer gates stoaChainLedger on payment-key-existance).
The funding flag now drives only the balance and a new subtle "virgin · never
funded" marker — never whether the section shows. This also makes Payment Key
consistent with every sibling chain section (Guard/StoicTag/Sovereign/Governor),
which already render an empty/placeholder state rather than disappearing.

Reproduces identically in OuronetUI, Mnemosyne, and the Codex playground because
all three read the same URC_0027 chain data through this shared card — hence the
fix lands here in the Codex package, and consumers pick it up on their next bump.

TDD: new ui-ouronet-accounts-payment-key.test.tsx mocks URC_0027 to return a
virgin payment key (existance:false, real payment-key address) and asserts the
address renders with the virgin marker; a funded row asserts the balance shows
with no marker. codex-ouronet 68 files / 724 tests green; full workspace
typecheck + build green.

codex-ouronet and codex both bump 0.8.0 -> 0.8.1 (PATCH, bug fix).

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com