@theholocron/holocron-plugin-vercel 5.0.0-alpha.28 → 5.0.0-alpha.29

package/README.md

@@ -64,11 +64,16 @@ Capability covers:
   an app) — `defaultFramework` only applies to `ensureProject()`'s
   Git-linked path.
 - `getDeployment()` — fetch a deployment by id
-- `ensureCustomDomain()` — idempotent add (list → check → add). Adding
-  a domain new to the Vercel account returns `verified: false` with a
-  DNS verification challenge (usually a CNAME to a per-project target
-  Vercel generates — never a fixed well-known host). The returned DNS
-  record is handed to the configured `dns` provider by `holocron setup`.
+- `ensureCustomDomain()` — idempotent add (list → add-if-missing →
+  check DNS routing). Ownership (`verified`) and DNS routing are
+  separate: once a team already owns a domain's apex, every new
+  subdomain auto-verifies immediately with no fresh challenge, so
+  attachment alone can't tell you whether traffic is actually routed
+  to Vercel yet. `domains.config()` answers that regardless of
+  ownership state, returning a per-project CNAME target — never a
+  fixed well-known host — only when DNS isn't already configured. The
+  returned DNS record is handed to the configured `dns` provider by
+  `holocron setup`.
 
 Declare the production domain in the Vercel provider options. On `holocron setup`,
 the domain is attached to the project and any Vercel verification CNAME is

package/dist/index.d.mts

@@ -35,16 +35,23 @@ declare class VercelDeployment implements Deployment {
   getDeployment(deploymentId: string): Promise<DeploymentRecord>;
   deployFunction(projectId: string, config: DeployFunctionConfig): Promise<DeployFunctionResult>;
   /**
-   * Idempotent — no-op when `hostname` is already on the project,
-   * matching `Deployment.ensureCustomDomain`'s contract (never break
-   * on re-runs, per CLAUDE.md's probe-then-act standard). Adding it
-   * the first time returns `verified: false` for a domain new to this
-   * Vercel account, plus a `verification` challenge — usually CNAME, a
-   * unique per-project target Vercel generates (never a fixed
-   * well-known host, confirmed via Vercel's own docs). Returned as a
-   * `DnsRecordRequest` — the caller (e.g. `holocron setup`'s
-   * custom-domain step) hands it straight to `dns.upsertRecord()`,
-   * same as `Wiki.dnsRecord()` already does for the wiki's own domain.
+   * Idempotent — matches `Deployment.ensureCustomDomain`'s contract
+   * (never break on re-runs, per CLAUDE.md's probe-then-act standard).
+   *
+   * Ownership (`domains.add`'s `verified`) and DNS routing are separate
+   * concerns: once a team already owns the domain's apex (true for any
+   * org with more than one project on the same domain), every new
+   * subdomain auto-verifies immediately with no `verification`
+   * challenge — re-adding an already-attached domain returns 409, not
+   * a fresh one. So attachment alone can't tell us whether traffic is
+   * actually routed to Vercel yet. `domains.config()` (Vercel's DNS
+   * *configuration* check) answers that regardless of ownership state:
+   * `misconfigured` + a `recommendedCNAME`, per-project, never a fixed
+   * well-known host — always read it from this response, never
+   * hardcode it. Returned as a `DnsRecordRequest` — the caller (e.g.
+   * `holocron setup`'s custom-domain step) hands it straight to
+   * `dns.upsertRecord()`, same as `Wiki.dnsRecord()` already does for
+   * the wiki's own domain.
    */
   ensureCustomDomain(projectId: string, hostname: string): Promise<DnsRecordRequest | null>;
   private getProjectByName;

package/dist/index.mjs

@@ -78,30 +78,45 @@ var VercelDeployment = class {
 		};
 	}
 	/**
-	* Idempotent — no-op when `hostname` is already on the project,
-	* matching `Deployment.ensureCustomDomain`'s contract (never break
-	* on re-runs, per CLAUDE.md's probe-then-act standard). Adding it
-	* the first time returns `verified: false` for a domain new to this
-	* Vercel account, plus a `verification` challenge — usually CNAME, a
-	* unique per-project target Vercel generates (never a fixed
-	* well-known host, confirmed via Vercel's own docs). Returned as a
-	* `DnsRecordRequest` — the caller (e.g. `holocron setup`'s
-	* custom-domain step) hands it straight to `dns.upsertRecord()`,
-	* same as `Wiki.dnsRecord()` already does for the wiki's own domain.
+	* Idempotent — matches `Deployment.ensureCustomDomain`'s contract
+	* (never break on re-runs, per CLAUDE.md's probe-then-act standard).
+	*
+	* Ownership (`domains.add`'s `verified`) and DNS routing are separate
+	* concerns: once a team already owns the domain's apex (true for any
+	* org with more than one project on the same domain), every new
+	* subdomain auto-verifies immediately with no `verification`
+	* challenge — re-adding an already-attached domain returns 409, not
+	* a fresh one. So attachment alone can't tell us whether traffic is
+	* actually routed to Vercel yet. `domains.config()` (Vercel's DNS
+	* *configuration* check) answers that regardless of ownership state:
+	* `misconfigured` + a `recommendedCNAME`, per-project, never a fixed
+	* well-known host — always read it from this response, never
+	* hardcode it. Returned as a `DnsRecordRequest` — the caller (e.g.
+	* `holocron setup`'s custom-domain step) hands it straight to
+	* `dns.upsertRecord()`, same as `Wiki.dnsRecord()` already does for
+	* the wiki's own domain.
 	*/
 	async ensureCustomDomain(projectId, hostname) {
 		const { domains: existing } = await this.client().domains.list(projectId);
-		if (existing.some((d) => d.name === hostname)) return null;
-		const result = await this.client().domains.add(projectId, hostname);
-		if (result.verified) return null;
-		const challenge = result.verification?.find((v) => v.type === "CNAME");
-		if (!challenge) return null;
+		let apexName = existing.find((d) => d.name === hostname)?.apexName;
+		if (!apexName) try {
+			apexName = (await this.client().domains.add(projectId, hostname)).apexName;
+		} catch (err) {
+			if (!(err instanceof ProviderApiError && err.status === 409)) throw err;
+			const { domains: refreshed } = await this.client().domains.list(projectId);
+			apexName = refreshed.find((d) => d.name === hostname)?.apexName;
+		}
+		if (!apexName) return null;
+		const config = await this.client().domains.config(hostname, projectId);
+		if (!config.misconfigured) return null;
+		const cname = config.recommendedCNAME[0]?.value;
+		if (!cname) return null;
 		return {
-			zone: result.apexName,
+			zone: apexName,
 			record: {
 				type: "CNAME",
 				name: hostname,
-				content: challenge.value
+				content: cname
 			}
 		};
 	}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/holocron-plugin-vercel",
-  "version": "5.0.0-alpha.28",
+  "version": "5.0.0-alpha.29",
   "description": "Holocron plugin for Vercel. Implements the deployment capability against the Vercel REST API.",
   "keywords": [
     "deployment",
@@ -31,10 +31,10 @@
   ],
   "devDependencies": {
     "@theholocron/eslint-config": "^8.0.0",
-    "@theholocron/http-client": "^1.23.0",
+    "@theholocron/http-client": "^1.24.0",
     "@theholocron/tsconfig": "^8.0.0",
     "@theholocron/tsdown-config": "^8.0.0",
-    "@theholocron/vercel-client": "^1.23.0",
+    "@theholocron/vercel-client": "^1.24.0",
     "@theholocron/vitest-config": "^8.0.0",
     "@types/node": "^26",
     "@vitest/coverage-v8": "^4.1.11",
@@ -46,11 +46,11 @@
     "tsx": "4.23.12",
     "typescript": "^5.9.3",
     "vitest": "^4.1.11",
-    "@theholocron/cli": "5.0.0-alpha.28"
+    "@theholocron/cli": "5.0.0-alpha.29"
   },
   "peerDependencies": {
-    "@theholocron/vercel-client": "^1.23.0",
-    "@theholocron/cli": "5.0.0-alpha.28"
+    "@theholocron/vercel-client": "^1.24.0",
+    "@theholocron/cli": "5.0.0-alpha.29"
   },
   "peerDependenciesMeta": {
     "@theholocron/vercel-client": {}