fix: publish to npm registry directly instead of Yarn proxy

Yarn's registry proxy (registry.yarnpkg.com) is failing with "Not found"
for scoped package publishes. Explicitly set the npm registry in
publishConfig to bypass the proxy.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: masnwilliams

package.json

@@ -14,7 +14,8 @@
   ],
   "private": false,
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "registry": "https://registry.npmjs.org"
   },
   "scripts": {
     "test": "./scripts/test",