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

package/README.md

@@ -64,9 +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); 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)
 
 Out of scope for alpha.0 (file a follow-up if needed):
 
-- Domain management (`addDomain` / `removeDomain`)
+- Domain removal (`removeDomain`)
 - Deletion (`deleteProject`)
 - Marketplace integrations (e.g. `vercel install neon` for vault-managed databases)

package/dist/index.d.mts

@@ -31,6 +31,21 @@ declare class VercelDeployment implements Deployment {
   }): Promise<DeploymentRecord>;
   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 — 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.
+   */
+  ensureCustomDomain(projectId: string, hostname: string): Promise<void>;
   private getProjectByName;
 }
 //#endregion

package/dist/index.mjs

@@ -75,6 +75,25 @@ var VercelDeployment = class {
 			url: raw.url
 		};
 	}
+	/**
+	* 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 — 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.
+	*/
+	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);
+	}
 	async getProjectByName(name) {
 		try {
 			return mapProject(await this.client().projects.get(name));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/holocron-plugin-vercel",
-  "version": "5.0.0-alpha.26",
+  "version": "5.0.0-alpha.27",
   "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.22.0",
+    "@theholocron/http-client": "^1.23.0",
     "@theholocron/tsconfig": "^8.0.0",
     "@theholocron/tsdown-config": "^8.0.0",
-    "@theholocron/vercel-client": "^1.22.0",
+    "@theholocron/vercel-client": "^1.23.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.26"
+    "@theholocron/cli": "5.0.0-alpha.27"
   },
   "peerDependencies": {
-    "@theholocron/vercel-client": "^1.22.0",
-    "@theholocron/cli": "5.0.0-alpha.26"
+    "@theholocron/vercel-client": "^1.23.0",
+    "@theholocron/cli": "5.0.0-alpha.27"
   },
   "peerDependenciesMeta": {
     "@theholocron/vercel-client": {}