Recover and diagnose the 3.0.0 release

[TDanks2000]

Summary

• keep version-PR creation unchanged
• make npm publication and GitHub release creation one explicit idempotent sequence
• preserve the exact-version registry check before publishing
• create and push the version tag explicitly before creating the GitHub release
• capture npm and GitHub CLI output on failure
• post exact release results to Release workflow status #23
• grant only the additional issues: write permission required for reporting

Why

The 3.0.0 version commit is on main, but npm and GitHub still expose 2.2.0. The previous workflow did not leave an inspectable failure report. Merging this PR safely retries 3.0.0: already-completed registry or release steps are skipped, while any remaining failure is reported verbatim in issue #23.

Validation

• parsed the complete workflow with Ruby's YAML parser
• publication remains restricted to main and the protected npm environment
• npm publication still uses Trusted Publishing and provenance
• retries remain safe because the exact npm version and GitHub release are checked first