fix(xc_admin): rethrow caught error instead of empty Error

[dhruvja]

Summary

The change replaces throw new Error(); with throw err; in the top-level catch of both crank scripts.

Rationale

• throw new Error() creates a brand-new Error with no message and a stack trace that points at line 63 (or 231) which is at the re-throw itself, not at where the failure actually happened.
• The original error is discarded. console.error(err) prints it to stderr first, but Node's eventual "uncaught exception" report shows the thrown error which is the empty one.
• Result in practice: an operator looking at why a crank process died sees a useless empty-message stack ending at throw new Error() instead of the real RPC timeout / auth failure / malformed VAA / whatever triggered it.
• throw err; preserves the original error message, stack, and any properties like cause. Node reports the real failure in its crash output, so root-causing a production incident is one less instead of a forensic dig.

How has this been tested?

• Current tests cover my changes
• Added new tests
• Manually tested the code

[vercel]

@dhruvja is attempting to deploy a commit to the Pyth Network Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
api-reference	Skipped		Apr 22, 2026 7:20am
proposals	Skipped		Apr 22, 2026 7:20am