Release next version as patch (1.5.x), not major

The unified-auth changeset cascaded to a 2.0.0 major release: four
fixed-group plugins (openapi, mcp, graphql, onepassword) declare
@executor-js/react as a peerDependency, and changesets' default rule
major-bumps any package whose peerDependency changes. The fixed group
then propagated that major to every member.

- Set the changeset bumps to patch.
- Enable onlyUpdatePeerDependentsWhenOutOfRange so peer-dependents only
  major-bump when the new version leaves the declared range (workspace:*
  always satisfies, so no forced major).

Author: RhysSullivan

.changeset/config.json

@@ -25,6 +25,9 @@
   "access": "public",
   "baseBranch": "main",
   "updateInternalDependencies": "patch",
+  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
+    "onlyUpdatePeerDependentsWhenOutOfRange": true
+  },
   "ignore": [
     "@executor-js/local",
     "@executor-js/host-mcp",

.changeset/unified-auth-methods.md

@@ -1,6 +1,6 @@
 ---
-"executor": minor
-"@executor-js/react": minor
+"executor": patch
+"@executor-js/react": patch
 ---
 
 **One auth model across OpenAPI, GraphQL, and MCP**