61 Commits

Include renames

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	1bf13be26e	feat: operators read print jobs; retire the Remove actions; plain refusal messages ... Operators read print jobs, read only. PrintingReadPermission accepted printing_operator for print stations and printers and required printing_admin for print jobs, so a person who prints could not see what was printed. A holder of printing_operator now has every read shape on printing_job that an administrator has (query, get, count, aggregate, export) and sees every job of the tenant, with the same fields; the table has no field for the document, its storage reference or the retained binding. Control history and deletion history stay administrator-only and nobody gains a write. Retire the Remove actions. Delete (RC.3) keeps job history and records who deleted what, so the older archive actions duplicated it on the screens. Removed: the processes printingRemoveDevices and printingRemoveSelectedPrinters and the control action Action.REMOVE. No HTTP or agent route called them; the REVOKE control still resolves to printingRevokeDevices. PrintingService.removePrinter and removeDevice stay as service methods, and records archived earlier behave as before. Refusals say what happened and what to do, and name no framework. The permission checks, the 403 text of the native and legacy routes, the control-action sign-in text and the OpenAPI descriptions are reworded; statuses, error codes and JSON field names are unchanged. A host may give its application's display name with PrintingQBitConfig.withProductName; the default is "this application". Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-13 08:15:30 -06:00
james.maesandClaude Fable 5.2	7ac849d09f	feat(admin): delete print stations and printers; "Print station"; an aggregate is a read ... Delete print stations (printingDeleteDevices) and Delete printers (printingDeleteSelectedPrinters), on a selection and on the record screen, behind a new permission, printing_delete, required in addition to printing_admin. A station is revoked through the existing REVOKE control, then its queued jobs are canceled, jobs sent without a reported result are closed as OUTCOME_UNKNOWN, and its control receipts, printers and row are deleted in one transaction. A station or printer that is connected and printing is refused by name; the rest of the selection is still deleted. Jobs are never deleted. printing_job gains device_name, computer_name, printer_name and queue_name (the names at submission), keeps device_id, printer_id and printer_row_id as the identifiers the records had, and loses its foreign key to printing_device. printing_deletion records who deleted what, when and what went with it (table Deletion history). A computer enrolled again is a new station; a queue shared again is a new printer awaiting approval. Labels: "Print device" becomes "Print station" everywhere an administrator reads it, from one place (PrintingNames). Table, field and process names, the HTTP API texts and the agent protocol are unchanged. PrintingReadPermission refused an aggregate (and an export) as a write, for everybody. Both are reads and now need exactly the permission a query needs. Schema step for hosts that own the schema is in CHANGELOG.md. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-11 12:57:43 -06:00
james.maesandClaude Fable 5.1	c2f6fc300a	docs(release): record QQQ Printing 1.1.2 as the current stable library ... 1.1.2 = the 1.1.1 code on QQQ 4.1.0-RC.22 from the Gitea registry, built and published by the shared ci-workflows pipeline (push build 6435, tag build 6475). README, RELEASES, REALTIME and SESSION-STATE point at it with the verified hashes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 14:45:40 -06:00
james.maesandClaude Fable 5.1	c31a8f5f33	docs: frontend-next 1.0.0-RC.37 is served from the Gitea registry ... Mirrored byte-for-byte from Maven Central (verified against Central's SHA-1 and read back from the registry), so the ui-demo profile resolves from Gitea too. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 13:32:16 -06:00
james.maesandClaude Fable 5.1	3c39a6af1b	build: QQQ 4.1.0-RC.22 from the Gitea registry; shared ci-workflows Maven pipeline; 1.1.2 ... Everything moves to the QRun-IO Gitea Maven registry. QQQ 4.1.0-RC.22 exists only there, and the protected qrun-release channel resolves only Maven Central, so the repository now builds on the shared KofTwentyTwo/ci-workflows maven workflow (@v1): every push runs -Pui-demo verify against the registry with the job token; a vX.Y.Z tag tests once and deploys the JAR/POM under that version. The qrun-release caller and its trusted-publisher path are retired for this repository; PrintingContractTest keeps using the vendored protocol fixtures. No printing contract change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 13:32:15 -06:00
james.maesandClaude Fable 5.1	f10cc03d9e	docs(release): record QQQ Printing 1.1.1 as the current stable library ... README, RELEASES, REALTIME and SESSION-STATE now point at 1.1.1 (source 2a56181, main run 5976, reactor artifact 4426, release 1381) with the verified JAR/POM hashes, and mark 1.1.0 as superseded by the realtime upgrade header-case fix. The release caller is untouched, so the publisher enrollment hash stays valid. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 10:33:25 -06:00
james.maesandClaude Fable 5.1	e7721bdf90	fix(realtime): resolve the device on the authorized upgrade so lowercase headers connect; 1.1.1 ... The WebSocket callbacks read X-QQQ-Device-Id from the socket context, whose header lookup is case-sensitive, while the HTTP upgrade matches names case-insensitively. Behind an ingress that lowercases header names the device resolved to null on connect and channels.put threw before WELCOME (Forge's adoption test of released 1.1.0; Forge had carried a local patch on 1.0.0). Resolve the device once after authorization on the upgrade and carry it as a connection attribute for connect, message and close. The new lowercaseUpgradeHeadersReachWelcomeAndFrames test fails on the previous code with the same NullPointerException and passes here. No contract change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 08:24:44 -06:00
james.maesandClaude Fable 5.1	ba7fdc23d0	docs(realtime): connector 1.2.1 ... Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 07:55:28 -06:00
james.maesandClaude Fable 5.1	ab51f8da06	docs: the paired Windows connector is 1.2.1 (1.2.0 was never published) ... Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 07:54:57 -06:00
james.maesandClaude Fable 5.1	102fde779c	docs(release): record QQQ Printing 1.1.0 and pin protocol fixtures to 1.1.0 ... Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-05 17:09:05 -06:00
james.maesandClaude Fable 5.1	e33823bbbd	feat(printers): remove printers and devices as archives, purged by retention ... Add nullable removed_at to printing_printer and printing_device (read-only "Removed at" on both tables) through the existing idempotent migration. Remove printers (printingRemoveSelectedPrinters, record and selection) and PrintingService.removePrinter set removed_at, clear approval and exposure, and drop the printer from the operator catalog, submissions, claims, the device/printer selectors and the PRINTERS frame, which is pushed again. A removed queue that the device shares again returns exposed but not approved; approval changes on a removed printer are refused. Remove device (printingRemoveDevices, confirmation required) revokes access through the existing REVOKE control, then PrintingService.removeDevice archives the device and all of its printers; an already revoked device is archived without a new command. Removed devices leave the device list, every device selector and all authenticated paths; job history stays. Retention cleanup hard-deletes removed printers that no job references and removed devices with no jobs and no printers, bounded by the batch size and logged. Native inventory authorization still covers removed rows so a re-shared queue can reactivate. Tests cover hiding, re-sharing, device removal with history, purge bounds and process metadata. Docs: README, UI walkthrough, storage and retention, realtime, changelog (1.1.0). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-05 16:31:33 -06:00
james.maesandClaude Fable 5.1	3fa78decc8	feat(realtime): printer approval over the socket (extension 2.4.0, product 1.1.0) ... Add the printer-approval-v1 capability and the server-to-client PRINTERS frame so a connector can show per-printer approval for the server it is connected to. - HELLO accepts up to five capabilities including printer-approval-v1; the HTTP control poll accepts up to four and stores it in control_capabilities like the others; the ControlPollRequest schema enumeration is extended. - After an accepted INVENTORY's ACK, a connection that advertised the capability receives PRINTERS: { "printers": [ { "printerId", "enabled" } ] } covering every printer in the device's latest accepted inventory (empty inventory: []). - Every approval change (admin route, native approve/disable/set-approval processes, PrintingService.enablePrinter) already publishes the commit wakeup; the connection's single serialized writer now compares the current approval state with the last PRINTERS frame it sent and resends on change only. Connections without the capability never receive PRINTERS. - PrintingService.printerApprovals(deviceId) exposes the list to host code. - Advertise native extension 2.4.0; regenerate the OpenAPI fragment; bump the product to 1.1.0 (pairs with protocol 1.1.0 and Windows connector 1.2.0; wire payload v1 and subprotocol unchanged). CHANGELOG, README, REALTIME/OPERATIONS docs and a dated in-progress session-state note. - Tests: five-capability HELLO, ACK-then-PRINTERS ordering with new printers disabled, approval via the admin route and the service pushing fresh frames, no PRINTERS on an unrelated job wakeup, empty inventory, a four-capability connection never receiving PRINTERS, and control-poll acceptance/bounds. Verified: .\mvnw.cmd -Pui-demo verify -> 195 tests, 0 failures, 0 errors, 1 skipped (opt-in workload), 0 Checkstyle violations, BUILD SUCCESS. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-05 15:45:16 -06:00
james.maesandCodex	1f6342e871	docs: close out printing 1.0 release documentation ... Update setup, operating and release guidance for the published Gitea artifacts, native API and real-time transport. Preserve historical evidence and scope the older optional Authentik fixture accurately. Co-Authored-By: Codex (GPT-6) <noreply@openai.com>	2026-11-04 09:39:13 -06:00
james.maesandCodex	48e6cdb9df	release: adopt published QQQ RC.21 for printing 1.0 ... Co-Authored-By: Codex <noreply@openai.com>	2026-11-03 15:04:49 -06:00
james.maesandClaude Sonnet 5.5	9ccd9d9b43	release: prepare printing 1.0.0 dependency adoption ... Document the final product scope and remaining native-login core publication dependency. Preserve the current core pin until the supported artifact is published. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-03 09:53:23 -06:00
3 people	cf57dfb521	release: prepare qbit-printing 0.4.0-rc.1 ... Use an immutable prerelease version for the existing JAR/POM release workflow; leave the parent, QQQ SDK, dependencies and printing code unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Co-Authored-By: Codex <noreply@openai.com>	2026-11-01 21:37:35 -06:00
james.maesandClaude Sonnet 5.5	38fd06229e	fix: complete printing cohort verification and pin its contract ... Keep the compiler-clean label test helper and record the passed 193-case verification and matching protocol fixture pin without changing runtime behavior. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 17:30:18 -06:00
james.maesandClaude Sonnet 5.5	111cbede8f	feat: integrate compact label tests with strict server contracts ... Preserve the current permission, retained-source and queue implementation while adding job-specific paper and compact four by one and four by two labels. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 17:01:23 -06:00
james.maesandClaude Sonnet 5.5	43253f6676	chore: retain protected printing script quality ancestry ... Integrate the already approved script main and preserve both sets of completed task notes; no application code changes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 16:53:08 -06:00
james.maesandClaude Sonnet 5.5	e4639e3cca	chore: integrate printing standards and strict Java compiler checks ... Preserve current rendering, operator and retained-source behavior while integrating script quality, meaningful headers and strict Error Prone/NullAway contracts. Production and test compilation and the 189-case verification gate pass with zero failures and one intentional workload skip. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 16:51:18 -06:00
james.maes	f2505160c6	chore: preserve current main in script quality branch ... Signed-off-by: James Maes <james@kof22.com>	2026-11-01 15:17:23 -06:00
3 people	f80498513e	chore(scripts): enforce locked lint and type quality gates ... Add strict Python and checked JavaScript tooling, explicit source-scope checks and real rejection probes to CI. Preserve existing runtime behavior and document the limited bundle and test portability changes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Co-Authored-By: Codex GPT-6 <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 14:47:49 -06:00
james.maesandClaude Sonnet 5.5	65e32f5ce9	fix(printing): reconcile 2.3 and await realtime shutdown ... Preserve the rendering changes from main while assigning operator, media and retained-source support to printing 2.3. Wait for channel workers before stopping the host so they cannot recreate a closed store. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 14:42:57 -06:00
james.maes	88f5fbb4b5	Merge branch 'main' of https://github.com/QRun-IO/qbit-printing into feat/echo-printing-catalog-20261101 ... Signed-off-by: James Maes <james@kof22.com>	2026-11-01 13:05:09 -06:00
james.maesandCodex GPT-6	08ee0efa3d	feat: authorize operator printing with exact retained acceptance ... Add current-user printer media catalog, stable request recovery and atomic retained-source acceptance. Recheck native authority through admission and commit, bind history to the accepted printer record, and gate selected media on the current client capability. Co-Authored-By: Codex GPT-6 <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-01 13:04:03 -06:00
james.maesandCodex	1a0964ef23	chore: enforce owned source copyright notices (#25) ... * chore(standards): preserve owned-source copyright notices Add accurate repository copyright and license comments to 50 owned source/build/configuration files. Preserve existing holders, upstream wrappers, legal payloads and schema/data exemptions. Exact inverse-byte reconstruction and applicable parser/token/AST checks prove comment-only changes; existing relevant regressions pass. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com> * chore: enforce owned source copyright notices Check real leading comments against explicit repository provenance and retain existing native style gates. Co-Authored-By: Codex GPT-6 <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com> --------- Signed-off-by: James Maes <james@kof22.com> Co-authored-by: Codex (GPT-6) <noreply@openai.com>	2026-11-01 12:41:00 -06:00
james.maesandCodex	02b922aa11	fix(dev): accept compatible printing discovery in native provider tests (#23) ... Reuse production Core strict discovery and the shared printing-major-2 gate while retaining the exact experimental API 1.9/native-session requirement. Add build-time fake-HTTP boundary cases without changing PKCE, TLS, provider or permission handling. The old native gate fails compatible 2.1.0; the fix passes 12 native and nine default discovery cases with zero compiler warnings/errors. One fresh current-source Docker provider run passes all eight checks with verified owned cleanup. Preserve unreleased-upstream and installed-browser limitations; no live runtime or physical printing changes. Signed-off-by: James Maes <james@kof22.com> Co-authored-by: Codex (GPT-6) <noreply@openai.com>	2026-11-01 12:04:51 -06:00
james.maesandCodex	bfba557b66	docs: record published Docker qualification (#22) ... Record protected PR21 publication and passing hosted Docker, script and Java results. Keep the experimental upstream candidate distinct from released-runtime adoption and the unchanged live installation. Both Markdown files and diff checks pass; no runtime changes. Prepared and reviewed with Codex (GPT-6). Signed-off-by: James Maes <james@kof22.com> Co-authored-by: Codex (GPT-6) <noreply@openai.com>	2026-11-01 10:53:45 -06:00
james.maesandCodex	3592decba8	feat(dev): add isolated Docker printing and provider qualification (#21) ... * feat(dev): add isolated Docker printing and provider qualification Provide owned local QQQ, MinIO and optional Authentik development fixtures with pinned inputs, protected synthetic state and ownership-checked cleanup. Exercise real Core/Java WebSocket jobs, S3 retention/isolation and opt-in native PKCE/provider renewal and revocation. Add cross-platform script gates and hosted Docker smoke CI. Include the opt-in 10000-job pooled-SQL/reopen regression and scoped evidence. The experimental API1.9 source remains explicitly unreleased and separate from the released runtime dependency set. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com> * fix(dev): report early workload failures before server waiting Preserve bounded client diagnostics privately and emit only allowlisted stage and exception classifications. Early failed clients no longer hide behind the server completion timeout; ownership-checked cleanup remains in finally. Five actual-entrypoint regression cases pass; all33script tests and parser/analyzer checks pass. This exposes the still-unknown hosted client failure without changing production behavior. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com> * fix(dev): accept compatible realtime printing API minor versions Use production Core discovery's strict stable SemVer validation and the realtime major2 compatibility gate instead of requiring exactly2.0.0. Protected main now advertises compatible2.1.0; the old fixture rejected it before login. Pinned-Core build reproduced2.1.0 rejection before the fix and passes all9positive/negative HTTP discovery cases after it. Docker builds run these checks. No production client, server, dependency or runtime change. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com> --------- Signed-off-by: James Maes <james@kof22.com> Co-authored-by: Codex (GPT-6) <noreply@openai.com>	2026-11-01 10:12:08 -06:00
james.maesandCodex	82fc5e5f8a	docs(release): finalize coordinated realtime candidate metadata ... Prepare0.3.0-rc.1 notes for native printingAPI2.0, outbound realtime delivery and coordinated server-first upgrade. Pin the merged protocol contract and preserve the distinction between source/release and installed acceptance. Validation: changedMarkdown, diff and actionlint checks pass. Application, schema and test behavior are unchanged. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 18:04:47 -05:00
james.maesandCodex	55f4266735	chore(ci): pin the verified printing API 2 contract ... Use signed protocol df3729ac632d4a34a3fb8423acef465042a624fc for reproducible consumer checks and record the successful final API 2 cross-runtime qualification. The deployed 0.2 package remains unchanged. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 16:29:28 -05:00
james.maesandCodex	e793b09922	fix(printing): version realtime claims and align connection freshness ... Advertise native printing API 2.0.0 because mandatory synchronized WebSocket claims are incompatible with the published HTTP-only native API. Keep the framework path and wire envelope unchanged. Derive dashboard freshness from the configured heartbeat timeout and record authorized control-channel liveness. Validation: final Maven verify passed118 tests with zero Checkstyle violations. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 16:25:47 -05:00
james.maesandCodex	2ed454301e	feat(printing): add authenticated realtime device transport ... Replace native job/control polling with client-initiated WebSockets, durable state and receipt reconciliation, independent verified document streams and native administrator settings for transfer, connection and admission limits. Preserve QQQ current-user authorization and device binding on every operation. Validation: Maven verify passes 117 tests with zero Checkstyle violations; OpenAPI generation/check and diff checks pass. Consumer CI pins protocol 67be986cb76d6b5d9a9f72cad054193b0d11b0d5. Installation is separate. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 16:12:42 -05:00
james.maesandCodex	ad53b69c0f	docs: prepare native printing 0.2.0 prerelease ... Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 11:06:12 -05:00
james.maesandCodex	3b73808650	fix: prevent legacy downgrade of native device credentials ... Reject bound device tokens on every legacy device route. Native proof verification continues through standard QQQ sessions and current user permissions. Disable legacy enrollment by default and explicitly in the native host; legacy-only demo and fixtures opt in, preserving eligible unbound-device migration. Validation: 110 Java tests pass with zero failures/errors/skips and zero Checkstyle. Actual native-bind HTTP regressions reject bearer-only claim/content/queue/control; legacy enrollment denial preserves the code for successful native enrollment. Independent review found no remaining blocker. No schema or dependency changes. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 10:24:13 -05:00
james.maesandCodex	23fccbb326	docs: explain standard QQQ session freshness policy ... Record verified RC20 behavior: OAuth2 caching defaults off and reruns supported host authorization hooks; explicitly cached sessions require normal invalidation or a qualified freshness policy. Table-based sessions reread user rows but do not automatically interpret arbitrary enabled fields. Validation: exact frozen source and a10-check synthetic reproduction. No product code or provider/runtime configuration changes. Long-lived provider renewal and configured native grants remain deployment qualifications. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 09:35:57 -05:00
james.maesandCodex	3435686e7e	fix: enforce native permissions during printing selections ... Wrap standard extraction with explicit current-user enforcement after callbacks, and authorize preview counts before the standard tenant-filtered count. Apply the wrapper to all14 printing selection processes so trusted internal defaults cannot skip table policies before Transform/Load checks. Validation:109 Java tests pass with zero failures/errors/skips and zero Checkstyle. New regressions exercise count/query denial, callback weakening, selected/filter tenant isolation and process registrations. Native API classes remain byte-identical to the23-check real client/server interop artifact. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 09:18:43 -05:00
james.maesandCodex	3062fc8e84	feat: add native printing device controls and session authorization ... Add record/selection actions, per-device printers/jobs/queue/history and observed connection/control status. Persist bounded device actions and immutable receipts, serialize queue clearing against claims, and cancel only owned Windows jobs. Register semantic printing extension 1.0.0 with standard QQQ sessions, secondary bound-device proof, current native table/process/record checks and explicit permission enforcement. Preserve legacy compatibility without primary fallback. Pin protocol cc3c4e50e8f6f4fbc93d351fb51edb4f5438bbd3 and prepare 0.2.0-rc.1. Validation: Java21 verify passes 106 tests with zero failures/errors/skips and zero Checkstyle. All204 runtime dependency hashes match frozen inputs. Native HTTP/OpenAPI, authority denial, FIFO eligibility, queue races, selection replay and offline command expiry covered; cross-runtime/provider/install acceptance remain separate gates. Independent source review findings are corrected. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 08:51:53 -05:00
james.maesandCodex	c3e37a548e	docs: update published printing release guidance ... Align installation examples and acceptance notes with the verified release. Keep physical-output and production deployment qualification limits explicit. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 05:13:59 -05:00
james.maesandCodex	c34883da07	fix: use official Query mascot on diagnostic prints ... Preserve the official artwork aspect ratio in every PDF and thermal profile. Record provenance and the completed local test and installed-client acceptance. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 04:51:49 -05:00
james.maesandCodex	31d1bc1cab	docs(printing): record verified local host deployment ... Record the approved H2 exception, passing complete CI and exact artifact comparison, verified recovery/cold-copy checks, and the state-preserving local native QQQ cutover. Keep remote S3 and physical-output limits explicit. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 04:09:57 -05:00
james.maesandCodex	09e099501b	fix(ci): apply approved H2 license metadata exception ... Reference merged standards EX-0013 while preserving the required reviewed-version inventory guard and every other license and vulnerability check. Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-31 03:40:35 -05:00
james.maesandCodex	45261d5508	fix(storage): preserve documents when S3 key layouts change ... Bind external print documents to the reviewed native S3 key layout and separator. Serialize destination components as ordered JSON so valid multiline prefixes cannot collide. Refuse incompatible reads, retries and cleanup while preserving content availability and retained-byte accounting; validate new retries before upload reservation and keep existing retry receipts and inline documents compatible. Validation: isolated Java 21 verify passes 72 tests and zero Checkstyle violations. The multiline-prefix regression fails before the fix; independent review found no remaining issue. Actual Windows-to-Linux S3 qualification returns 409 before read/retry/cleanup IO, preserves the exact object and counters, and records zero transmissions with a positive-control observer. Five documentation files pass Markdown lint. Fresh hosted checks and the existing H2 metadata approval remain pending. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 23:09:20 -05:00
james.maesandCodex	00dd2dda2d	fix(build): package license and attribution notices ... Use standard Maven resources to include root LICENSE and NOTICE under META-INF while retaining existing runtime assets. No implementation or dependency changes. Validation: isolated frontend-profile verify passes 67 tests with zero Checkstyle violations. JAR inspection verifies exact notice bytes, all 38 implementation classes unchanged, font/license/logo resources retained, and unchanged dependency declarations. Independent review found no issue. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 21:57:39 -05:00
james.maesandCodex	d1821bedf2	fix(ci): constrain reviewed H2 license scope ... Require the reviewed H2 runtime in the selected Maven inventory and reject absent or different versions. Record unchanged H2 licensing and exact-artifact native cold-restart acceptance while keeping the central license exception and live deployment pending. Validation: 11 inventory guard tests and 6 SARIF guard tests pass; workflow lint and independent review passed. Production Java remains the verified 67-test H2-fixed candidate. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 21:49:38 -05:00
james.maesandCodex	fb99fafbbf	fix: use H2 with durable close-time compaction ... Pin H2 2.4.240 for upstream compaction data loss. A closed legacy fixture lost newly created audit tables after reopening with 2.3.232; replacing only the driver preserves them. Add cold-reopen durability coverage and document backup/runtime qualification. Full isolated verification passes 67 tests and all 204 dependency inventories agree. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 21:29:26 -05:00
james.maesandCodex	d52dfd722b	fix: consume device request bodies before queue mutations ... Claim and cancel could complete before reading valid JSON, causing Jetty to close the persistent connection before a subsequent status event. Consume the bounded body after authentication. A split-body HTTP regression fails before this change; full isolated UI-profile verification passes 66 tests and Checkstyle. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 20:55:15 -05:00
james.maesandCodex	60ce6e4f93	ci: verify the complete printing host runtime inventory ... Resolve the selected UI profile once into a Maven CycloneDX graph and fail closed when Trivy or OSV omits packages or returns malformed evidence. Keep existing vulnerability and malicious-package gates. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 20:43:47 -05:00
james.maesandCodex	78e09115cb	feat: connect authenticated QQQ screens to the local printing host ... Use native table authentication and scheduling with preserved paired H2 data, tenant authorization and strict browser-origin checks. Verify both H2 identifier conventions and account/session boundaries. Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 20:10:47 -05:00
james.maesandCodex	aeac1a6842	fix: bound print resource admission and inventory history ... Co-authored-by: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>	2026-10-30 19:37:30 -05:00