rpa-bot-handoff: write down the PDF recipe that worked

Step 4 now gives the exact recipe used for the MEK SOP: Python markdown
(tables + fenced_code, blank line before lists), the page style (A4,
navy/teal headings, light-blue table header, bold E-numbers, rows that
don't split, grey email box), headless Edge/Chrome --print-to-pdf without
header/footer, and a page-by-page look via PyMuPDF images.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

skills/rpa-bot-handoff/SKILL.md

@@ -36,7 +36,7 @@ Run started / Error: E<number> - <message> / Where / What I did / Attached: scre
 Never send: passwords, patient data, result files that hold patient data.
 ```
 
-4. **Make the PDF yourself:** turn the SOP into one self-contained HTML page (A4, 1.8 cm margins, clean sans-serif 10.5 pt, bold headings, bordered tables with a shaded header row at 9.5 pt, the email block in a grey box, no page break inside a table row), then print it with headless Chrome or Edge (`--headless --print-to-pdf`) to `<Project Name> Handover SOP.pdf`. Look at every page. Over 4 pages: shorten cells, never drop a message.
+4. **Make the PDF yourself** (no converter script): turn the SOP into one HTML page (Python `markdown` with `tables` + `fenced_code`; add a blank line before every list or it merges into the paragraph above). Style: A4, 16-18 mm margins, Segoe UI 10.5 pt, title 19 pt navy with a teal rule under it and the version line in small grey, navy section headings with a thin rule, tables full width with borders, light-blue header row, 9.5 pt cells, bold E-numbers, `tr { break-inside: avoid }`, the email block in a grey box with a teal left edge. Print with headless Edge or Chrome: `--headless=new --no-pdf-header-footer --print-to-pdf="<Project Name> Handover SOP.pdf"`. Render each page to an image (PyMuPDF) and look at it. Over 4 pages: shorten cells, never drop a message.
 5. **Hand over** the PDF. Problems for the dev team go in the chat (at most 5 lines), not in the SOP.
 
 **Rules**