# Proposal ## Why While verifying the `revert-colour-mode-default` change, an operational check found a divergence for one PPD option: after the entrypoint applies `PRINTER_OPTIONS="BRColorMode=None TonerSaveMode=True"`, the queue shows `BRColorMode ... *None` (consistent everywhere) but `TonerSaveMode ... *False` even though the queue's PPD copy at `/etc/cups/ppd/.ppd` contains `*DefaultTonerSaveMode: True`. The rejected tool option `lpadmin -p -o TonerSaveMode=True` (config-only, immediately surfaced) reproduces the same split. `TonerSaveMode` is the option that the `APPrinterPreset` entries use to implement the "draft prints with toner saving" behaviour recorded in the spec, so a queue default that only half applies undermines one of the documented scenarios. The current spec (`Queue defaults are configurable at runtime` → *Options are applied on start*) is written as a configuration check ("the queue defaults include `TonerSaveMode=False`") and is satisfied by the settings file alone, so it does not pin down whether a job actually receives `TonerSaveMode=True`. That gap is why the divergence went unnoticed. This change turns the requirement into an observable one — the emitted job — and makes whatever the investigation finds explicit in the spec instead of leaving the contradiction undocumented. ## What Changes - **Investigate** the `TonerSaveMode` split during apply: determine whether a job with the queue default `TonerSaveMode=True` actually emits the toner-save PostScript (`statusdict/tonersave` → `true`) or silently falls back to the PPD default `False`, and record the root cause in the design/tasks notes. - **Spec** (`printserver/cups`): replace the configuration-only *Options are applied on start* scenario with an observable job-level scenario; add a scenario that pins down what a job whose queue default conflicts with the PPD default must emit. Add the `TonerSaveMode` observable to the colour-mode requirement's scope (BRColorMode only) so the two are not conflated. - **Tests** (`tests/`): add a job-level integration test that applies the documented `PRINTER_OPTIONS="BRColorMode=Vivid TonerSaveMode=False"` example, submits a job with the bundled sample, and asserts the emitted PostScript carries `UseCIEColor true` (Vivid) **and** `statusdict ... tonersave ... false` (TonerSaveMode) — i.e. the queue default wins over the PPD default in the output. If the investigation shows it cannot win, the test instead asserts the honest current behaviour and the spec records the limitation. - **README**: state what `PRINTER_OPTIONS` queue defaults do to a job, with the verified example output, and note any option-specific caveat found. No change to `entrypoint.sh` plumbing is planned: it already calls `lpadmin -o