Create real-chain CI smoke system

[Andre-Diamond]

Why this exists

• Protects v1 API routes from regressions on pull requests.
• Verifies behavior against real blockchain conditions (preprod), not only mocked/unit paths.
• Keeps wallet bootstrap stable while allowing route tests to grow incrementally.
• Makes it easy to add new API route checks as composable scenario steps.

High-level flow

CI runs these stages in order:

1. Bootstrap (create-wallets.ts)

   • Derives signer addresses from mnemonic secrets.
   • Provisions one bot key per signer address.
   • Creates test wallets (legacy, hierarchical, sdk).
   • Grants all signer bots cosigner access to created wallets.
   • Seeds baseline pending transactions.
   • Writes a versioned context JSON consumed by all later steps.

2. Route chain (run-route-chain.ts)

   • Loads and validates bootstrap context.
   • Loads enabled scenarios from scenarios/manifest.ts.
   • Executes steps in deterministic order with critical/non-critical failure semantics.
   • Emits console summary and machine-readable JSON report.

3. Artifacts

   • Route-chain JSON report is written to ci-artifacts/ci-route-chain-report.json.
   • Workflow uploads it as an artifact for triage.

Commit history

[QSchlegel]

Status snapshot (2026-04-23): the route-chain system itself is landed — ci-smoke-preprod.yml, scripts/ci-smoke/create-wallets.ts, scripts/ci-smoke/run-route-chain.ts, and the scenario/manifest harness are all in place via PR #217, and the skip-gracefully path from `dc49af2` keeps PR CI green when secrets are missing. Every successful run since has completed in ~7-8s, which means it hit the skip path.

We won't have a real end-to-end green run (with a smoke-report artifact and the ci-artifacts/ci-route-chain-report.json written) until the SMOKE_* repo secrets are configured (SMOKE_API_BASE_URL, SMOKE_SIGNER_MNEMONIC_1, SMOKE_SIGNER_MNEMONIC_2, SMOKE_BOT_MNEMONIC, SMOKE_BOT_KEY_ID, SMOKE_BOT_SECRET).

Leaving this open until the first real green run on a recent PR is linked.