rpa-bot-handoff: email To the developer with their manager in CC, and hand ops a PDF

- Section 5 of the SOP now names a real "To" (the developer) and "CC"
  (the developer's manager, not the operator's), and the email block to
  copy starts with To: and CC: lines. The skill asks for both addresses.
- to_docx.py --pdf also writes the PDF (Word through PowerShell on Windows,
  LibreOffice elsewhere) and prints the real page count against MAX_PAGES.
  The PDF is what ops gets.
- Tebra reference and README updated; new test for the To/CC lines.

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

skills/rpa-bot-handoff/README.md

@@ -3,12 +3,12 @@
 A Claude skill that writes a short **Handover SOP** for an RPA bot that is being handed over to an ops team.
 
 ## What you get
-**`<Project Name> Handover SOP.docx`** (and `HANDOVER-SOP.md`): at most 4 pages, in plain words, for operators who don't read code:
+**`<Project Name> Handover SOP.pdf`** (plus the `.docx` and `HANDOVER-SOP.md`): at most 4 pages, in plain words, for operators who don't read code:
 1. How to run: the URL or shortcut, what to click, and what a new click does to the previous results
 2. What you see while it runs: what shows where, a normal run, how long each step may take
 3. Result: how a good run ends, where the report is, what each status means
 4. When something goes wrong: how it shows, each message (E01, E02...) with what to do, the don'ts, how to stop it
-5. Email us: the address, when to email, and the email to copy
+5. Email us: To the developer, CC their manager, when to email, and the email to copy
 
 Problems the scan finds for the dev team are listed in the chat, not in the SOP.
 
@@ -18,9 +18,9 @@ Copy this folder to `~/.claude/skills/rpa-bot-handoff/`.
 ## Use
 In your bot project, ask Claude: *"write the handover SOP for this bot"* or *"document this bot for handover"*. The skill:
 1. Scans the code with a subagent. It never runs the bot.
-2. Asks up to two things: the email group ops writes to, and where ops runs the bot.
+2. Asks up to two things: the developer's and the manager's email (To and CC), and where ops runs the bot.
 3. Writes the SOP, checks every quoted message and label against the code, and keeps it under 1,400 words.
-4. Turns it into the Word file you give to ops.
+4. Turns it into Word and PDF; you give the PDF to ops.
 
 ## Files
 | File | What it is |
@@ -29,4 +29,4 @@ In your bot project, ask Claude: *"write the handover SOP for this bot"* or *"do
 | `templates/HANDOVER-SOP.md` | The SOP skeleton |
 | `templates/failure-classes.md` | 12 failure classes from Tebra's first months with ops, used as a scan checklist |
 | `templates/reference/tebra-auto-post.md` | The SOP filled in for Tebra, scrubbed |
-| `templates/to_docx.py` | Turns the SOP into Word and prints the word count (`--selfcheck` tests it) |
+| `templates/to_docx.py` | Turns the SOP into Word, and with `--pdf` into PDF; prints word and page counts (`--selfcheck` tests it) |