fix: remaining-time in the Bambu Lab and Snapmaker side cards

Both cards showed "0m" next to the clock while the printers table showed the
right figure, for two different reasons — and one shared root cause: each card
derived the remaining time itself instead of reading the one the table uses.

- Bambu Lab: `mc_remaining_time` is MINUTES, fed straight into a seconds
  formatter, so a 32-minute job floored to 0. PROTOCOL.md documented the field
  as seconds — the source of the mistake — and is corrected.
- Snapmaker: the card printed `printDuration`, which is the time ELAPSED. It
  now reads the shared normalised job (new `ctx.getPrinterJob`) and shows "—"
  rather than a wrong "0m" when there is nothing to derive from yet.

Also: extend the on-demand test build to all three platforms (renamed
test-build-win.yml → test-build.yml, matrix, fail-fast off, 7-day artifacts)
and add the two missing `build:{mac,linux}:nopublish` scripts it needs.

Author: BenGlut

.github/workflows/test-build-win.yml

@@ -0,0 +1,101 @@
+name: Test build (all platforms)
+
+# On-demand build of all three platforms for handing a binary to a tester,
+# WITHOUT cutting a release: artifacts only — no git tag, no GitHub Release, no
+# auto-update feed, nothing published. Every binary is UNSIGNED:
+#   • Windows → SmartScreen warns ("More info" → "Run anyway")
+#   • macOS   → Gatekeeper blocks it (right-click → Open, or `xattr -dr
+#               com.apple.quarantine <app>`); it is NOT notarized
+#   • Linux   → AppImage, chmod +x and run
+#
+# Two ways to run it:
+#   • push any branch named  test/**  (this file must be on that branch)
+#   • Actions tab → "Test build (all platforms)" → Run workflow
+#
+# Native module note: nfc-pcsc is a C++ addon, so each platform MUST build on
+# its own runner — none of this can be cross-compiled.
+#
+# Artifacts are throwaway: 7-day retention, and delete them by hand once the
+# test is done rather than leaving installers lying around.
+
+on:
+  push:
+    branches:
+      - 'test/**'
+  workflow_dispatch: {}
+
+permissions:
+  contents: read
+
+# A second push to the same test branch supersedes the first — three full
+# Electron builds is not something to queue up twice by accident.
+concurrency:
+  group: test-build-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  build:
+    strategy:
+      # One platform failing must not cancel the other two — the whole point is
+      # to see which ones break.
+      fail-fast: false
+      matrix:
+        include:
+          - os: windows-latest
+            platform: win
+            artifact: TigerStudio-Windows-test
+            path: dist/*.exe
+          - os: macos-latest
+            platform: mac
+            artifact: TigerStudio-macOS-test
+            path: dist/*.dmg
+          - os: ubuntu-latest
+            platform: linux
+            artifact: TigerStudio-Linux-test
+            path: dist/*.AppImage
+
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: actions/setup-node@v5
+        with:
+          node-version: 24
+
+      # Same list as the release workflow — nfc-pcsc needs the PC/SC headers,
+      # and electron-builder needs the packaging tools.
+      - name: Install Linux system dependencies
+        if: matrix.os == 'ubuntu-latest'
+        run: |
+          sudo apt-get update -y
+          sudo apt-get install -y \
+            libpcsclite-dev \
+            libusb-1.0-0-dev \
+            libudev-dev \
+            build-essential \
+            python3 \
+            rpm \
+            fakeroot
+
+      - run: npm ci
+
+      - name: Build ${{ matrix.platform }} (unsigned, no publish)
+        run: npm run build:${{ matrix.platform }}:nopublish
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # Baked in so Google sign-in works in the test build.
+          TIGERTAG_GOOGLE_DESKTOP_CLIENT_ID: ${{ secrets.TIGERTAG_GOOGLE_DESKTOP_CLIENT_ID }}
+          TIGERTAG_GOOGLE_DESKTOP_CLIENT_SECRET: ${{ secrets.TIGERTAG_GOOGLE_DESKTOP_CLIENT_SECRET }}
+          # Belt and braces on macOS: without this electron-builder still hunts
+          # the keychain for an identity and can fail the build on a runner that
+          # has none, even with identity=null in the script.
+          CSC_IDENTITY_AUTO_DISCOVERY: false
+
+      - name: Upload ${{ matrix.platform }} artifact
+        uses: actions/upload-artifact@v5
+        with:
+          name: ${{ matrix.artifact }}
+          path: ${{ matrix.path }}
+          if-no-files-found: error
+          retention-days: 7

.github/workflows/test-build.yml

@@ -5,6 +5,18 @@
 ## Changed
 
 ## Fixed
+- Snapmaker printer side card showed "0m" next to the clock on a running print while the table
+  showed the real 21m — the card printed `printDuration`, which is the time ELAPSED, not remaining.
+  Moonraker sends no remaining time, so the card now reads the same normalised job the table does
+  (slicer estimate − elapsed, else extrapolated from progress) via a new `ctx.getPrinterJob`, and
+  shows "—" rather than a wrong "0m" while there is nothing to derive from yet —
+  `renderer/printers/snapmaker/cards.js`, `renderer/printers/context.js`, `renderer/inventory.js`
+- Bambu Lab printer side card showed "0m" remaining on a running print while the table column
+  showed the real figure. `mc_remaining_time` is reported in MINUTES, but the card fed it straight
+  into a seconds formatter, so a 32-minute job floored to 0. The table was right because it goes
+  through `_getPrinterJob`, which converts. `PROTOCOL.md` documented the field as seconds — the
+  source of the mistake — and is corrected with the observed value — `renderer/printers/bambulab/cards.js`,
+  `renderer/printers/bambulab/PROTOCOL.md`
 - Dependency refresh — 18 advisories (1 critical, 17 high) down to 0, entirely within the existing
   semver ranges: `package.json` is untouched, only the lockfile was stale. Covers the reported
   **CVE-2026-54673** / GHSA-p2f4-r6v6-j797 (`builder-util-runtime` 9.5.1 → 9.7.0 — electron-updater

WORKLOG.md

@@ -14,7 +14,9 @@
     "build:mac": "node scripts/gen-oauth-config.mjs && electron-builder --mac --publish always",
     "build:mac:local": "bash build/sign-and-notarize.sh",
     "build:mac:unsigned": "node scripts/gen-oauth-config.mjs && electron-builder --mac -c.mac.identity=null -c.mac.notarize=false",
+    "build:mac:nopublish": "node scripts/gen-oauth-config.mjs && electron-builder --mac -c.mac.identity=null -c.mac.notarize=false --publish never",
     "build:linux": "node scripts/gen-oauth-config.mjs && electron-builder --linux --publish always",
+    "build:linux:nopublish": "node scripts/gen-oauth-config.mjs && electron-builder --linux --publish never",
     "build:all": "node scripts/gen-oauth-config.mjs && electron-builder -wml --publish always",
     "i18n:add": "node scripts/i18n-add.mjs",
     "i18n:check": "node scripts/check-i18n-consistency.mjs",

package.json

@@ -23217,6 +23217,11 @@ import { elgFanStep } from './printers/elegoo/widget_control.js';
     toast: (msg, type) => toast(msg, type),
     isForcedOffline: (key) => _ppForcedOfflineKeys.has(key),
     snapFmtTempPair, snapFmtDuration, snapTextColor,
+    // One reading of the live job for both surfaces. The cards used to derive
+    // their own remaining time and drifted from the table (Snapmaker showed
+    // elapsed, Bambu read minutes as seconds) — deriving it twice is what
+    // caused both.
+    getPrinterJob: (p) => _getPrinterJob(p),
     findPrinterModel, printerImageUrl, printerImageUrlFor,
     snapFilenameRel,
     SNAP_ICON_NOZZLE, SNAP_ICON_BED, SNAP_ICON_CHAMBER, SNAP_ICON_CLOCK,

renderer/inventory.js

@@ -300,8 +300,8 @@ Tous les messages reçus sur `device/{serialNumber}/report` sont du JSON. La rac
     "gcode_state": "RUNNING",
     "mc_percent": 45,
     "mc_print_stage": 2,
-    "mc_remaining_time": 3600,
-    "remaining_time": 3600,
+    "mc_remaining_time": 32,
+    "remaining_time": 32,
     "layer_num": 120,
     "total_layer_num": 300,
     "subtask_name": "my_print.gcode",
@@ -374,8 +374,8 @@ Tous les messages reçus sur `device/{serialNumber}/report` sont du JSON. La rac
 | `status` | string | Alternative à `gcode_state` |
 | `mc_percent` | int/string | Progression 0–100 (%) |
 | `mc_print_stage` | int | Étape interne. `0` = pas d'impression en cours |
-| `mc_remaining_time` | int | Temps restant en secondes (alias de `remaining_time`) |
-| `remaining_time` | int | Temps restant en secondes |
+| `mc_remaining_time` | int | Temps restant en **MINUTES** (alias de `remaining_time`). Vérifié sur matériel réel : une impression à 32 min restantes envoie `32`, pas `1920`. Cette ligne annonçait des secondes et a produit un « 0m » dans la carte latérale (v2.19.1) — convertir en secondes avant tout formatage |
+| `remaining_time` | int | Temps restant en **minutes** (voir ci-dessus) |
 | `layer_num` | int | Couche actuelle |
 | `total_layer_num` | int | Nombre total de couches |
 | `subtask_name` | string | Nom du sous-job / fichier en cours |

renderer/printers/bambulab/PROTOCOL.md

@@ -26,7 +26,11 @@ export function renderBambuJobCard(p, conn) {
 
   const layerText = isActive && (d.layerNum || d.totalLayerNum)
     ? `${d.layerNum || 0}/${d.totalLayerNum || 0}` : "";
-  const timeText = isActive ? _bblFmtDuration(d.remainingTime) : "—";
+  // `remainingTime` is `mc_remaining_time`, which Bambu reports in MINUTES —
+  // the formatter takes seconds, so a 32-minute job read as 32 seconds and
+  // rendered "0m". (The table column got this right via _getPrinterJob, which
+  // is why the two views disagreed.)
+  const timeText = isActive ? _bblFmtDuration(d.remainingTime * 60) : "—";
   const stateLabel = ctx.t("snapState_" + state) || state;
 
   const nameLine = leafName

renderer/printers/bambulab/cards.js

@@ -20,6 +20,11 @@ export const ctx = {
   snapFmtDuration: s => `${Math.floor((s || 0) / 60)}m`,
   snapTextColor: () => "#fff",
 
+  // Normalised live job for a printer — the SAME reading the printers table
+  // uses (state, pct, remainSec…), so a card never has to re-derive it and
+  // drift from the table. Returns null when the printer isn't connected.
+  getPrinterJob: () => null,
+
   // Printer model helpers (read state.db.printerModels at call time)
   findPrinterModel: () => null,
   printerImageUrl: () => null,

renderer/printers/context.js

@@ -22,7 +22,13 @@ export function renderSnapJobCard(p, conn) {
   const thumbUrl  = ((isActive || isDone) && d.printPreviewUrl) ? d.printPreviewUrl : (fallbackImg || "");
   const layerText = isActive && (d.currentLayer || d.totalLayer)
                   ? `${d.currentLayer || 0}/${d.totalLayer || 0}` : "";
-  const durationText = isActive ? ctx.snapFmtDuration(d.printDuration) : "0m";
+  // Time REMAINING, like the printers table — this used to print `printDuration`,
+  // which is the time ELAPSED, so a job that had just started showed "0m" next to
+  // a clock while the table said 21m. Moonraker sends no remaining time, so the
+  // shared reading derives it (slicer estimate − elapsed, else extrapolated from
+  // progress); "—" while it has nothing to go on yet, never a wrong "0m".
+  const remainSec = ctx.getPrinterJob(p)?.remainSec;
+  const durationText = isActive ? (remainSec > 0 ? ctx.snapFmtDuration(remainSec) : "—") : "0m";
   const stateLabel  = ctx.t("snapState_" + jobState) || jobState;
   const isPaused    = jobState === "paused";
   const isPrinting  = jobState === "printing";