Verified tests & release status
Status recorded: 30 October 2026
This page records what was actually observed , not an unsupported claim of full product certification. The current test candidate is DirectSpool v0.77.3 ; the JavaScript/TypeScript SDK is v0.77.3-rc.1 .
Test results and evidence limits
| Milestone | Result | What was verified / limitation |
|---|---|---|
| Windows x64 v0.77.3 Rust build / source QA | PASS — selected development environment | Static executable; formatting, tests and Clippy checks passed. Does not certify a signed consumer installer. |
| Tray icon embedded / Explorer recovery | PASS — Windows QA | Custom icon shown without external sidecar and recovered after Windows Explorer restart. |
| Disposable Windows Sandbox installer lifecycle | PASS — TEST-ONLY | Installation, app start, local status and uninstall observed on Windows Sandbox. Physical Windows 10 and production installer not certified. |
| Upgrade v0.76.0 → v0.77.3: device configuration | PASS — isolated dummy device | A no-hardware registered dummy device survived the same-AppId QA upgrade; nonproduction profile only. |
| Upgrade v0.76.0 → v0.77.3: pairing/trusted-origin config | PASS — exact fingerprints | v3 Before/Ready/After: one trusted origin and one paired client, with unchanged config fingerprints and no registered devices. |
| Original pre-upgrade pairing token authentication | NOT YET VERIFIED | Preserved configuration fingerprints do not alone prove the original token continues to authenticate. |
| SDK Linux and Windows Actions | PASS — pre-release SDK | Syntax, unit/regression and package-file allowlist checks passed in the private repository. |
| Chrome: public HTTPS origin → loopback agent | PASS — Windows Sandbox | https://directspool.com paired to http://127.0.0.1:9108; claim, authenticated read-only list_devices and status succeeded; zero devices. |
| Microsoft Edge: public HTTPS origin → loopback | PASS — Windows Sandbox | Pairing claim and authenticated list_devices succeeded; zero devices; no printing. |
| Edge: Apps on device / loopback permission BLOCK | PASS — browser restriction | Site permission reported denied; browser rejected loopback pairing request. No bypass observed. |
| Firefox local SDK authorization | PASS — limited local QA | Local pairing and authenticated list_devices tested; external HTTPS-to-loopback and denied-permission matrix not yet certified. |
| Physical receipt output | PASS — one earlier selected test | Prior physical multi-line 58 mm ESC/POS output observed on ZY302. Not universal hardware or customer-site acceptance. |
| Device- and capability-scoped permission audit | OPEN | The zero-device read-only browser tests did not certify least-privilege device rights; broad default capability display requires review. |
| Signed Windows production installer | OPEN | Authenticode signing, installer provenance, rollback and release security gate remain. |
| Physical Windows 10 acceptance / broad printer matrix | OPEN | Physical Windows 10 x64 install, authorized old-token use, real printer/driver coverage and representative device workflows remain. |
Release boundary
Tests used disposable QA profiles and Windows Sandbox. No production customers or working-PC installations were modified by these checks. Browser integration tests were read-only and did not send print commands.
Private source and compliance
The private SDK GitHub repository contains the staged JavaScript/TypeScript candidate and CI. The proprietary Rust Core, Business Cloud services, signing certificates, credentials, pairing records and customer files are not approved for publication. A passing browser test does not replace security review, release signing or compliance work.