chore: upgrade biome to 2.5.1 and migrate config (#105)

Author: jamie-at-bunny

biome.json

@@ -1,5 +1,5 @@
 {
-  "$schema": "https://biomejs.dev/schemas/2.4.12/schema.json",
+  "$schema": "https://biomejs.dev/schemas/2.5.1/schema.json",
   "vcs": {
     "enabled": true,
     "clientKind": "git",
@@ -15,7 +15,7 @@
   "linter": {
     "enabled": true,
     "rules": {
-      "recommended": true,
+      "preset": "recommended",
       "suspicious": {
         "noExplicitAny": "off"
       },

bun.lock

@@ -23,7 +23,7 @@
     "release": "changeset publish"
   },
   "devDependencies": {
-    "@biomejs/biome": "^2.4.12",
+    "@biomejs/biome": "^2.5.1",
     "@changesets/changelog-github": "^0.6.0",
     "@changesets/cli": "^2.30.0",
     "@types/bun": "latest",

package.json

@@ -41,7 +41,9 @@ export async function resolveDnsScriptId(
 
   const manifest = loadManifest<DnsScriptManifest>(DNS_SCRIPT_MANIFEST);
   if (manifest.id) {
-    logger.dim(`Using linked DNS script ${manifest.name ?? manifest.id}.`);
+    // Validate the linked ID; a stale or hand-edited manifest can point at a non-DNS script.
+    const script = await fetchDnsScript(client, manifest.id);
+    logger.dim(`Using linked DNS script ${script.Name ?? manifest.id}.`);
     return manifest.id;
   }