ee782b7d6e
Checkpoint implementation at user-requested stop; document known failures and incomplete release qualification. Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: GPT-6 Codex <noreply@openai.com>
2.8 KiB
Verification record — 2026-10-30
./mvnw.cmd -B verify completed at 20:45:01 CDT with 22 tests, zero failures, errors or skips, and zero Checkstyle violations. Main artifact: target/qbit-document-generation-renderer-0.1.0-SNAPSHOT.jar; runtime distribution dependencies: target/lib.
The suite exercises fixed-argv subprocess output limits, cleared environment, timeout and interruption; fake-daemon runtime/image rejection, requested and inspected controls, exact-owned cleanup, ambiguous create recovery, foreign-label refusal, durable cleanup failure/restart recovery, prevention of new create while a failed-cleanup lease occupies capacity, failed fsync before launch, concurrent journal initialization, JVM admission shared by adapter instances before asset reads, release after exception, immutable asset authorization/digest and font metadata, strict scalar-only response parsing, identity/media/hash/length/frame rejection, bounded pure context, and independent ZPL grammar/placement/raster/control rejection.
Checked-in src/test/resources/corpus contains generated trusted renderer fixture bytes, not uploaded or confidential records. Both real PDF and ZPL outputs pass the bridge's offline transport/output checks. This is producer/consumer compatibility testing; the bridge does not parse PDF internals. The standalone renderer has its own rendering/barcode corpus and dependency verification.
Independent source review: qbit-documents/docs/reviews/renderer-bridge-native-review.md. The reviewer identified missing aggregate admission and two journal concurrency races; fixes added shared JVM admission, locked durable lease capacity and race-specific filesystem handling. The reviewer inspected these corrections. Tests cover shared admission, failed cleanup capacity, restart and concurrent initialization; the exact disappearance-between-enumeration-and-stat branch is source-reviewed, not deterministically interposed by a filesystem fixture.
The bridge dependency distribution excludes legacy PDFBox/OpenHTML engines inherited from core. No scripting QBit, PDF renderer, FreeMarker or Okapi implementation is linked by this adapter. Existing application core dependencies remain the application's responsibility; this is not an estate-wide dependency upgrade.
No Docker daemon, renderer container, gVisor runtime, systemd unit, hostile template, physical printer or external storage service was run by these tests. POSIX directory fsync and file locking, actual cgroup controls, network/filesystem/secret isolation, crash/daemon-disconnect recovery, aggregate host memory/CPU admission, isolated PDF inspection/quarantine, asset-reader deployment integration, and printer/scanner behavior still require the explicitly authorized deployment qualification described in DEPLOYMENT.md. The example qualification remains unset and cannot launch production jobs.