fix(release): refresh npm metadata while awaiting registry propagation

[Si40Code]

Summary

• Allow up to 30 attempts at ten-second intervals for registry metadata and installation checks.
• Prefer fresh npm responses over cached pre-publish metadata and explicitly select the public npm registry.
• Preserve failure-on-timeout, all publish gates, OIDC and immutable versions. No package version or SDK runtime changes.

Evidence

Release run 35846704730 successfully published @call-e/[email protected] at 10:05:50 UTC. npm reported the package was still processing. The registry showed the new version/latest at 10:07:26 UTC, but the previous 10-attempt metadata check timed out and installation continued reading stale metadata.

The published version is now verified from the registry. A fresh temporary installation passed Calls and Goal helpers plus CLI help. The existing release must not be republished or its tag moved.

Validation

• Parsed workflow YAML and checked both changed shell steps with bash -n.
• Executed both changed post-publish steps against the actual published 1.0.1: passed.
• git diff --check: passed.
• SDK code unchanged; repository CI runs the standard validation.