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

package/README.md

@@ -67,10 +67,19 @@ Capability covers:
 - `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); this method only
-  adds the domain, reading the challenge to finish DNS setup is the
-  caller's own job today (no `Wiki.dnsRecord()`-style shared surface
-  for it yet)
+  Vercel generates — never a fixed well-known host). 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
+upserted through the configured DNS provider:
+
+```ts
+providers: {
+	deployment: ["vercel", { teamId: "team_…", domain: "sentinel.example.com" }],
+	dns: "cloudflare",
+}
+```
 
 Out of scope for alpha.0 (file a follow-up if needed):
 

package/dist/index.d.mts

@@ -1,4 +1,4 @@
-import { AuthError, DeployFunctionConfig, DeployFunctionResult, Deployment, DeploymentProject, DeploymentProjectSettings, DeploymentRecord, DeploymentTarget, DeploymentTrigger, ResolveTokenInput } from "@theholocron/cli";
+import { AuthError, DeployFunctionConfig, DeployFunctionResult, Deployment, DeploymentProject, DeploymentProjectSettings, DeploymentRecord, DeploymentTarget, DeploymentTrigger, DnsRecordRequest, ResolveTokenInput } from "@theholocron/cli";
 import { VercelClient, VercelClient as VercelClient$1, VercelClientOptions, createVercelClient } from "@theholocron/vercel-client";
 //#region src/auth.d.ts
 declare const resolveToken: (input?: ResolveTokenInput) => string;
@@ -7,11 +7,14 @@ declare const resolveToken: (input?: ResolveTokenInput) => string;
 interface DeploymentOptions {
   /** Optional framework hint passed to project creates. Defaults to "nextjs". */
   defaultFramework?: string;
+  /** Custom domain that `holocron setup` should attach to this project. */
+  domain?: string;
 }
 declare class VercelDeployment implements Deployment {
   private readonly client;
   readonly key: "deployment";
   readonly providerName = "vercel";
+  readonly domain?: string;
   private readonly defaultFramework;
   constructor(client: () => VercelClient$1, opts?: DeploymentOptions);
   listProjects(): Promise<DeploymentProject[]>;
@@ -36,16 +39,14 @@ declare class VercelDeployment implements Deployment {
    * 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 — Vercel needs a DNS record (usually CNAME, a
-   * unique per-project target) created before it routes traffic. This
-   * method only adds the domain; reading the verification challenge
-   * needed to finish is the caller's job (`client().domains.add()`'s
-   * own return value carries it) — Sentinel has no `holocron setup`
-   * orchestration to hand it to, so there's no shared "here's the DNS
-   * record" surface to route it through the way `Wiki.dnsRecord()`
-   * does today.
+   * 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.
    */
-  ensureCustomDomain(projectId: string, hostname: string): Promise<void>;
+  ensureCustomDomain(projectId: string, hostname: string): Promise<DnsRecordRequest | null>;
   private getProjectByName;
 }
 //#endregion
@@ -76,6 +77,8 @@ interface VercelPluginOptions extends ResolveTokenInput {
   teamId?: string;
   /** Default framework slug for new project creates. Defaults to "nextjs". */
   defaultFramework?: string;
+  /** Custom domain that `holocron setup` should attach to the Vercel project. */
+  domain?: string;
   /** Override base URL for tests. */
   baseUrl?: string;
   /** Override `fetch` for tests. */

package/dist/index.mjs

@@ -13,10 +13,12 @@ var VercelDeployment = class {
 	client;
 	key = "deployment";
 	providerName = "vercel";
+	domain;
 	defaultFramework;
 	constructor(client, opts = {}) {
 		this.client = client;
 		this.defaultFramework = opts.defaultFramework ?? "nextjs";
+		this.domain = opts.domain;
 	}
 	async listProjects() {
 		const { projects } = await this.client().projects.list();
@@ -80,19 +82,28 @@ var VercelDeployment = class {
 	* 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 — Vercel needs a DNS record (usually CNAME, a
-	* unique per-project target) created before it routes traffic. This
-	* method only adds the domain; reading the verification challenge
-	* needed to finish is the caller's job (`client().domains.add()`'s
-	* own return value carries it) — Sentinel has no `holocron setup`
-	* orchestration to hand it to, so there's no shared "here's the DNS
-	* record" surface to route it through the way `Wiki.dnsRecord()`
-	* does today.
+	* 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.
 	*/
 	async ensureCustomDomain(projectId, hostname) {
 		const { domains: existing } = await this.client().domains.list(projectId);
-		if (existing.some((d) => d.name === hostname)) return;
-		await this.client().domains.add(projectId, hostname);
+		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;
+		return {
+			zone: result.apexName,
+			record: {
+				type: "CNAME",
+				name: hostname,
+				content: challenge.value
+			}
+		};
 	}
 	async getProjectByName(name) {
 		try {
@@ -176,6 +187,7 @@ function createContext(options = {}) {
 function deployment(ctx) {
 	const opts = {};
 	if (ctx.options.defaultFramework !== void 0) opts.defaultFramework = ctx.options.defaultFramework;
+	if (ctx.options.domain !== void 0) opts.domain = ctx.options.domain;
 	return new VercelDeployment(ctx.client, opts);
 }
 function createPlugin(options = {}) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/holocron-plugin-vercel",
-  "version": "5.0.0-alpha.27",
+  "version": "5.0.0-alpha.28",
   "description": "Holocron plugin for Vercel. Implements the deployment capability against the Vercel REST API.",
   "keywords": [
     "deployment",
@@ -46,11 +46,11 @@
     "tsx": "4.23.12",
     "typescript": "^5.9.3",
     "vitest": "^4.1.11",
-    "@theholocron/cli": "5.0.0-alpha.27"
+    "@theholocron/cli": "5.0.0-alpha.28"
   },
   "peerDependencies": {
     "@theholocron/vercel-client": "^1.23.0",
-    "@theholocron/cli": "5.0.0-alpha.27"
+    "@theholocron/cli": "5.0.0-alpha.28"
   },
   "peerDependenciesMeta": {
     "@theholocron/vercel-client": {}