QQQ Print Agent v1.0.1

Windows x64 release of QQQ Print Agent for QQQ 4.1+. The MSI and the first-party service, companion and command-line binaries are Authenticode-signed with SHA256 and an RFC3161 timestamp by the project's Azure Artifact Signing publisher identity.

Verify the MSI against SHA256SUMS and its GitHub provenance attestation before installing; every asset was built and tested by this workflow after all security, CodeQL and script gates passed, and the checksums were generated after signing.

This client requires QQQ's semantic printing extension >=2.0.0 <3.0.0 and standard QQQ sign-in; selected-media jobs need printing 2.3+. Upgrade the server first. Existing pairings and history are preserved.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope, evidence and limitations. Spool acceptance alone does not establish physical output.

QQQ Print Agent v0.4.0-rc.4

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

This client requires QQQ's semantic printing extension >=2.0.0 <3.0.0 and standard QQQ sign-in. When upgrading from 0.2, upgrade the server first: native API 2.0 makes a synchronized authenticated WebSocket mandatory for claims. An existing 0.3 server remains compatible with this client follow-up. Existing pairings and history are preserved; unbound devices require explicit account association.

New in 0.4.0: optional printer-media selection and 4 x 2 / 4 x 1 test-label choices. Printer profiles describe configured defaults, not physical stock sensing; jobs refuse a selected profile whose revision has drifted. Each job writes a phase-timing log line. Ordered numeric executable versions allow normal upgrades between release candidates. Upgrade the server first for selected-media jobs. The local rc.3 build of the same printing runtime passed installation and the operator's 4 x 1 test; Letter and 4 x 6 output were previously accepted. Physical 4 x 2 testing is deferred. This remains an unsigned prerelease, with no GA or stable 1.0 claim.

New in 0.3.2: a successful MSI result is accepted only when app, service and CLI have the requested release and identical full build versions. Missing, unreadable or mixed builds report an inconsistent installation without claiming rollback. The SDK credit references Microsoft's separate terms and installed notices. The native test host now matches production's PerMonitorV2 DPI declaration while retaining unelevated execution.

New in 0.3.1: the footer shows explicit WebSocket state, a server-settings link, live QQQ service upload/download payload rates and totals since service start. Lightweight local observations add no QQQ job/control polling. Windows-normalized startup account names are accepted only when they resolve to the exact expected SID; this preference controls the tray companion, independently of the automatic print service.

Known issue: a post-print native LayoutCycleException was observed in the 0.3.0 companion. The original trigger remains unreproduced despite nonprinting native geometry/dialog/refresh tests. This follow-up logs that exact fatal exception and permits normal WinUI termination rather than leaving an input-dead window; the service continues and the operator can reopen the companion. This is mitigation, not an underlying layout fix. Actual fatal handling and natural termination were verified with an intentionally cycling native Panel in an isolated nonprinting host; that test does not reproduce the original post-print trigger.

New in 0.3: persistent outbound authenticated WSS carries controls, commands, receipts, status and job notifications, with no job/control polling or fallback. Documents stream separately over same-origin HTTPS into protected staging. Administrator settings bound document size, copies, aggregate bandwidth, staging, queues, concurrency, liveness and timeouts; defaults include 100 MiB PDF, 20 MiB ZPL and one download/print lane. Durable reconnect reconciliation preserves receipts and prevents blind resubmission of uncertain jobs. The Jobs view adds inline expansion and actions with sortable, bounded history.

Existing features include standard QQQ sign-in and protected service sessions, PDF/ZPL printing and warehouse diagnostic profiles, exact owned spool cancellation, synchronized device/printer profiles, configurable logs, customer branding, AppKit settings/logs/update prompts, machine-wide MSI updates, tray status and explicit printer exposure. Replacement pairing and recovery from damaged saved credentials preserve history and printer choices without silently enabling printing.

The published 0.3.2 MSI was reached by a real in-app update from 0.3.1 with pairing, printer profiles and local receipts preserved, and its service restored the native QQQ session and WebSocket. The operator confirmed successful test prints on 0.3.1. Configured provider/browser callbacks also need end-to-end qualification against a compatible native-session API. See docs/ACCEPTANCE.md for version-specific evidence and remaining limits. Spool acceptance alone does not establish physical output or scanner readability; no stable 1.0 readiness is claimed.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.3.2-rc.1

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

This client requires QQQ's semantic printing extension >=2.0.0 <3.0.0 and standard QQQ sign-in. When upgrading from 0.2, upgrade the server first: native API 2.0 makes a synchronized authenticated WebSocket mandatory for claims. An existing 0.3 server remains compatible with this client follow-up. Existing pairings and history are preserved; unbound devices require explicit account association.

New in 0.3.2: a successful MSI result is accepted only when app, service and CLI have the requested release and identical full build versions. Missing, unreadable or mixed builds report an inconsistent installation without claiming rollback. The SDK credit references Microsoft's separate terms and installed notices. The native test host now matches production's PerMonitorV2 DPI declaration while retaining unelevated execution.

New in 0.3.1: the footer shows explicit WebSocket state, a server-settings link, live QQQ service upload/download payload rates and totals since service start. Lightweight local observations add no QQQ job/control polling. Windows-normalized startup account names are accepted only when they resolve to the exact expected SID; this preference controls the tray companion, independently of the automatic print service.

Known issue: a post-print native LayoutCycleException was observed in the 0.3.0 companion. The original trigger remains unreproduced despite nonprinting native geometry/dialog/refresh tests. This follow-up logs that exact fatal exception and permits normal WinUI termination rather than leaving an input-dead window; the service continues and the operator can reopen the companion. This is mitigation, not an underlying layout fix. Actual fatal handling and natural termination were verified with an intentionally cycling native Panel in an isolated nonprinting host; that test does not reproduce the original post-print trigger.

New in 0.3: persistent outbound authenticated WSS carries controls, commands, receipts, status and job notifications, with no job/control polling or fallback. Documents stream separately over same-origin HTTPS into protected staging. Administrator settings bound document size, copies, aggregate bandwidth, staging, queues, concurrency, liveness and timeouts; defaults include 100 MiB PDF, 20 MiB ZPL and one download/print lane. Durable reconnect reconciliation preserves receipts and prevents blind resubmission of uncertain jobs. The Jobs view adds inline expansion and actions with sortable, bounded history.

Existing features include standard QQQ sign-in and protected service sessions, PDF/ZPL printing and warehouse diagnostic profiles, exact owned spool cancellation, synchronized device/printer profiles, configurable logs, customer branding, AppKit settings/logs/update prompts, machine-wide MSI updates, tray status and explicit printer exposure. Replacement pairing and recovery from damaged saved credentials preserve history and printer choices without silently enabling printing.

The published 0.3.1 MSI was installed with pairing, printer profiles, local receipts and log settings preserved; its service automatically restored the native QQQ session and WebSocket. The operator confirmed successful test prints and a responsive window. This 0.3.2 candidate still needs actual in-app update acceptance. Configured provider/browser callbacks also need end-to-end qualification against a compatible native-session API. See docs/ACCEPTANCE.md for version-specific evidence and remaining limits. Spool acceptance alone does not establish physical output or scanner readability; no stable 1.0 readiness is claimed.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.3.1-rc.1

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

This client requires QQQ's semantic printing extension >=2.0.0 <3.0.0 and standard QQQ sign-in. When upgrading from 0.2, upgrade the server first: native API 2.0 makes a synchronized authenticated WebSocket mandatory for claims. An existing 0.3 server remains compatible with this client follow-up. Existing pairings and history are preserved; unbound devices require explicit account association.

New in 0.3.1: the footer shows explicit WebSocket state, a server-settings link, live QQQ service upload/download payload rates and totals since service start. Lightweight local observations add no QQQ job/control polling. Windows-normalized startup account names are accepted only when they resolve to the exact expected SID; this preference controls the tray companion, independently of the automatic print service.

Known issue: a post-print native LayoutCycleException was observed in the 0.3.0 companion. The original trigger remains unreproduced despite nonprinting native geometry/dialog/refresh tests. This follow-up logs that exact fatal exception and permits normal WinUI termination rather than leaving an input-dead window; the service continues and the operator can reopen the companion. This is mitigation, not an underlying layout fix. Actual fatal handling and natural termination were verified with an intentionally cycling native Panel in an isolated nonprinting host; that test does not reproduce the original post-print trigger.

New in 0.3: persistent outbound authenticated WSS carries controls, commands, receipts, status and job notifications, with no job/control polling or fallback. Documents stream separately over same-origin HTTPS into protected staging. Administrator settings bound document size, copies, aggregate bandwidth, staging, queues, concurrency, liveness and timeouts; defaults include 100 MiB PDF, 20 MiB ZPL and one download/print lane. Durable reconnect reconciliation preserves receipts and prevents blind resubmission of uncertain jobs. The Jobs view adds inline expansion and actions with sortable, bounded history.

Existing features include standard QQQ sign-in and protected service sessions, PDF/ZPL printing and warehouse diagnostic profiles, exact owned spool cancellation, synchronized device/printer profiles, configurable logs, customer branding, AppKit settings/logs/update prompts, machine-wide MSI updates, tray status and explicit printer exposure. Replacement pairing and recovery from damaged saved credentials preserve history and printer choices without silently enabling printing.

The published 0.3.0 local cohort passed state preservation and service restart/restoration checks, with fresh laser PDF and Zebra ZPL spool receipts. This 0.3.1 client still requires its own installed UI and physical-output acceptance. Configured authentication providers and installed browser callbacks also require end-to-end qualification, including provider renewal and permissions deployment. Source tests do not establish those outcomes. See docs/ACCEPTANCE.md for version-specific evidence and remaining limits. Spool acceptance alone does not establish physical output or scanner readability; no stable 1.0 readiness is claimed.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.3.0-rc.1

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

Upgrade the server first: this client requires QQQ's semantic printing extension >=2.0.0 <3.0.0 and standard QQQ sign-in. Native API 2.0 makes a synchronized authenticated WebSocket mandatory for claims, so coordinate the server and Windows upgrade. Existing pairings and history are preserved; unbound devices require explicit account association.

New in 0.3: persistent outbound authenticated WSS carries controls, commands, receipts, status and job notifications, with no job/control polling or fallback. Documents stream separately over same-origin HTTPS into protected staging. Administrator settings bound document size, copies, aggregate bandwidth, staging, queues, concurrency, liveness and timeouts; defaults include 100 MiB PDF, 20 MiB ZPL and one download/print lane. Durable reconnect reconciliation preserves receipts and prevents blind resubmission of uncertain jobs. The Jobs view adds inline expansion and actions with sortable, bounded history.

Existing features include standard QQQ sign-in and protected service sessions, PDF/ZPL printing and warehouse diagnostic profiles, exact owned spool cancellation, synchronized device/printer profiles, configurable logs, customer branding, AppKit settings/logs/update prompts, machine-wide MSI updates, tray status and explicit printer exposure. Replacement pairing and recovery from damaged saved credentials preserve history and printer choices without silently enabling printing.

Installed 0.3 behavior and physical output require separate acceptance; prior 0.2 output confirmation does not qualify this release. Configured authentication providers and installed browser callbacks also require end-to-end qualification, including provider renewal and permissions deployment. Source tests do not establish those outcomes. See docs/ACCEPTANCE.md for version-specific evidence and remaining limits. Spool acceptance alone does not establish physical output or scanner readability; no stable 1.0 readiness is claimed.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.2.0-rc.1

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

Upgrade the server first: this client requires QQQ's semantic printing extension and standard QQQ sign-in. Older bearer-only servers must be upgraded. Existing pairings and history are preserved; unbound devices require explicit account association.

New features: semantic capability discovery, standard table-based or explicitly advertised native browser authentication, DPAPI-protected service sessions and QQQ session resume. Independent device-control polling supports durable pause/disconnect/reconnect state and command receipts, with cancellation limited to the exact owned spool job. Normal CLI operations use the authenticated service; direct legacy diagnostics require an explicit compatibility flag. Explicit replacement pairing and recovery from damaged saved credentials preserve history and printer choices without silently enabling printing.

Existing features include PDF/ZPL printing and warehouse diagnostic profiles, sortable printer/job tables, bounded searchable history, synchronized device/printer profiles, configurable logs, customer branding, AppKit settings/logs/update prompts, machine-wide MSI updates, tray status and explicit printer exposure.

Configured authentication providers and installed browser callbacks still require end-to-end qualification, including provider renewal and permissions deployment. Source tests do not establish those outcomes. See docs/ACCEPTANCE.md for version-specific installed checks, physical-output confirmation and remaining limits. Spool acceptance alone does not establish physical output or scanner readability; no stable 1.0 readiness is claimed.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.1.9-rc.1

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

Features: QQQ-branded warehouse diagnostic documents with native Letter/A4/4 × 6-inch PDF and 203/300/600-dpi ZPL profile choices, label-aware defaults with operator resolution verification, sortable printer and job tables, inline printer details, double-click settings and job dialogs, bounded history pages with creation-time ordering, synchronized computer/printer profiles, daily log limits and clearing, same-installer customer branding, native Windows navigation, AppKit logs/settings/update prompts, verified machine-wide MSI updates, tray status, explicit printer exposure, reconnect and service controls, searchable job history with test/retry/cancel/review actions, bounded printer workers, outbound cloud polling, PDF and ZPL spool submission, durable receipts and protected service credentials. See docs/ACCEPTANCE.md for version-specific installed checks, diagnostic spool submissions, physical-output confirmation and remaining qualification limits. Spool acceptance alone does not establish physical output or scanner readability.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.1.7-rc.1

QQQ Print Agent 0.1.7 adds QQQ-branded warehouse diagnostic pages and labels for QQQ 4.1+ with qbit-printing 0.1.3-rc.1 or later.

• Shared QQQ logo and JetBrains Mono Bold with a dotted zero and distinct 1/I/l glyphs across PDF and ZPL.
• Native format and stock choices: Letter, A4 and 4 × 6-inch PDF; 4 × 6-inch ZPL at 203, 300 or 600 dpi.
• Label-aware format defaults, explicit resolution confirmation, alignment/scale checks and a Code 128 barcode on the ZPL diagnostic.

Validation: 227 unit/regression tests, zero build warnings/errors, all 16 installed UI checks in one run, and passing tagged CI/package workflow. The installed upgrade retained pairing and configuration. The user confirmed laser PDF output and Zebra ZPL output. The Zebra PDF initially failed to produce a label because the machine driver defaults were 4.09 × 2 inches and Thermal Transfer; after correcting them to 4 × 6 inches and Thermal Direct, a fresh PDF test printed correctly and was confirmed by the user. Barcode scanning and measured alignment remain unverified. This is local end-to-end evidence, not remote production deployment qualification.

For ribbon-free Zebra printers, configure Printer properties → Advanced → Printing Defaults for the actual stock and Thermal Direct. The Windows service uses machine defaults; per-user Printing Preferences may differ. A spooler acknowledgment alone does not prove physical output.

The MSI is unsigned. Verify downloaded assets against SHA256SUMS. Customer branding uses the accompanying Install-Branded.ps1 and branding.example.json without a custom build. Existing tables, tray/status, AppKit menus/logs/settings/update prompts and printer/job controls remain included.

See installation, user guide, and acceptance evidence.

QQQ Print Agent v0.1.6-rc.1

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

Features: sortable printer and job tables, inline printer details, double-click settings and job dialogs, bounded history pages with creation-time ordering, synchronized computer/printer profiles, daily log limits and clearing, same-installer customer branding, native Windows navigation, AppKit logs/settings/update prompts, verified machine-wide MSI updates, tray status, explicit printer exposure, reconnect and service controls, searchable job history with test/retry/cancel/review actions, bounded printer workers, outbound cloud polling, PDF and ZPL spool submission, durable receipts and protected service credentials. Laser output was confirmed on earlier development builds; current installed acceptance is recorded in docs/FUNCTIONAL-AUDIT.md and docs/APPKIT-PARITY.md. Zebra qualification remains pending.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.

QQQ Print Agent v0.1.0-rc.1

Known issue: the desktop companion in this MSI fails to open because generated WinUI resources are missing from the package. A corrective prerelease is being prepared. Build/unit-test success did not cover this packaged-app startup failure.

This is an unsigned Windows x64 prerelease of QQQ Print Agent for QQQ 4.1+.

Assets were built and tested by this workflow. Verify the MSI against SHA256SUMS before installing. No Authenticode signature or production qualification is claimed.

Features: AppKit setup and tray status, explicit printer exposure, outbound cloud polling, PDF and ZPL spool submission, durable local receipts and protected service credentials. Physical laser acceptance passed locally; Zebra hardware qualification remains pending.

See CHANGELOG.md, docs/INSTALLATION.md and docs/ACCEPTANCE.md in the tagged source for scope and limitations.