Electron Releases

Description of Change

Tightens the electron-node-upgrade skill so patch-fix commits on node roller branches cite the right upstream change.

• references/phase-one-commit-guidelines.md: replace "use git log or git blame" with a required procedure. Name the symbol the fix touches, find its introducing commit with git log -S or git blame against refs/patches/upstream-head, verify that commit's diff contains the symbol, then take its PR-URL: and use its subject line verbatim as the title. Recency queries like git log -10 -- file are explicitly not attribution.
• references/phase-one-commit-guidelines.md: new "Reuse Fixes From Sibling Roller Branches" section. Check roller/node/main and sibling roller/node/{N}-x-y branches for the same version first and reuse patch names, content, titles and refs verbatim.
• references/patch-analysis.md: same procedure in the "Finding the Upstream Commit for a Change" section, and a note that the recent-history step is for orientation only.
• references/phase-two-commit-guidelines.md: point at the phase-one procedure and the sibling-branch check.
• SKILL.md: pre-flight item to look for the same roll on other branches.

Prompted by #53250, where the guard for ReadASN1Element was attributed to nodejs/node#64547 (the newest commit touching ncrypto.cc) instead of nodejs/node#64211 (the commit that added it), and where the same JSPI fix landed under a different patch name than on main and 43-x-y.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• relevant documentation is changed or added
• PR title follows semantic commit guidelines

Release Notes

Notes: none