/* ══════════════════════════════════════════════════════════════════════ coa-straight.css — a certificate, a lab report or a lot sheet is drawn FLAT. Every page except standards.html. OWNER, 2026-08-26: "also the coas are crooked but the client wants them to be straight." ── WHY THIS SHEET IS SCOPED TO AN ATTRIBUTE ──────────────────────────── lib.linkCss() links a lane sheet on EVERY built page, standards.html included, and standards.html belongs to a different lane in this same pass. So the sheet does nothing until 30-coa-straight.mjs stamps `data-cc-coa-straight` on , and the module stamps every page BUT standards.html. The boundary between the two lanes is therefore a fact on disk that either side can check, not a promise in a comment. THE REASON standards.html IS EXCLUDED IS THE OWNER'S BRIEF, NOT A COLLISION HAZARD. That page is assigned to the research-layout lane, which already writes `body .pg-plate-inner img.pg-coa { transform: none }` at final/css/research-layout.css:143 — an earlier draft of this comment cited :121, which is prose inside that file's opening block. The only property this sheet and that one both declare is `transform`, and both want the same value, so arming standards.html would have been REDUNDANT rather than destructive: a sheet that declares only `transform` and `rotate` cannot reach that lane's isolation, z-index or width work. Redundant is still not ours to write. ── WHY !important, WHICH IS NOT USUALLY THE ANSWER HERE ──────────────── A document tilt on this engine can arrive by four routes, and NONE of them loses to an ordinary later rule: 1. a page-level