rpc-bastion 0.3.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Bastion contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,52 @@
+# rpc-bastion
+
+The `bastion` diagnostics CLI — inspect endpoints, watch transactions, and run
+chaos scenarios, all on the same resilient pool/sender the SDK uses.
+
+> Not yet published to npm (the package name is pending). Build it from the repo
+> and run the bin directly:
+
+```bash
+npm install && npm run build                    # from the repo root
+node packages/cli/dist/bin.cjs <command>        # e.g. doctor --json
+# (after publication this becomes `npx bastion <command>`)
+```
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `bastion doctor --endpoints <urls\|--config file> [--probes N] [--json]` | One-shot diagnostics per endpoint: p50 latency, `getHealth`, slot vs cluster max, version. Pretty table or `--json`. |
+| `bastion monitor --endpoints <urls\|--config file> [--interval ms]` | Live endpoint health table (status dot, latency sparkline, error rate, slot lag, breaker) refreshing on an interval. |
+| `bastion watch-tx <signature> --endpoints <urls>` | Watch a transaction to a terminal state (confirmed / failed / expired), reusing the confirmation engine. |
+| `bastion simulate --scenario <name> \| --list` | Run a built-in testkit chaos scenario against a local mock pool and render it live. |
+
+Config file (`bastion.config.json`): `{ "endpoints": ["..."], "jito": { "region": "..." } }`.
+
+## Examples
+
+```bash
+bastion doctor --endpoints https://api.devnet.solana.com --json
+bastion simulate --list
+bastion simulate --scenario flaky-endpoint
+bastion monitor --config bastion.config.json --interval 1000
+```
+
+## Architecture (why it's testable)
+
+All **data-fetching and aggregation** lives in pure functions under
+[`src/data/`](./src/data) — endpoint probing (`runDoctor`), health projection
+(`summarizeSnapshot`), scenario simulation (`runSimulation`), and the config/arg
+parsers. These are exported from the package and fully unit-tested (against the
+testkit mock RPC, with injected clocks — no real network in tests).
+
+The **rendering + live-I/O** layer lives under [`src/ui/`](./src/ui) (ANSI
+tables/sparklines, the command orchestrators, the `bastion` executable) and is
+excluded from coverage — the data it renders is what's verified.
+
+```ts
+// programmatic use of the data layer
+import { runDoctor, doctorReportToJson } from 'rpc-bastion';
+const report = await runDoctor(urls, { rpcFactory });
+console.log(doctorReportToJson(report));
+```

package/dist/args-O3XNV7QR.js

@@ -0,0 +1,3 @@
+export { flagBool, flagInt, flagString, parseArgs } from './chunk-Q2OA5HXD.js';
+//# sourceMappingURL=args-O3XNV7QR.js.map
+//# sourceMappingURL=args-O3XNV7QR.js.map

package/dist/args-O3XNV7QR.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"names":[],"mappings":"","file":"args-O3XNV7QR.js"}