motedb-python 0.15.0__tar.gz → 0.15.2__tar.gz

motedb_python-0.15.2/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,73 @@
+name: Bug report
+description: Something returns the wrong result, panics, corrupts data or hangs.
+title: "[bug] "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the report. Install / import problems have their own template ("Installation problem").
+        Security-relevant bugs (crash from crafted input, path traversal, data loss): please use
+        private reporting instead — see SECURITY.md.
+  - type: input
+    id: version
+    attributes:
+      label: MoteDB version
+      description: "`cargo tree -i motedb`, `python -c \"import importlib.metadata as m; print(m.version('motedb-python'))\"`, or `node -p \"require('motedb/package.json').version\"`"
+      placeholder: "0.15.0"
+    validations:
+      required: true
+  - type: dropdown
+    id: surface
+    attributes:
+      label: Where you hit it
+      options:
+        - Rust crate
+        - Python (motedb-python)
+        - Node.js (motedb)
+        - Go binding
+        - motedb-cli
+        - SQL (any surface)
+    validations:
+      required: true
+  - type: input
+    id: platform
+    attributes:
+      label: Platform
+      placeholder: "macOS 15 arm64 / Ubuntu 24.04 x86_64 (glibc) / Alpine 3.20 (musl) / Windows 11 x64"
+    validations:
+      required: true
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened
+      description: Actual behaviour, including the full error message or panic backtrace (`RUST_BACKTRACE=1`).
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What you expected
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Minimal reproduction
+      description: |
+        The smallest schema + statements (or code) that shows the problem. Starting from an empty
+        database is ideal. If it needs an existing database file, say whether you can share it.
+      render: sql
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: "Output with `RUST_LOG=motedb=debug` (Rust) or the equivalent logger in your language, if relevant."
+      render: text
+  - type: textarea
+    id: config
+    attributes:
+      label: Configuration
+      description: "Preset (`for_edge` / `for_robotics` / `for_embodied` / default) and any overridden `DBConfig` fields, read-only container or not."

motedb_python-0.15.2/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions & usage help
+    url: https://github.com/motedb/motedb/discussions/categories/q-a
+    about: "\"How do I…\", \"is this expected?\", schema design — ask in Discussions."
+  - name: Security vulnerability
+    url: https://github.com/motedb/motedb/security/advisories/new
+    about: Crash from crafted input, path traversal, silent data loss — report privately (see SECURITY.md).
+  - name: Show & tell
+    url: https://github.com/motedb/motedb/discussions/categories/show-and-tell
+    about: Built something on MoteDB? Robot, pipeline, benchmark — we would love to see it.

motedb_python-0.15.2/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,50 @@
+name: Feature request
+description: A capability MoteDB should have — SQL syntax, an API, a format, a platform.
+title: "[feat] "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Not sure it fits? Open a [Discussion](https://github.com/motedb/motedb/discussions) first.
+        Out of scope by design (see `docs/design/`): distributed / clustered mode, a client-server daemon,
+        a visualization frontend, full DuckDB-level SQL parity.
+  - type: textarea
+    id: problem
+    attributes:
+      label: The problem
+      description: What you are trying to do and why the current engine makes it hard. Concrete data shapes (rows, dimensions, rates) help a lot.
+    validations:
+      required: true
+  - type: dropdown
+    id: scenario
+    attributes:
+      label: Scenario
+      options:
+        - On-robot / edge capture (power-fail safety, low memory)
+        - Training-data pipeline (MCAP / LeRobot / Parquet / DataLoader)
+        - Retrieval (vector / FTS / hybrid / trajectory)
+        - Time series / episodes / alignment (ASOF JOIN etc.)
+        - SQL surface / types
+        - SDK / bindings / platform support
+        - Tooling (CLI, doctor, MCP, observability)
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed shape
+      description: The SQL or API you would like to write. Pseudocode is fine.
+      render: sql
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: What you do today instead (another tool, a workaround), and why it falls short.
+  - type: checkboxes
+    id: help
+    attributes:
+      label: Contribution
+      options:
+        - label: I am willing to implement this with guidance.

motedb_python-0.15.2/.github/ISSUE_TEMPLATE/install_problem.yml

@@ -0,0 +1,64 @@
+name: Installation problem
+description: pip / npm / cargo install fails, or the module does not load.
+title: "[install] "
+labels: ["install"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please read [docs/18-install-troubleshooting.md](https://github.com/motedb/motedb/blob/main/docs/18-install-troubleshooting.md)
+        first — the package names differ per registry (`pip install motedb-python`, `npm install motedb`,
+        `cargo add motedb`) and most reports are covered there.
+  - type: dropdown
+    id: lang
+    attributes:
+      label: Language
+      options:
+        - Python (pip install motedb-python)
+        - Node.js (npm install motedb)
+        - Rust (cargo add motedb)
+        - Go (bindings/go)
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version you tried to install
+      placeholder: "0.15.0"
+    validations:
+      required: true
+  - type: input
+    id: platform
+    attributes:
+      label: OS / architecture / libc
+      description: "`uname -a` (or `ver` on Windows). On Linux say glibc or musl (Alpine)."
+      placeholder: "Linux 6.8 aarch64, Debian 12 (glibc 2.36) / Alpine 3.20 (musl) / macOS 15 arm64 / Windows 11 x64"
+    validations:
+      required: true
+  - type: input
+    id: runtime
+    attributes:
+      label: Runtime version
+      description: "`python -V && python -m pip --version` / `node -v && npm -v` / `rustc -V && cargo -V`"
+    validations:
+      required: true
+  - type: textarea
+    id: command
+    attributes:
+      label: Exact command
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    id: output
+    attributes:
+      label: Full output
+      description: Everything the command printed, unedited. For Node loader errors include `npm ls | grep motedb-`.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: env
+    attributes:
+      label: Environment details
+      description: "Container / CI image, proxy or private registry mirror, `--no-optional` / `--omit=optional`, pnpm/yarn, virtualenv/conda, anything non-default."

motedb_python-0.15.2/.github/pull_request_template.md

@@ -0,0 +1,29 @@
+<!-- Thanks! Keep the PR focused: one behaviour change per PR. -->
+
+## What
+
+<!-- One or two sentences: what changes and why. Link the issue / discussion / design note. -->
+
+## How
+
+<!-- The approach, and anything a reviewer should look at first (a tricky invariant, a lock order, a format change). -->
+
+## Checklist
+
+- [ ] Tests: new behaviour has a test; a bug fix has a regression test that failed before.
+- [ ] `cargo fmt --check` and `cargo test --lib --all-features` pass locally.
+- [ ] Touched suites pass: `cargo test --test <suite>` (and `CI=1 cargo test --workspace` if the change is broad).
+- [ ] Storage format / WAL / recovery touched → migration test added, `docs/design/2026-10-file-layout.md` rules respected, crash tests run.
+- [ ] SQL surface changed → `README.md` *SQL Support* and `docs/` updated; fuzz template / differential test extended where applicable.
+- [ ] Engine capability added → wired through FFI + Python + Node (+ Go) or the gap is called out below.
+- [ ] New dependency → passes `cargo deny check`, feature-gated if not needed by edge builds.
+- [ ] `CHANGELOG.md` entry under the upcoming version.
+- [ ] No `println!`/`eprintln!` in library code (use the `log` facade macros).
+
+## Performance
+
+<!-- Delete if not relevant. Otherwise: `make compete-quick` JSON attached, or "perf gate unchanged". No ad-hoc numbers. -->
+
+## Not in this PR
+
+<!-- Follow-ups you deliberately left out, so reviewers do not ask for them. -->

{motedb_python-0.15.0 → motedb_python-0.15.2}/.github/workflows/ci.yml

@@ -131,6 +131,7 @@ jobs:
         #     hardware-speed assumptions shared runners can't meet. Tracked in
         #     BENCHMARK.md instead.
         run: |
+          set +e
           cargo test --workspace --all-features -- \
             --test-threads=1 \
             --skip bench_ --skip stress_ --skip perf_ \
@@ -150,13 +151,29 @@ jobs:
             --skip test_scalability_latency \
             --skip test_scalability_memory \
             --skip test_durability_large_dataset_checkpoint_recovery \
-            --skip test_performance_guarantees
+            --skip test_performance_guarantees \
+            > /tmp/ci-test.log 2>&1
+          rc=$?
+          if [ $rc -ne 0 ]; then
+            # 🔑 Anonymous-readable failure surface: the trailing `Running
+            # tests/…` line before the failure block names the failing
+            # binary. (The separate diagnostics step proved unreliable — its
+            # `{ } || …` grouping suppressed set -e and silently skipped.)
+            grep -E "Running (tests|unittests)|FAILED|panicked at|^failures:" /tmp/ci-test.log \
+              | tail -8 | while IFS= read -r line; do
+                echo "::error title=integration-fail::$line"
+              done
+            echo "---- tail of test log ----"
+            tail -30 /tmp/ci-test.log
+          fi
+          exit $rc
       - name: cargo test (workspace, hardware-threshold tests skipped) [attempt 2]
         id: ci2
         if: steps.ci1.outcome == 'failure'
         env:
           CI: "1"
         run: |
+          set +e
           cargo test --workspace --all-features -- \
             --test-threads=1 \
             --skip bench_ --skip stress_ --skip perf_ \
@@ -176,7 +193,22 @@ jobs:
             --skip test_scalability_latency \
             --skip test_scalability_memory \
             --skip test_durability_large_dataset_checkpoint_recovery \
-            --skip test_performance_guarantees
+            --skip test_performance_guarantees \
+            > /tmp/ci-test.log 2>&1
+          rc=$?
+          if [ $rc -ne 0 ]; then
+            # 🔑 Anonymous-readable failure surface: the trailing `Running
+            # tests/…` line before the failure block names the failing
+            # binary. (The separate diagnostics step proved unreliable — its
+            # `{ } || …` grouping suppressed set -e and silently skipped.)
+            grep -E "Running (tests|unittests)|FAILED|panicked at|^failures:" /tmp/ci-test.log \
+              | tail -8 | while IFS= read -r line; do
+                echo "::error title=integration-fail::$line"
+              done
+            echo "---- tail of test log ----"
+            tail -30 /tmp/ci-test.log
+          fi
+          exit $rc
       - name: verdict
         if: always()
         run: |
@@ -191,8 +223,12 @@ jobs:
           # 🔑 K-debug: cargo 顶层一次跑时，crashing binary 会以 exit 101
           # 中断整个套件且不留 FAILED 行。逐 bin 运行并把每个 bin 的退出码
           # 通过 ::error:: annotations 上报（匿名可读）。
+          # 2026-10-21 修复: 曾有一行多余的 `} || echo …`（未配对大括号）
+          # 让本步骤自身以 exit 2 崩溃，逐 bin 上报从未生效过；同时对
+          # rc=101（真实测试失败，有 FAILED 行）也提取失败测试名，不再只
+          # 处理非 101 的编译错误。
           {
-            echo "### mac integration per-binary status"
+            echo "### integration per-binary status ($RUNNER_OS)"
             BINS=$(cargo test --workspace --all-features -- --list 2>/dev/null \
               | grep -E "^Running|^ " >/dev/null; cargo test --workspace \
               --all-features --no-run 2>&1 | grep -oE "Executable tests/[a-z0-9_]+\.rs" \
@@ -213,14 +249,13 @@ jobs:
                 --skip test_performance_guarantees --no-fail-fast \
                 > /tmp/one.log 2>&1
               rc=$?
-              echo "::error title=mac-integration::$t exit=$rc"
-              if [ $rc -ne 0 ] && [ $rc -ne 101 ]; then
-                grep -E "panicked at|FAILED" /tmp/one.log | head -5 \
+              echo "::error title=integration-$RUNNER_OS::$t exit=$rc"
+              if [ $rc -ne 0 ]; then
+                grep -E "^test .* FAILED|^failures:|panicked at" /tmp/one.log | head -8 \
                   | while read -r line; do echo "::error ::$line"; done
               fi
             done
           } || echo "per-binary diagnostics done" >> "$GITHUB_STEP_SUMMARY"
-          } || echo "diagnostics pass done" >> "$GITHUB_STEP_SUMMARY"
 
 
   # ── Cross-compile: aarch64-unknown-linux-gnu (build only) ────────────────

motedb_python-0.15.2/.github/workflows/node-publish.yml

@@ -0,0 +1,304 @@
+name: Node SDK publish (npm)
+
+# Multi-platform prebuilt napi binaries → npmjs.org (unscoped):
+#   motedb (main, pure JS loader) + one platform package per target:
+#   motedb-darwin-arm64 / -darwin-x64 / -linux-x64-gnu / -linux-arm64-gnu /
+#   -win32-x64-msvc
+# Triggers on v* tags (publish) and PRs touching the binding (build-only).
+# 🔑 Publishing needs the NPM_TOKEN repository secret (an npmjs.org automation
+#   token with publish rights on the motedb* packages). The publish job fails
+#   fast with a clear message when it is missing.
+# musl (Alpine) targets: the Alpine-container build step below is wired up but
+#   the two matrix entries stay commented out until a PR run has proven them —
+#   `publish` needs every matrix job green, so an unproven target must not be
+#   able to block a release. Enable them together with the matching
+#   package.json targets/optionalDependencies.
+
+on:
+  push:
+    tags: ["v*"]
+  pull_request:
+    paths:
+      - "bindings/node/**"
+      - ".github/workflows/node-publish.yml"
+  workflow_dispatch:
+
+concurrency:
+  group: node-publish-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: write
+  id-token: write
+  packages: write
+
+jobs:
+  build:
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - os: macos-latest # arm64
+            target: aarch64-apple-darwin
+          # x64-macOS via CROSS-COMPILE on the arm64 runner — macos-13
+          # (Intel) runners are retiring and queue for an hour+; rust
+          # cross-compiles x86_64-apple-darwin natively from arm64.
+          - os: macos-latest # arm64 → cross x64
+            target: x86_64-apple-darwin
+          - os: ubuntu-latest # x64 gnu
+            target: x86_64-unknown-linux-gnu
+          - os: ubuntu-24.04-arm
+            target: aarch64-unknown-linux-gnu
+          # musl: GitHub runners are glibc, so these build in the napi-rs
+          # Alpine image (same recipe as the napi-rs project template; the
+          # image carries the aarch64-linux-musl cross toolchain). Commented
+          # out until proven by a PR run — see the header note.
+          # - os: ubuntu-latest
+          #   target: x86_64-unknown-linux-musl
+          #   docker: ghcr.io/napi-rs/napi-rs/nodejs-rust:lts-alpine
+          # - os: ubuntu-latest
+          #   target: aarch64-unknown-linux-musl
+          #   docker: ghcr.io/napi-rs/napi-rs/nodejs-rust:lts-alpine
+          - os: windows-latest
+            target: x86_64-pc-windows-msvc
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+
+      - uses: dtolnay/rust-toolchain@stable
+        if: ${{ !matrix.docker }}
+        with:
+          targets: ${{ matrix.target }}
+
+      - uses: Swatinem/rust-cache@v2
+        if: ${{ !matrix.docker }}
+        with:
+          workspaces: bindings/node
+          key: ${{ matrix.target }}
+
+      - name: Install napi CLI
+        if: ${{ !matrix.docker }}
+        working-directory: bindings/node
+        run: npm install --no-save @napi-rs/cli@3.10.8
+
+      - name: Build (napi layout)
+        if: ${{ !matrix.docker }}
+        working-directory: bindings/node
+        shell: bash
+        run: |
+          set -e
+          ARGS=(--release --platform --target ${{ matrix.target }} --js false --dts false)
+          npx napi build "${ARGS[@]}"
+
+      - name: Build (napi layout, musl in Alpine container)
+        if: ${{ matrix.docker }}
+        uses: addnab/docker-run-action@v3
+        with:
+          image: ${{ matrix.docker }}
+          options: -v ${{ github.workspace }}:/build -w /build/bindings/node -e CARGO_TERM_COLOR=always
+          run: |
+            set -e
+            # 容器自带 Node 18, 而 @napi-rs/cli 的依赖树 (@inquirer/core) 已要求
+            # Node≥20 (styleText) 且 --no-save 无锁文件每次拉最新 — 曾于 2026-10-20
+            # 上游漂移打破构建。装固定版本的官方 musl Node, 消除漂移。
+            NODE_ARCH=$(uname -m); [ "$NODE_ARCH" = "x86_64" ] && NODE_ARCH=x64
+            NODE_VER=v22.14.0
+            wget -qO- "https://nodejs.org/dist/$NODE_VER/node-$NODE_VER-linux-$NODE_ARCH-musl.tar.xz" \
+              | tar xJ -C /usr/local --strip-components=1
+            node -v | grep -Eq '^v2[2-9]' || { echo "node upgrade failed: $(node -v)"; exit 1; }
+            rustup target add ${{ matrix.target }}
+            if [ "${{ matrix.target }}" = "aarch64-unknown-linux-musl" ]; then
+              # zstd-sys compiles C: point cc + the linker at the image's cross toolchain.
+              export CC_aarch64_unknown_linux_musl=aarch64-linux-musl-gcc
+              export CARGO_TARGET_AARCH64_UNKNOWN_LINUX_MUSL_LINKER=aarch64-linux-musl-gcc
+            fi
+            npm install --no-save @napi-rs/cli@3.10.8
+            npx napi build --release --platform --target ${{ matrix.target }} --js false --dts false
+            if [ "${{ matrix.target }}" = "x86_64-unknown-linux-musl" ]; then
+              node smoke_ci.js
+            fi
+
+      - name: Smoke (JS loader)
+        if: matrix.target == 'aarch64-apple-darwin' || matrix.target == 'x86_64-unknown-linux-gnu'
+        working-directory: bindings/node
+        shell: bash
+        # smoke_ci.js is committed (also reused by scripts/release_smoke.sh);
+        # it requires './index.js' FILE-relative, so run it from the package dir.
+        run: node smoke_ci.js
+
+      - name: Upload binding artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: bindings-${{ matrix.target }}
+          path: bindings/node/*.node
+          if-no-files-found: error
+
+  package:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+      - name: Install napi CLI
+        working-directory: bindings/node
+        run: npm install --no-save @napi-rs/cli@3.10.8
+      - name: Create npm dirs
+        working-directory: bindings/node
+        run: npx napi create-npm-dirs
+      - uses: actions/download-artifact@v4
+        with:
+          path: bindings/node/artifacts
+      - name: Place binaries into npm dirs
+        working-directory: bindings/node
+        shell: bash
+        # 🔑 Deterministic placement (napi artifacts misbehaves with
+        # cross-compiled targets): match each downloaded .node against the
+        # platform package's "main" field, copy, then verify completeness.
+        run: |
+          set -e
+          for d in artifacts/bindings-*; do
+            node_file=$(ls "$d"/*.node 2>/dev/null | head -1 || true)
+            [ -n "$node_file" ] || { echo "no .node in $d"; ls -la "$d"; exit 1; }
+            base=$(basename "$node_file")
+            placed=0
+            for pkg in npm/*/; do
+              main=$(jq -r .main "${pkg}package.json")
+              if [ "$main" = "$base" ]; then
+                cp "$node_file" "$pkg"
+                echo "placed $base -> $pkg"
+                placed=1
+              fi
+            done
+            [ "$placed" = 1 ] || { echo "no package wants $base"; exit 1; }
+          done
+          missing=0
+          for pkg in npm/*/; do
+            main=$(jq -r .main "${pkg}package.json")
+            [ -f "$pkg/$main" ] || { echo "MISSING $pkg/$main"; missing=1; }
+          done
+          [ "$missing" = 0 ] || exit 1
+          ls -R npm | head -40
+      - name: Dry-run publish (structure validation only)
+        if: ${{ !startsWith(github.ref, 'refs/tags/v') }}
+        working-directory: bindings/node
+        shell: bash
+        run: |
+          set -e
+          # pre-publish performs REAL npm publishes, so staging (PRs) only
+          # validates each platform package with npm publish --dry-run.
+          for d in npm/*/; do
+            (cd "$d" && npm publish --dry-run --access public) || exit 1
+          done
+          npm pack --dry-run
+
+  publish:
+    needs: [build, package]
+    # workflow_dispatch 允许在 npm 反垃圾拦截后从 main 手动慢速重发 (无需新标签)
+    if: startsWith(github.ref, 'refs/tags/v') || github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          registry-url: https://registry.npmjs.org
+      - name: Install napi CLI
+        working-directory: bindings/node
+        run: npm install --no-save @napi-rs/cli@3.10.8
+      - name: Create npm dirs
+        working-directory: bindings/node
+        run: npx napi create-npm-dirs
+      - uses: actions/download-artifact@v4
+        with:
+          path: bindings/node/artifacts
+      - name: Place binaries into npm dirs
+        working-directory: bindings/node
+        shell: bash
+        run: |
+          set -e
+          for d in artifacts/bindings-*; do
+            node_file=$(ls "$d"/*.node 2>/dev/null | head -1 || true)
+            [ -n "$node_file" ] || { echo "no .node in $d"; ls -la "$d"; exit 1; }
+            base=$(basename "$node_file")
+            placed=0
+            for pkg in npm/*/; do
+              main=$(jq -r .main "${pkg}package.json")
+              if [ "$main" = "$base" ]; then
+                cp "$node_file" "$pkg"
+                echo "placed $base -> $pkg"
+                placed=1
+              fi
+            done
+            [ "$placed" = 1 ] || { echo "no package wants $base"; exit 1; }
+          done
+          missing=0
+          for pkg in npm/*/; do
+            main=$(jq -r .main "${pkg}package.json")
+            [ -f "$pkg/$main" ] || { echo "MISSING $pkg/$main"; missing=1; }
+          done
+          [ "$missing" = 0 ] || exit 1
+      - name: Check NPM_TOKEN is configured
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          if [ -z "$NPM_TOKEN" ]; then
+            echo "::error::NPM_TOKEN repository secret is not set — cannot publish to npmjs.org. Create an automation token at https://www.npmjs.com/settings/~/tokens and add it under Settings → Secrets → Actions."
+            exit 1
+          fi
+      - name: Publish platform packages + root
+        # 🔑 Plain `npm publish` per package (platform packages first, then the
+        # root loader whose optionalDependencies point at them). Auth comes
+        # from setup-node's .npmrc + NODE_AUTH_TOKEN. `napi pre-publish` is
+        # deliberately NOT used: it assumes a GitHub release flow we don't run.
+        # Idempotent + burst-safe: skips versions already on the registry
+        # (EPUBLISHCONFLICT would otherwise abort the loop on re-runs) and
+        # paces publishes with escalating retries — npm's anti-spam
+        # heuristics reject rapid-fire new-package creation from new accounts
+        # (v0.15.1 tag run: the one brand-new platform package burned all 3
+        # fast retries; a cooldown + re-dispatch is the recovery path).
+        working-directory: bindings/node
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          set -e
+          pub() {
+            local d="$1" name ver try wait
+            name=$(jq -r .name "$d/package.json")
+            ver=$(jq -r .version "$d/package.json")
+            # Compare the PINNED version, not mere existence: after a version
+            # bump the old package is on npm but this version is not, and
+            # skipping would leave root's optionalDependencies pointing at a
+            # version that never ships (E404 for every consumer).
+            if npm view "$name@$ver" version >/dev/null 2>&1; then
+              echo "  $name@$ver already on npm — skip"; return 0
+            fi
+            # Escalating backoff: anti-spam blocks clear after a cooldown,
+            # not immediately — fast retries just burn the attempts.
+            for try in 1 2 3 4 5; do
+              echo "::group::publish $name@$ver (attempt $try)"
+              if (cd "$d" && npm publish --access public); then
+                echo "::endgroup::"; echo "  published $name@$ver"; return 0
+              fi
+              echo "::endgroup::"
+              [ "$try" = 5 ] && break
+              case "$try" in
+                1) wait=120 ;; 2) wait=300 ;; 3) wait=600 ;; *) wait=900 ;;
+              esac
+              echo "  retry in ${wait}s (npm anti-spam/rate heuristics)"; sleep "$wait"
+            done
+            echo "::error::gave up publishing $name@$ver after 5 attempts"
+            return 1
+          }
+          # 主包最优先 — 它是 `npm install motedb` 的入口; 平台包是
+          # optionalDependencies, 单个被 npm 反垃圾拦截不应拖死主包
+          # (失败让 job 标红以便跟踪, 但其余包继续发)。
+          pub . || exit 1
+          rc=0
+          for d in npm/*/; do pub "$d" || rc=1; sleep 120; done
+          exit $rc