fix(release): handle npm errors without summaries

[omegent-app]

Why

npm 12 can return an E403 publish error without a summary. Changesets assumes every summary is a string and crashes while classifying the error, hiding npm's actionable detail and preventing duplicate-publish races from completing cleanly.

What

Patch @changesets/cli@2.31.0 to safely inspect npm errors and recognize the existing “already published” message in either summary or detail.

How

Duplicate versions are silently skipped as Changesets intends. An E403 that does not contain the duplicate-publish message remains a failure and retains its npm diagnostics.

Remarks

This is release-tooling only. It is intentionally narrow and can be removed once Changesets ships the equivalent guard.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/effect-app/libs/@effect-app/cli@839

effect-app

npm i https://pkg.pr.new/effect-app/libs/effect-app@839

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-codegen-model@839

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-shared-config@839

@effect-app/infra

npm i https://pkg.pr.new/effect-app/libs/@effect-app/infra@839

@effect-app/vue

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue@839

@effect-app/vue-components

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue-components@839

commit: 3a3d344