[Feat]: Add a read-only account-profile lens

[sphamjoli]

Component

Other

Priority

P2

Summary

Reading everything about an account, its lite name, full name, chat key, lite-to-full link and personhood tier, takes several calls to different contracts today. Add a read-only lens that returns the lot in one call, without moving ownership of any of that data away from the contract that owns it. Part of #214. Depends on the address reads added in the permanent-names issue.

Proposal

• Add a separate read-only contract with one entry point, profileOf(address), returning the account's lite name, full names, chat key, linked full node, personhood tier, and whether the name is settled.
• Compose each field from the contract that owns it: the names from the controller's liteNameOf and fullNameOf, the chat key and link from the resolver, the tier from the pricing rules.
• Read the tier defensively. The classifier reverts on an empty or non-canonical label, which is exactly a cold or unminted name, so wrap the call and return a no-tier value instead of reverting. Otherwise the aggregate fails on the names a caller most needs to look up.
• State the read's bound and paginate if an account can hold many names.
• Do not put this on the controller. The controller issues names, and hosting an all-about-an-account read there would make it a second resolver.

Acceptance criteria

• profileOf returns the full record in one call for any address.
• It never reverts on a cold, unminted, or non-canonical name; the tier reads as a no-tier value in that case.
• The contract holds no state and owns none of the data it returns.
• Tests cover an account with a cold name, one with a settled name, a lite name promoted to full, and an address that holds nothing.

[re-gius]

Confirmed as P2 from my side - postponed

[filip-parity]

Same note as on #216: #243 makes profileOf(address) the app's single query under the contract-path branch, so the P2/postponed status may want revisiting once #216 moves. Two consumer requirements from #243 and paritytech/host-rust-core#426 worth fixing in the design: whether a lite name returns flat (alice01) or dotted (alice.01), with the lite/full split authoritative (both app and host currently guess by trailing digits), and whether publicly registered / transferred-in names are included or the lens is gateway-provenance only.

[sphamjoli]

@filip-parity this done #249

[re-gius]

Closing note: profileOf shipped as a 3-field summary (hasLabelStore, pendingClaimCount, reservationLabelhash) rather than the full record this issue described. Names, chat key, link and tier are deliberately excluded since names need an unbounded scan of the account's holdings, and the tier needs the personhood precompile, neither of which belongs in a constant-time read.

So the "everything in one call" goal is not met. Acceptable for now, but worth knowing for anyone planning against a single call.