Remove legacy TypeScript 1.x packages (#383)

* Remove legacy TypeScript packages

* Fix wrapper optional dependency lockfile entries

* Coerce search limit for Node SDK binding

* Remove stale README migration context

Author: willwashburn

.github/workflows/ci.yml

@@ -1,10 +1,7 @@
 name: CI
 
-# Build + test the full workspace on every PR and on every push to main.
-# Catches the failure mode where a syntactically-broken file lands on main
-# undetected because publish.yml only runs on workflow_dispatch — e.g. the
-# unescaped backticks in archive.ts's SCHEMA_SQL template literal that
-# slipped past review and broke `tsc` for everyone downstream.
+# Build + test the Rust workspace and remaining npm wrappers on every PR and
+# on every push to main.
 
 on:
   pull_request:
@@ -37,20 +34,13 @@ jobs:
       - name: Install deps
         run: pnpm install --frozen-lockfile
 
-      # `tsc --build` walks every package in the workspace and is the gate
-      # for parse-level failures. Run it as its own step so a syntax error
-      # surfaces clearly in the failure summary instead of being lumped in
-      # with test output.
-      - name: Build workspace
-        run: pnpm -r run build
+      - name: Build npm wrappers
+        run: pnpm -r --if-present run build
 
-      - name: Run tests
+      - name: Run npm tests
         run: pnpm run test
 
   cargo-build-and-test:
-    # Sibling job to build-and-test: as the Rust port (#240) lands crate by
-    # crate, the Cargo workspace lives alongside the TS workspace. Run this
-    # job in parallel with the TS job so neither tree blocks the other.
     runs-on: ubuntu-latest
     steps:
       - name: Checkout

.github/workflows/cli-build.yml

@@ -1,7 +1,7 @@
 name: cli build
 
 # Build prebuilt `burn` binaries for every platform we publish to npm under
-# `@relayburn/cli-*`. PRs validate the matrix; the cutover publish workflow
+# `@relayburn/cli-*`. PRs validate the matrix; the publish workflow
 # (`.github/workflows/publish.yml`) calls this workflow via `workflow_call`
 # to produce the binaries it then stages into per-platform packages.
 #

.github/workflows/napi-build.yml

@@ -120,16 +120,6 @@ jobs:
       - name: Install workspace deps
         run: pnpm install --frozen-lockfile
 
-      - name: Install packages/sdk-node deps
-        # `packages/sdk-node` is intentionally excluded from the pnpm
-        # workspace until the 2.0 cutover (see pnpm-workspace.yaml), so
-        # `pnpm install` at the root won't pull its devDependencies
-        # (`@napi-rs/cli`, `esbuild`). `--ignore-workspace` makes pnpm
-        # treat this directory as a standalone project and install into
-        # `packages/sdk-node/node_modules/` directly.
-        working-directory: packages/sdk-node
-        run: pnpm install --ignore-workspace --no-frozen-lockfile
-
       - name: Lockstep Cargo.toml to release version
         # When invoked via the publish workflow, sed the workspace
         # `[workspace.package].version` (and the path-dep `version = "X.Y"`
@@ -204,28 +194,9 @@ jobs:
         working-directory: packages/sdk-node
         run: node --test 'test/esbuild-smoke.test.js'
 
-      - name: Build TS workspace (for conformance step)
-        # Conformance imports `packages/sdk/index.js` (the TS 1.x SDK), which
-        # imports `@relayburn/{ledger,analyze,ingest,reader}`. Those packages
-        # ship as `dist/index.js` so they need a `tsc --build` pass before
-        # they can be required at runtime. The matrix runs `pnpm install` at
-        # the root above, but no build — flip that here so the conformance
-        # step's TS-side import resolves cleanly.
-        #
-        # Skipped on the aarch64-linux leg: that leg cross-compiles on an
-        # x64 host, so `node` (the runner's interpreter) cannot load the
-        # arm64 `.node` artifact we just built. Building the TS workspace
-        # is wasted work on that leg too — the conformance step below is
-        # also gated off there.
-        if: matrix.target != 'aarch64-unknown-linux-gnu'
-        run: pnpm run build
-
-      - name: Conformance test (TS @relayburn/sdk@1.x vs napi-rs @2.0.0-pre)
-        # The conformance suite seeds a deterministic ledger via
-        # `tests/fixtures/cli-golden/scripts/build-ledger.mjs`, runs each of
-        # the 7 verbs against both impls into matched tmp homes, and asserts
-        # `deepStrictEqual`. With α (#354) shape-conformant, this gate is
-        # the acceptance test for #247.
+      - name: Native SDK smoke test
+        # The suite runs the Node facade against the committed cli-golden
+        # ledger and checks stable result shapes for the exported verbs.
         #
         # Skipped on the aarch64-linux leg: that leg is a CROSS-COMPILE
         # (host=ubuntu-latest x64, target=aarch64-unknown-linux-gnu), so
@@ -239,10 +210,6 @@ jobs:
         # and exercise the same conformance contract; this leg's job is
         # purely to validate the cross-compile build + artifact upload.
         #
-        # If conformance fails on a verb, the failure is α follow-up scope —
-        # see the test header for the seeding strategy and the
-        # `tests/fixtures/cli-golden/ledger/.gitignore` note about the
-        # JSONL→SQLite replay the Rust SDK requires.
         if: matrix.target != 'aarch64-unknown-linux-gnu'
         working-directory: packages/sdk-node
         env:

.github/workflows/publish.yml

@@ -48,9 +48,9 @@ concurrency:
   group: publish-${{ github.ref }}
   cancel-in-progress: false
 
-# 2.0 cutover (epic #240) target shape:
+# Publish target shape:
 #
-#   TS-only umbrellas (3):
+#   npm umbrellas (3):
 #     - relayburn                    packages/relayburn/
 #     - @relayburn/sdk (napi)        packages/sdk-node/
 #     - @relayburn/mcp               packages/mcp/
@@ -59,11 +59,10 @@ concurrency:
 #     - @relayburn/cli-<short>       packages/relayburn/npm/<short>/  (Rust burn binary)
 #     - @relayburn/sdk-<short>       packages/sdk-node/npm/<short>/   (napi-rs .node)
 #
-# Total: 11 npm packages. The five legacy TS packages
+# Total: 11 npm packages. The five legacy TypeScript implementation packages
 # (`@relayburn/{reader,ledger,analyze,ingest,cli}`) are intentionally not
 # in the publish loop — `npm deprecate` for those is a manual post-cutover
-# step. Their source dirs stay (they back the conformance fixture seeder
-# and the cli-golden suite).
+# step.
 #
 # crates.io still ships exactly two crates (`relayburn-sdk` + `relayburn-cli`).
 

.github/workflows/verify-publish.yml

@@ -3,7 +3,7 @@ name: Verify Publish
 # Manually triggered smoke test against the npm registry — run after a
 # Publish Packages workflow completes. Installs the just-published package into
 # a clean environment and exercises it enough to catch "published but broken"
-# failures (bin missing +x, workspace:* deps not rewritten, missing exports,
+# failures (bin missing +x, missing exports, optional dependency resolution,
 # etc.).
 
 on:
@@ -17,7 +17,6 @@ on:
         options:
           - 'relayburn'
           - '@relayburn/sdk'
-          - '@relayburn/mcp'
       version:
         description: 'Version to verify (defaults to the "latest" dist-tag)'
         required: false