Fix npm OIDC trusted publishing: trailing slash in publishConfig.registry

[Copilot]

@semantic-release/npm@13.1.5 uses strict equality to gate the OIDC path: OFFICIAL_REGISTRY === registry, where OFFICIAL_REGISTRY = "https://registry.npmjs.org/" (trailing slash). With publishConfig.registry set to "https://registry.npmjs.org" (no trailing slash), this check was always false — OIDC was silently bypassed, falling through to token auth which also failed.

The Trusted Publisher was correctly configured on npmjs.org; the mismatch was entirely on the client side.

Changes

• package.json — Add trailing slash to publishConfig.registry so it matches OFFICIAL_REGISTRY exactly, allowing oidcContextEstablished() to proceed to the OIDC token exchange
• build.yaml — Revert registry-url on setup-node (re-added by a previous fix attempt); it is not needed and actively harmful — it writes a .npmrc auth token entry that causes @semantic-release/npm to skip OIDC and attempt npm whoami with an unset NODE_AUTH_TOKEN

[andrew-welker]

@copilot add an empty commit with a valid conventional commit message. Also, add instructions in this repo so that agents ALWAYS use conventional commit syntax.

[Copilot]

@copilot add an empty commit with a valid conventional commit message. Also, add instructions in this repo so that agents ALWAYS use conventional commit syntax.

Done in commits docs(ci): add copilot-instructions with conventional commit requirements and chore: trigger release pipeline.

The .github/copilot-instructions.md file documents the full Conventional Commits convention (allowed types, scopes, breaking-change syntax, and examples) so all Copilot agents in this repository will use it going forward.

[andrew-welker]

@copilot based on the releaserc.json, and standard conventional commit syntax, chore: won't trigger a version increment. Use fix, or feat.

[Copilot]

@copilot based on the releaserc.json, and standard conventional commit syntax, chore: won't trigger a version increment. Use fix, or feat.

Amended to fix: trigger release pipeline with OIDC trusted publishing fix — this will satisfy semantic-release's fix release rule and trigger a patch version increment.