feat(moshpit): batch-register the profullstack TLDs and expose alias controls

[ralyodio]

Registers the requested namespace to anthony@profullstack.com, and gives operators a UI for the alias/exemption APIs that until now existed only as endpoints.

Only TLDs get registered — that's the whole model

registerTld is the only registration there is: "the operator of that TLD then owns everything under it" (PRD 0001). Claiming .yeah is what delivers fuck.yeah. There is no second-level row to write, and no moshpit_names table — I checked the schema.

So the 11 names in the request are 6 TLD claims:

TLD	carries
.yeah	fuck.yeah
.oranges	chovy.oranges, california.oranges
.agent	profullstack.agent
.profullstack	— (reserved; see below)
.sploof	original.sploof
.agentic	— (registered so it can point at .agent)

The second-level names are kept in the script so the intent stays readable, and are asserted to parse under the TLD claimed for them — not claimed separately.

.profullstack is reserved, on purpose

It sits on RESERVED_TLDS under "ours: the network's own names are not for sale". That list exists to stop other people claiming it; assigning one of our own names to us is the single case it's meant to yield to — exactly what seed-moshpit-tld.ts already does for .moshpit. The script passes allowReserved for that one entry, and it stays unreachable from the public API.

Idempotent

An already-held TLD is left exactly as it is. A TLD held by a different owner is reported and skipped, never reassigned. --dry-run reads the live registry and writes nothing.

bun run scripts/seed-moshpit-names.ts --dry-run   # see what would happen
bun run scripts/seed-moshpit-names.ts             # do it

Needs TURSO_DATABASE_URL / TURSO_AUTH_TOKEN, which is why it ships as a script rather than being run from here — I have no production credentials, and registration through the API is session-cookie authenticated.

.agentic → .agent

Applied through the existing setAlias, which already requires the same account to hold both ends — aliasing a name you don't own would let one claim absorb a dozen unregistered ones. Resolution carries the label across, so foo.agentic → foo.agent.

The operator UI was the real gap

PUT/DELETE /api/moshpit/tlds/:tld/alias and the exemption routes worked fine and had no interface anywhere — grep -rln alias app --include=*.tsx returned nothing. That made "customizable by operators" true only for operators who write curl.

New Moshpit TLDs tab in /dashboard: lists what you hold, claims new endings, points one TLD at another, clears the redirect, and manages the names held back from it (exemptions), which is how you keep keep.agentic where it is while the rest of .agentic redirects.

Tests

tests/moshpit-seed-names.test.mjs pins the assumptions the batch rests on: every requested name is a legal TLD, each second-level name really falls under the TLD claimed for it, the alias pair are both present, and .profullstack is still reserved — if that assertion ever flips, the name became publicly claimable and allowReserved stopped protecting anything.

69 tests pass, clean tsc --noEmit.

Note

app.moshcode.sh/pit currently returns 404, while pit.moshcode.sh/dashboard returns 200. If those are meant to be the same surface, that redirect is missing — out of scope here, flagging it.

🤖 Generated with Claude Code

[github-actions]

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.