Update release guides

Signed-off-by: Émile Ré <emile@getprobo.com>

contrib/claude/release/n8n-nodes-probo.md

@@ -1,58 +1,31 @@
 # Release `@probo/n8n-nodes-probo`
 
-Entrypoint for releasing the n8n nodes package. Read
-[README.md](./README.md) first for overall flow, changelog rules, and the
-non-empty-track guarantee.
+After confirming commits below, follow the
+[common steps](./README.md#3-common-steps-every-track).
 
 ## Track facts
 
-- **Tag pattern**: `@probo/n8n-nodes-probo/v*` (the `@` and `/` are valid
-  in Git tag refs)
+- **Tag pattern**: `@probo/n8n-nodes-probo/v*` (the `@` and `/` are
+  valid in Git tag refs)
 - **Version source**: `packages/n8n-node/package.json`
+- **Version bump**: `npm --workspace @probo/n8n-nodes-probo version <X.Y.Z> --no-git-tag-version`
+- **Build**: `npm --workspace @probo/n8n-nodes-probo run build`
 - **Changelog**: `packages/n8n-node/CHANGELOG.md`
+- **Files to stage**: `packages/n8n-node/package.json`,
+  `packages/n8n-node/CHANGELOG.md`, `package-lock.json`
 - **Workflow**: `.github/workflows/release-npm-n8n-node.yaml`
-- **Path filter** (for log/scoping): `packages/n8n-node`
+- **Path filter**: `packages/n8n-node`
 
-## Steps
+## Detect commits
 
-1. From a clean `main`, list commits since the last
-   `@probo/n8n-nodes-probo` tag:
+```shell
+git log $(git describe --tags --abbrev=0 --match='@probo/n8n-nodes-probo/v*')..HEAD --oneline \
+  -- packages/n8n-node
+```
 
-   ```shell
-   git log $(git describe --tags --abbrev=0 --match='@probo/n8n-nodes-probo/v*')..HEAD --oneline \
-     -- packages/n8n-node
-   ```
+If empty or non-user-facing only, do not release this track.
 
-   If the list is empty (or contains only non-user-facing commits), do
-   not release this track.
+## Notes
 
-2. Decide the version bump (PATCH for fixes, MINOR for features).
-3. Bump the version using npm so `package.json` and `package-lock.json`
-   stay consistent:
-
-   ```shell
-   npm --workspace @probo/n8n-nodes-probo version <X.Y.Z> --no-git-tag-version
-   ```
-
-4. Run the workspace build to confirm it succeeds with the new version
-   (and to surface any compile errors before we tag):
-
-   ```shell
-   npm --workspace @probo/n8n-nodes-probo run build
-   ```
-
-5. Write the new entry in `packages/n8n-node/CHANGELOG.md` following the
-   rules in [README.md](./README.md#2-writing-a-changelog-entry).
-6. Show the user the changelog diff and the new version. Wait for
-   confirmation.
-7. Stage the files modified by the version bump and changelog edit
-   (typically `packages/n8n-node/package.json`,
-   `packages/n8n-node/CHANGELOG.md`, and `package-lock.json`). Commit
-   subject: `Release @probo/n8n-nodes-probo/v<version>`. No body.
-8. Annotated tag:
-   `git tag -a @probo/n8n-nodes-probo/v<version> -m "@probo/n8n-nodes-probo/v<version>"`.
-9. Push: `git push origin main --follow-tags`.
-
-CI workflow `release-npm-n8n-node.yaml` verifies the tag matches
-`package.json`, publishes to npm with provenance + SBOM, and creates a
-GitHub Release.
+CI verifies the tag matches `package.json`, publishes to npm with
+provenance + SBOM, and creates a GitHub Release.