The contracts the preview, bridge and render target packages plug into. No
label prints differently and no existing host adapter changes.
GenerationPorts:
- Diagnostic (with Severity): a code from a closed vocabulary, an author
element id, a box and named integers. It has no field that holds free text.
- PreviewRequest, PreviewPage and Preview, and IsolatedRenderer.preview as a
default that refuses, so an adapter written before it compiles unchanged.
- 15 version 2 FailureCode values after the 13 released ones, and
RenderException(FailureCode, Diagnostic) beside the existing constructor.
- Integer targetDpi on RenderRequest (absent, 203, 300 or 600); the
seven-argument constructor is kept and nothing reads the value yet.
Registration points, each an empty class that is already called:
GenerationPreviewProcesses, GenerationAssetProcesses,
GenerationUpgradeProcesses and GenerationAssetTables from the producer, and
GenerationPreviewWidget.section(table) from GenerationTables.
Bridge: IsolatedRendererBridge maps any FailureCode name from a 0.1.0 worker
to a typed refusal, so growing the enum alone would have widened what such a
worker can name. The 13 released codes are now the set a 0.1.0 worker may
name; BridgeTest asserts the other 15 stay generic.
Tests: record validation, default refusals, source compatibility of the
existing constructors, and that the producer registers exactly the tables,
processes, choices, widgets and template sections it did before (the lists
were captured from the untouched v1.1.0-RC.2 tag).
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Coverage gates:
- renderer and bridges/renderer gain JaCoCo (prepare-agent, report, check at
verify) with a bundle rule at the measured baseline, rounded down: renderer
94% instructions and 91% lines, bridge 85% instructions and 82% lines.
- New code is held to 100% line coverage from its first commit: packages
com.kingsrook.qbits.renderer.scene2 and below, AssetInspector, ZplRaster,
and the new foundation classes the label layout design names. The rules
match nothing until those exist, so later packages do not edit these poms.
- The foundation's 85% instruction and 90% class rule is unchanged.
Fuzz scaffolding:
- MutationCampaign in each module's test tree: a seeded, bounded mutation
harness with no clock and no unseeded randomness; a finding replays from
its seed and iteration.
- One campaign per module in the normal test phase: what the version 1 scene
parser accepts is a version 1 scene (checked by a second parser), and what
the host printer gate accepts holds only the renderer's command set.
- docs/security/fuzzing.md: targets, properties, limits, seeds and replay.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Version 1 scenes (qqq-zpl-scene/1) are frozen. This adds 42 render requests
and the exact ZPL the released renderer returned for each, so later work can
prove that labels already printing are untouched.
- renderer/src/test/resources/compat-v1: cases, stored ZPL, SHA256SUMS and a
README with provenance and rules. The bytes were produced by the source of
tag v1.1.0-RC.2 (e9ffba48), not by this branch, and the same test passed
against the tag on Temurin 21.0.12 (Windows) and 21.0.9 (the CI image).
- renderer ZplSceneOneCompatibilityTest: fails on the first differing byte,
on a manifest that does not name exactly the cases, and on a corpus that
misses a version 1 element type, property or resolution.
- bridges/renderer ZplSceneOneCompatibilityTest: every stored output has its
manifest hash and passes the unchanged ZplOutputPolicy. It reads the
renderer's directory in place, so there is one copy of the corpus.
Covered: the four shapes Forge publishes at 203 and 300 dpi (GS1-128 with
fit and quiet, text in font 0, rasterText with fontAsset), the README and
BARCODE-FIT.md examples, and one scene per element and option at 203, 300
and 600 dpi. All values are synthetic.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
james.maesandClaude Fable 5.2