Building UserTold

• A Study chooses how its launcher is dressed: calm, which holds completely still, or one of three treatments carrying a single moving element. Corner radius and glyph are separate choices.
• The Invitation editor keeps a live preview beside its settings: the launcher in the Study's own colour and label on a light and a dark page at once, and the expanded Invitation on a page when the Study shows one.

Why it matters. Products that turn completed customer interviews into source-linked Evidence can make that practice visible and help people discover teams that keep listening.

• A public leaderboard ranks participating customer domains by collected Evidence, with completed Interviews as the tie-breaker.
• Owners decide whether to publish, can refine the automatically fetched title and description, and can unpublish later.
• Listings use live research counts and direct website links; payment is only a private anti-abuse eligibility check and never changes rank or promotion.
• Listings display the product's own site icon, fetched from the listed website at publish time and served from UserTold rather than hotlinked.
• The Terms of Service gained a Public Listings section covering listing content rules and UserTold's right to suspend or remove a listing.

• Existing browser sessions and user-issued CLI, MCP, and REST credentials remain usable when the active legal-document version changes.
• A persistent account notice links the current documents and records acknowledgement without blocking product access.
• New signups record the active legal version, while capability-specific consent uses a separate version from general document updates.

• The public UserTold CLI source, command documentation, release notes, and Apache-2.0 license are available in the dedicated usertold/cli repository.
• This application repository retains the private operator CLI only.
• v2.0.0 is available as a GitHub Release and from the usertold npm package.