Migration 010 gave endings a one-year term with renewals, per PRD 0005 §5. That is withdrawn. The prices are unchanged — what changed is that they are not charged again.

The reason is what the namespace is for. A name that lapses is a name somebody else can catch, and the whole pitch is that you can finally hold the clean name instead of the hyphenated one you settled for. An annual invoice with a drop date attached is the thing people are trying to get away from; selling it back to them undoes the pitch.

Two things worth knowing before reviewing

Names were already sold this way. moshpit_names has never had an expiry column and nothing has ever renewed a name. The PRD called it a yearly fee, the schema sold it outright, and the doc comment described the PRD. It now describes the code.

The ending term never shipped. Nothing in the app could open an ending checkout, so quoteTld and quoteRenewal were unreachable and only the webhook settler was wired up. No ending was ever charged a renewal, and no row in the wild has an expiry this drop takes away. That is why migration 016 is a plain drop rather than a grandfathering policy — §21.8 asks for one before putting endings into a lifecycle, and taking them back out of one nobody was in needs no such thing.

What changed

• expires_at and term_started_at dropped from moshpit_tlds, columns and index. Gone rather than left NULL: a nullable expiry is an annual term waiting to be switched back on.
• moshpit_tld_purchases keeps kind and years. That is a financial record of what was sold at the time, and a ledger is not something to rewrite once the product changes.
• A renew row can no longer be created, but one may still settle late. It is honoured rather than refused — the buyer keeps the ending, which now keeps itself. Refusing it would take money for nothing. (A renewal for an ending that has since changed hands is still a refund.)
• isExpired() stays and always answers no, so callers asking a fair question get a permanent answer instead of an import that fails.
• quoteRenewal, TERM_MS and MAX_TERM_YEARS are gone rather than left as no-ops somebody could wire a checkout to. There is a test asserting they are undefined.

The pit page

Leads with it, since it is the one claim here worth making above the fold and the whole reason to prefer this over a registrar:

Bought once. Yours for good.
$5 an ending, $2 a name — paid one time, not every year. Nothing here renews, nothing lapses, and no name you hold can drop because an invoice went to an address you stopped reading.

For whoever writes the next migration

Nothing may follow the last statement in a .sql file but whitespace. migrate.mjs splits on semicolons and hands each piece to libSQL, and a trailing comment-only piece comes back as SQLITE_OK: not an error, which is as unhelpful as it sounds. Cost me a debug cycle; noted in the migration header.

Tests

591 pass in apps/pwa. moshpit-terms.test.mjs rewritten for lifetime semantics; migration verified from scratch.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GWhPX5Uzd29whRg5WPAYM7