nerdsystem 0.0.23 → 0.0.24

package/dist/api.d.ts

@@ -53,6 +53,8 @@ export interface Project {
     name: string;
     scriptName: string;
     url: string;
+    /** The address on the owner's own domain, once one is verified. Absent from an older platform. */
+    customUrl?: string | null;
 }
 export interface Deployment {
     id: string;

package/dist/commands/deploy.d.ts

@@ -46,6 +46,8 @@ export declare function checksMetadata(results: GateResult[]): {
 export interface ShipResult {
     deployment: Deployment;
     url: string;
+    /** The app's address on the owner's own domain, once one is verified; null otherwise. */
+    customUrl: string | null;
     migrations: {
         applied: string[];
         skipped: string[];

package/dist/commands/deploy.js

@@ -185,11 +185,14 @@ export async function shipBuild(args) {
     }
     const { deployment } = await api.post(projectPath(nerd, "/deployments"), form);
     const { project } = await api.get(projectPath(nerd));
-    log.ok(`Deployed ${deployment.id} (${deployment.status}) → ${project.url}`);
+    log.ok(`Deployed ${deployment.id} (${deployment.status}) → ${project.customUrl ?? project.url}`);
+    // The owner knows the app by their own domain; the platform address is the one that is probed, because it always resolves.
+    if (project.customUrl)
+        log.info(`Also at ${project.url}`);
     if (!opts["skip-probe"] && deployment.status === "live")
         log.step(`Probing ${project.url}`);
     const probes = await probeAfterDeploy(root, deployment, project.url, Boolean(opts["skip-probe"]));
-    return { deployment, url: project.url, migrations: mig, probes, source, sourceSkipped, lineage, warnings: pack.warnings };
+    return { deployment, url: project.url, customUrl: project.customUrl ?? null, migrations: mig, probes, source, sourceSkipped, lineage, warnings: pack.warnings };
 }
 /** The one line about the code after a live deploy, keyed on what the API recorded, not on what we sent. */
 export function sourceLine(r) {
@@ -230,7 +233,7 @@ export async function deploy(opts) {
     const wantReview = r.deployment.status === "live" && Boolean(r.source);
     if (opts.json) {
         const review = wantReview ? await platformReview(api, `${projectPath(nerd)}/sources/${r.source.id}`, reviewPage) : null;
-        return printJson({ deployment: r.deployment, url: r.url, migrations: r.migrations, probes: r.probes, source: r.source, sourceSkipped: r.sourceSkipped, lineage: r.lineage.passed, warnings: r.warnings, review });
+        return printJson({ deployment: r.deployment, url: r.url, customUrl: r.customUrl, migrations: r.migrations, probes: r.probes, source: r.source, sourceSkipped: r.sourceSkipped, lineage: r.lineage.passed, warnings: r.warnings, review });
     }
     printProbe(r.url, r.probes);
     if (r.deployment.status === "live") {
@@ -243,7 +246,7 @@ export async function deploy(opts) {
         log.step("Your app is live. Asking for a model review of how it is put together (up to a minute or two; safe to stop waiting)");
         printReview(await platformReview(api, `${projectPath(nerd)}/sources/${r.source.id}`, reviewPage));
     }
-    log.info(`First time? Sign up on your app at ${r.url}, then make yourself admin in the dashboard's Auth tab: ${dashboardUrl(api.apiUrl)}/app/${nerd.org}/projects/${nerd.project}/auth`);
+    log.info(`First time? Sign up on your app at ${r.customUrl ?? r.url}, then make yourself admin in the dashboard's Auth tab: ${dashboardUrl(api.apiUrl)}/app/${nerd.org}/projects/${nerd.project}/auth`);
 }
 export async function deployments(opts) {
     const nerd = readNerdJson(findProjectRoot());

package/dist/commands/init.js

@@ -192,4 +192,4 @@ export async function init(dir, args) {
     log.ok(`Ready. Next:\n  cd ${dir}\n  pnpm install\n  nerd dev\n\nThen open the folder in your coding agent and ask it to build the first feature; the nerdsystem skill walks it through.\nDeploys go to ${project.url}`);
 }
 // Kept in sync with packages/sdk/package.json by the release script.
-const SDK_VERSION = "0.0.23";
+const SDK_VERSION = "0.0.24";

package/dist/commands/org.js

@@ -52,6 +52,16 @@ export function setupText(s) {
         "If you are a coding agent: give the owner these steps as they are, numbered, and nothing else to decide. Do not ask which company they use (it was looked up) and do not offer other record types. When they say it is done, run `nerd domains` until the status is active, then open the address to confirm.",
     ].join("\n");
 }
+/** Whether the domain without www forwards to the app yet, in words an agent can pass on. */
+function bareText(b) {
+    if (!b)
+        return "";
+    if (b.status === "forwarding")
+        return `${b.hostname} forwards here`;
+    if (b.status === "starting")
+        return `${b.hostname} is starting (certificate, under a minute)`;
+    return `${b.hostname} does not point here yet`;
+}
 export async function domainsList(opts) {
     const nerd = readNerdJson(findProjectRoot());
     const r = await ApiClient.fromConfig().get(projectPath(nerd, "/domains"));
@@ -59,7 +69,7 @@ export async function domainsList(opts) {
         return printJson(r);
     if (!r.domains.length)
         return log.info(`No custom domains. Add one: nerd domains add example.com`);
-    table(r.domains.map((d) => ({ hostname: d.hostname, status: d.status, ssl: d.sslStatus ?? "", does: d.redirectTo ? `forwards to ${d.redirectTo}` : "the app", error: d.lastError ?? "", id: d.id })), ["hostname", "status", "ssl", "does", "error", "id"]);
+    table(r.domains.map((d) => ({ hostname: d.hostname, status: d.status, ssl: d.sslStatus ?? "", does: d.redirectTo ? `forwards to ${d.redirectTo}` : "the app", "bare name": bareText(d.bare), error: d.lastError ?? "", id: d.id })), ["hostname", "status", "ssl", "does", "bare name", "error", "id"]);
     // Only addresses still waiting for their DNS records have steps left to do.
     for (const s of r.setups ?? [])
         log.info(`\n${setupText(s)}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nerdsystem",
-  "version": "0.0.23",
+  "version": "0.0.24",
   "description": "nerd: start, check, and deploy a web app on nerdsystem from the terminal or a coding agent.",
   "type": "module",
   "bin": {

package/template/.claude/skills/nerdsystem/SKILL.md

@@ -184,7 +184,7 @@ Paid plans only; on Free the command answers with the plan that includes it, so
 
 1. Run `nerd domains add example.com` with the bare domain the owner gives you. The platform makes `www.example.com` the app's address and sets the bare name up to forward to it. It also looks up which company runs the domain's DNS and prints the exact steps for that company.
 2. Give the owner those steps as printed, numbered. Do not ask who their registrar is, do not show a table of record types, and do not offer alternatives: the platform already chose. The steps are things only they can do (signing in where the domain is managed).
-3. When they say it is done, run `nerd domains` every minute or two until the status is `active`, then open the address and confirm it loads with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
+3. When they say it is done, run `nerd domains` every minute or two until the status is `active` and the "bare name" column says it forwards here, then open both addresses and confirm they load with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
 4. Tell them two things once it is live: they sign in once more on the new address (same account, same data), and links to the old `.nerdsystem.app` address keep working.
 
 For a subdomain such as `app.example.com`, the same command gives a single record to add.

package/template/.cursor/rules/nerdsystem.mdc

@@ -2,7 +2,7 @@
 description: How to build, run, and deploy this app on nerdsystem. Applies to server, database, auth, and deploy work.
 alwaysApply: true
 ---
-<!-- generated from .claude/skills/nerdsystem/SKILL.md (1794b8a1a530); edit the skill, then run: nerd agents sync -->
+<!-- generated from .claude/skills/nerdsystem/SKILL.md (e9b33e090df6); edit the skill, then run: nerd agents sync -->
 
 # Building on nerdsystem
 
@@ -185,7 +185,7 @@ Paid plans only; on Free the command answers with the plan that includes it, so
 
 1. Run `nerd domains add example.com` with the bare domain the owner gives you. The platform makes `www.example.com` the app's address and sets the bare name up to forward to it. It also looks up which company runs the domain's DNS and prints the exact steps for that company.
 2. Give the owner those steps as printed, numbered. Do not ask who their registrar is, do not show a table of record types, and do not offer alternatives: the platform already chose. The steps are things only they can do (signing in where the domain is managed).
-3. When they say it is done, run `nerd domains` every minute or two until the status is `active`, then open the address and confirm it loads with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
+3. When they say it is done, run `nerd domains` every minute or two until the status is `active` and the "bare name" column says it forwards here, then open both addresses and confirm they load with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
 4. Tell them two things once it is live: they sign in once more on the new address (same account, same data), and links to the old `.nerdsystem.app` address keep working.
 
 For a subdomain such as `app.example.com`, the same command gives a single record to add.

package/template/.github/copilot-instructions.md

@@ -1,4 +1,4 @@
-<!-- generated from .claude/skills/nerdsystem/SKILL.md (1794b8a1a530); edit the skill, then run: nerd agents sync -->
+<!-- generated from .claude/skills/nerdsystem/SKILL.md (e9b33e090df6); edit the skill, then run: nerd agents sync -->
 
 # Building on nerdsystem
 
@@ -181,7 +181,7 @@ Paid plans only; on Free the command answers with the plan that includes it, so
 
 1. Run `nerd domains add example.com` with the bare domain the owner gives you. The platform makes `www.example.com` the app's address and sets the bare name up to forward to it. It also looks up which company runs the domain's DNS and prints the exact steps for that company.
 2. Give the owner those steps as printed, numbered. Do not ask who their registrar is, do not show a table of record types, and do not offer alternatives: the platform already chose. The steps are things only they can do (signing in where the domain is managed).
-3. When they say it is done, run `nerd domains` every minute or two until the status is `active`, then open the address and confirm it loads with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
+3. When they say it is done, run `nerd domains` every minute or two until the status is `active` and the "bare name" column says it forwards here, then open both addresses and confirm they load with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
 4. Tell them two things once it is live: they sign in once more on the new address (same account, same data), and links to the old `.nerdsystem.app` address keep working.
 
 For a subdomain such as `app.example.com`, the same command gives a single record to add.

package/template/AGENTS.md

@@ -1,4 +1,4 @@
-<!-- generated from .claude/skills/nerdsystem/SKILL.md (1794b8a1a530); edit the skill, then run: nerd agents sync -->
+<!-- generated from .claude/skills/nerdsystem/SKILL.md (e9b33e090df6); edit the skill, then run: nerd agents sync -->
 
 # Building on nerdsystem
 
@@ -181,7 +181,7 @@ Paid plans only; on Free the command answers with the plan that includes it, so
 
 1. Run `nerd domains add example.com` with the bare domain the owner gives you. The platform makes `www.example.com` the app's address and sets the bare name up to forward to it. It also looks up which company runs the domain's DNS and prints the exact steps for that company.
 2. Give the owner those steps as printed, numbered. Do not ask who their registrar is, do not show a table of record types, and do not offer alternatives: the platform already chose. The steps are things only they can do (signing in where the domain is managed).
-3. When they say it is done, run `nerd domains` every minute or two until the status is `active`, then open the address and confirm it loads with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
+3. When they say it is done, run `nerd domains` every minute or two until the status is `active` and the "bare name" column says it forwards here, then open both addresses and confirm they load with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
 4. Tell them two things once it is live: they sign in once more on the new address (same account, same data), and links to the old `.nerdsystem.app` address keep working.
 
 For a subdomain such as `app.example.com`, the same command gives a single record to add.

package/template/GEMINI.md

@@ -1,4 +1,4 @@
-<!-- generated from .claude/skills/nerdsystem/SKILL.md (1794b8a1a530); edit the skill, then run: nerd agents sync -->
+<!-- generated from .claude/skills/nerdsystem/SKILL.md (e9b33e090df6); edit the skill, then run: nerd agents sync -->
 
 # Building on nerdsystem
 
@@ -181,7 +181,7 @@ Paid plans only; on Free the command answers with the plan that includes it, so
 
 1. Run `nerd domains add example.com` with the bare domain the owner gives you. The platform makes `www.example.com` the app's address and sets the bare name up to forward to it. It also looks up which company runs the domain's DNS and prints the exact steps for that company.
 2. Give the owner those steps as printed, numbered. Do not ask who their registrar is, do not show a table of record types, and do not offer alternatives: the platform already chose. The steps are things only they can do (signing in where the domain is managed).
-3. When they say it is done, run `nerd domains` every minute or two until the status is `active`, then open the address and confirm it loads with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
+3. When they say it is done, run `nerd domains` every minute or two until the status is `active` and the "bare name" column says it forwards here, then open both addresses and confirm they load with https. If it is still pending after an hour, run `nerd domains` and read the steps again with them; the usual cause is a leftover parking record.
 4. Tell them two things once it is live: they sign in once more on the new address (same account, same data), and links to the old `.nerdsystem.app` address keep working.
 
 For a subdomain such as `app.example.com`, the same command gives a single record to add.