chore: retarget shared toolchain ref @prm/toolchain -> @main

.changeset/README.md

@@ -21,7 +21,7 @@ pnpm change --bump <none|patch|minor|major> --summary "<changelog entry>" [<pkg>
 The release pipeline is the shared toolchain in
 `systemfsoftware/pnpm-release-management`, consumed as a reusable workflow
 (`.github/workflows/release.yml` and `changeset-check.yml` are thin callers
-pinned to its `prm/toolchain` ref). On a push to `main` it opens or updates the
+pinned to its `main` ref). On a push to `main` it opens or updates the
 version PR when intents are pending, and otherwise tags each released version
 `<pkg>@vX.Y.Z` and cuts a GitHub Release from its authored changelog. A version
 with no such tag is what the pipeline treats as owed a release.

.github/workflows/changeset-check.yml

@@ -9,9 +9,9 @@ permissions:
 
 jobs:
   require-changeset:
-    uses: systemfsoftware/pnpm-release-management/.github/workflows/changeset-check.yml@prm/toolchain
+    uses: systemfsoftware/pnpm-release-management/.github/workflows/changeset-check.yml@main
     with:
-      tools-ref: prm/toolchain
+      tools-ref: main
     permissions:
       contents: read
       pull-requests: read

.github/workflows/release.yml

@@ -14,9 +14,9 @@ permissions:
 
 jobs:
   release:
-    uses: systemfsoftware/pnpm-release-management/.github/workflows/release.yml@prm/toolchain
+    uses: systemfsoftware/pnpm-release-management/.github/workflows/release.yml@main
     with:
-      tools-ref: prm/toolchain
+      tools-ref: main
     permissions:
       contents: write
       pull-requests: write

release.jsonc

@@ -1,7 +1,7 @@
 {
   // The release pipeline is the shared systemfsoftware/pnpm-release-management
   // toolchain, consumed as a reusable workflow (see .github/workflows/release.yml
-  // and changeset-check.yml, pinned to prm/toolchain). This config is the only
+  // and changeset-check.yml, pinned to main). This config is the only
   // repo-local input it reads. Distribution is Nix flakes consumed from git
   // refs: a <pkg>@vX.Y.Z git tag is the durable record a version shipped, so
   // there is no npm-registry publish step.