solana-resilience-kit 1.0.1 → 1.0.2

package/README.md

@@ -143,13 +143,14 @@ The package ships an executable, `solana-resilience-diagnose`, built on the same
 `Diagnostics` core (`src/cli/diagnose.ts`). It answers the two questions an
 operator asks when a Solana dApp misbehaves — *which of my providers is healthy
 and freshest?* and *did this transaction land, expire, or is it still pending?* —
-without writing any code. Run it with `npx` (no install) or from a dependency's
-`node_modules/.bin`:
+without writing any code. Run it zero-install with `npx`, or — once the package
+is a dependency — call `solana-resilience-diagnose` directly (it is on your
+`node_modules/.bin`):
 
 ```bash
 # Probe provider health across one or more endpoints (reuses the pool's own
 # slot-freshness ranking, so "freshest" matches what routing would pick):
-npx solana-resilience-diagnose probe \
+npx -p solana-resilience-kit solana-resilience-diagnose probe \
   --rpc https://api.mainnet-beta.solana.com \
   --rpc https://my-backup.rpc
 ```
@@ -167,7 +168,7 @@ Freshest: https://api.mainnet-beta.solana.com  ·  1/2 healthy.
 # Explain a transaction's outcome point-in-time (no polling loop): it compares
 # the current signature status and block height against lastValidBlockHeight —
 # the canonical Solana rule — and never re-signs.
-npx solana-resilience-diagnose explain \
+npx -p solana-resilience-kit solana-resilience-diagnose explain \
   --rpc https://api.mainnet-beta.solana.com \
   --sig 5xRe...your-signature \
   --lvbh 287654321

package/dist/cli/index.js

@@ -19,6 +19,7 @@
  * tx) · 2 a usage error.
  */
 import { createSolanaRpc } from "@solana/kit";
+import { realpathSync } from "node:fs";
 import { pathToFileURL } from "node:url";
 import { SdkError } from "../errors.js";
 import { Diagnostics } from "./diagnose.js";
@@ -211,8 +212,11 @@ export async function run(argv, deps = {}) {
     return result.status === "expired" ? 1 : 0;
 }
 /* v8 ignore start -- process bootstrap; only runs when invoked as the binary */
+// Resolve symlinks: npm installs the bin as a symlink in node_modules/.bin, so
+// process.argv[1] is that link while import.meta.url is the real dist file —
+// comparing realpaths is what makes the binary fire when run by name.
 const entry = process.argv[1];
-if (entry !== undefined && import.meta.url === pathToFileURL(entry).href) {
+if (entry !== undefined && import.meta.url === pathToFileURL(realpathSync(entry)).href) {
     run(process.argv.slice(2)).then((code) => {
         process.exitCode = code;
     }, (err) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "solana-resilience-kit",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Vendor-neutral, client-side resilience and observability layer for Solana dApps, built on @solana/kit (web3.js v2).",
   "type": "module",
   "license": "MIT",