qbit-printing/docs/TODO.md

Follow-up

Script quality gates

• Pin Ruff and strict Pyright with a locked restore; reject Python outside .github/scripts/ and zero-file Pyright runs; negative tool probes pass locally.
• Observe the new verify job steps pass on hosted CI before relying on them.

Echo integration candidate

• Implement authorized operator catalog, native submission/process permission, exact actor/request lookup and reported driver-default media revisions.
• Integrate the opt-in atomic retained-source facade using the same queue, current authority, immutable acceptance and exact device-event observation.
• Close native callback authority changes and preserve the exact accepted printer-row identity during read-only request reconciliation.
• Complete local combined verification on the merged 2.3.0 candidate: 189 reported, 188 executed, one opt-in workload skip, zero failures/errors and Checkstyle violations (the earlier 183-test gate was pre-merge). Preserve exact source, draft protocol fixtures and frozen runtime hashes.
• Pass hosted CI on the final signed candidate head; local results do not replace it.
• Qualify Echo/Generation's exact core tuple and configured source authority; do not silently adopt experimental core or bypass external-upload admission.
• Publish the reviewed additive contract and coordinate client/runtime adoption before owner-operated end-to-end physical acceptance.

Current local development qualification

• Reuse production discovery and the shared major-2 gate in the optional native-auth probe; reproduce the old 2.1.0 rejection, then pass 12 native and nine default workload fake-HTTP compatibility checks without provider launch.
• Rerun the eight-check native provider profile once against printing API 2.1.0 after review; all eight passed with unchanged source hashes and owned cleanup.
• Supply portable, owned Docker Start/Test/Stop commands with private synthetic credentials and explicit cleanup; leave the installed pairing untouched.
• Run the 40-job smoke, 65 real S3 backend checks and 10,000 network jobs with 30,000 durable server receipts and replay/isolation assertions.
• Qualify real Authentik provider discovery and registered/unregistered redirect controls while reporting the released QQQ 1.8 native-grant absence honestly.
• Qualify the separate experimental API 1.9/container-TLS native login, denied-user/wrong-Origin permissions, logout, short renewal and provider revocation.
• Include the opt-in 10,000-job pooled-SQL/cold-reopen service regression and preserve separate released-artifact network/idle-latency evidence.
• Publish developer tooling through PR #21, merged as 3592decba8087439aff5d1b75a9726c72f460cb9: hosted 40-job/65-S3 checks, 33 script tests on both Windows and Ubuntu, and the ordinary Java gate (133 reported, 132 executed, one opt-in skip, zero failures/Checkstyle violations). Keep experimental API 1.9 artifacts opt-in; this merge does not adopt them into the released application or upgrade the live paired runtime.

The older release checklists below are historical context. AWS/cloud-account provisioning is outside the user's current local-Docker-only request.

• Complete native device controls, per-record/selection actions, queue/history, dashboard and legacy-boundary integration tests; 110 tests pass with zero Checkstyle violations.

• Complete 25 actual Windows Core client/native QQQ interoperability checks with table-based authentication, no printers and no jobs.

• Complete installed candidate acceptance after protected CI.

• Complete standard QQQ discovery/session/device-binding security checks and Windows auth integration; qualify the shared Authentik native grant without a private authentication fork.

• Review and merge immutable protocol inputs (cc3c4e5), pass protected CI and merge the server and Windows implementations normally. Release tagging and installed acceptance remain separate.

• Replace the test-document logo with the exact official Query dog asset; preserve aspect ratio and verify all PDF/thermal profiles with 73 passing tests, zero Checkstyle violations and reviewed previews.

• Publish v0.1.4-rc.1 after all required release gates, verify checksums and all three asset attestations, and complete local native deployment acceptance.

• Obtain user confirmation for all three updated Query diagnostic documents (Letter PDF, Zebra ZPL and Zebra PDF).

• Correct S3 layout and multiline-prefix binding ambiguity; full isolated gate passes 72 tests with zero Checkstyle violations and independent review complete.

• Reproduce the actual Windows-to-Linux false-expiration defect, then qualify the corrected runtime: zero SDK requests for refused reads/retries/cleanup and preserved objects, availability and accounting.

• Pass fresh hosted gates for the S3 correction and approved scoped H2 input; verify exact CI artifacts, all 47 archive payloads and 204 runtime coordinates. Portable upstream keys, historical migration and production IAM remain separate qualification work.

• Verify the H2 2.4.240 candidate at fb99faf: 67 Java tests, zero Checkstyle violations, hosted build/CodeQL/security pass, and all 204 selected runtime dependencies verified.

• Qualify the exact CI artifact on an isolated closed-data copy: native frontend/authentication/query/denial/logout/retention checks, actual scheduled zero-removal tick, forced termination, read-only inspection before initialization, and successful cold restart; all 11 tables and retained state preserved.

• Add the exact reviewed H2 version guard and license attribution/evidence; 17 Python guard tests and workflow lint pass.

• Approve central H2 metadata record EX-0013 through standards PR #54, apply only its package-scoped workflow input and pass every fresh required check.

• Qualify registered JVM-hook shutdown on exact 00dd2dd: native acceptance, Quartz/HTTP shutdown, exit 0 and independent read-only cold inspection before initialization pass. Windows reboot/service-manager behavior remains separate.

• Complete local paired-host acceptance after verified recovery backups and fresh required gates; preserve pairing and history. Native authentication/query/denial/logout, automatic connector reconnection and 365-day retention checks pass.

• Finish audit regressions for native-process replay, strict options/inventory validation, retained duplicate risk and event field bounds; full gate passes 53 tests.

• Implement admin-configurable document retention (one-year default), bounded scheduled cleanup and existing QQQ object-storage integration, retaining history/receipts and protecting active or uncertain output.

• Implement the optional Record Files adapter against its verified frozen contract: durable accepted-source/actor binding, legitimate current reporting identity and committed observation receipt. Adapter remains disabled; standalone printing does not depend on it.

• Verify v0.1.4-rc.1 release run 41190650664, published JAR/POM/SHA256SUMS provenance and local native deployment acceptance.

• Historical audit PR #10 checkpoint aeac1a6 passed hosted checks; current H2/native qualification and remaining license gate are recorded above.

• Complete the independent baseline scan and current-source reviews of all five findings and remediations.

• Add authenticated native QQQ local host sharing paired data with device routes and the existing scheduler; 65 tests/zero Checkstyle pass and independent source review found no blocker.

• Complete live authenticated local-host deployment after isolated native and graceful/cold-copy acceptance; remote/S3 qualification remains separate under the user's local-first instruction.

• Versioned shared contract and HTTP happy-path test.

• Durable enrollment, device-scoped authentication, inventory and printer approval.

• PDF/ZPL queue, idempotency, content integrity and status events.

• QQQ metadata and native enrollment/enable/test-print processes.

• Durable enqueue EffectTarget for QQQ workflows.

• Verify local laser output from connector and installed LocalSystem service; user confirmed both pages.

• Confirm physical built-in ZPL and PDF output on the connected Zebra; scanning and measured alignment remain separate checks below.

• Add separate synthetic native QQQ frontend preview host.

• Replace identifier text inputs with tenant-scoped, device-dependent selectors and add table/record actions.

• Qualify authenticated local QQQ host integration with preserved pairing/history and native retention scheduling.

• Qualify remote QQQ host deployment and production authentication/facility policy.

• Separate local printer availability from server approval and block withdrawn queues.

• Prepare public repository documentation, license, CI and GitHub prerelease artifacts.

• Verify remote CI/security and publish v0.1.0-rc.1 JAR/POM/checksum assets.

• Client-owned device/printer name, description and location synchronized into native QQQ metadata.

• Implement the dedicated QQQ object-storage document backend; live S3/IAM qualification remains pending configuration.

• Logical destination mappings.

• Run the coordinated Java gate for profile migration, long text and 10,000-row bounded-history regressions; included in the passing 28-test v0.1.3-rc.1 gate.

• Qualify long-duration soak and sustained physical throughput separately from the completed bounded network/fake-printer workloads; see qualification evidence.

• Device-scoped test/retry/cancel/queued-job routes and native record/table cancellation/reprint review, explicit duplicate-risk consent and retry idempotency.

• Implement admin document retention and bounded scheduled cleanup, default 365 days.

• Server-side job expiry and operational alerts.

• PostgreSQL integration and multi-node stress tests; migration/version management.

• Resolve upstream/cached qbit-build-parent interpolation warning for Maven 3.10.

• Add native Printing home with scoped operational widgets and actionable links.

• Complete dashboard-standard live attention, URL scope, stale/retry and responsive/accessibility acceptance.

Historical 0.1.1-rc.1 integration checkpoint

• Verify current Java source: 19 tests passed, zero Checkstyle violations.
• Preserve job outcome while retry creates a new job; reject cancellation after claim.
• Expose cloud-queued jobs to the companion for visibility/cancellation before local receipt.

The Windows gate, MSI rebuild, installed UI acceptance, release evidence and fresh hardware submissions pending at this historical checkpoint are superseded by the newer records below and the Windows acceptance notes. Zebra is connected and both label format paths are physically confirmed.

• Qualify reboot/sign-in/service recovery and deployed-host behavior; no source-only or synthetic result substitutes for those checks.

v0.1.3-rc.1 diagnostic documents

• Share branded diagnostic generators and explicit stock/resolution profiles across native QQQ and device test-print entrypoints.

• Verify source a6266fe: full Maven gate passed 28 tests with zero Checkstyle violations; exact-source build, CodeQL and security workflows passed.

• Publish v0.1.3-rc.1 and verify its public JAR, POM and SHA256SUMS assets.

• Installed Windows 0.1.7 passed all 16 UI checks; reviewed built-in preview bytes matched the three submitted documents.

• Submit one Letter PDF to the laser, one 4 × 6-inch 300 dpi ZPL and one matching PDF to the Zebra through the installed pipe/device API/shared generator; all reached SPOOLED with the original paired database retained.

• User confirmed the Letter laser page and the Zebra label containing the barcode, identifying the latter as the built-in ZPL output.

• Correct the Zebra machine driver defaults from 4.09 × 2-inch Thermal Transfer to 4 × 6-inch Thermal Direct, restore/resume the printer, and confirm one fresh built-in PDF printed correctly. No application code fix was needed.

• Verify published Windows 0.1.7 assets; all three built-in physical paths are confirmed: laser PDF, Zebra ZPL and Zebra PDF.

• Obtain explicit barcode scan and measured alignment confirmation; successful spooling is not physical acceptance.

• Complete independent review after the five baseline security findings are remediated; current details are in SESSION-STATE.md.

• Complete remote deployment and production S3/IAM qualification; local native acceptance and isolated storage tests do not establish these.

Real-time upgrade (active)

• Complete authenticated outbound WebSocket transport and automatic durable recovery; remove production job/control polling fallback.
• Verify concurrent control while large streamed documents download, bounds/cleanup, real concurrency and exact event replay.
• Verify native administrator limits forms, live policy delivery, admission overrides and configurable document sizes.
• Complete consistent sortable/expandable Windows Jobs and Printers tables.
• Run coordinated server/client/protocol gates and cross-runtime native integration before packaging/installing.