Add rpa-bot-handoff skill: ops guide for bot handover

The skill scans a bot with subagents (never runs it) and writes
HANDOVER.md, an 11-section ops guide in the operator's order: where is
what, how to run, how long to wait, after the run, how to see an
exception, exception list, how you will know, how to tell us, don'ts,
issues seen before. Dev material (check against 12 failure classes from
Tebra Auto Post, gaps with file:line, incidents) goes to HANDOVER-DEV.md.

Also adds ADR-0004, glossary terms, five fixture bots and a handoff eval
runner (--resume, --regrade) with results from 47 runs of the earlier
13-section version. The grader still expects that structure and must be
updated before the next eval run.

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

tests/evals/results/handoff/h-mail-intake-full-r1.json

@@ -0,0 +1,31 @@
+{
+  "case": "h-mail-intake/full",
+  "rep": 1,
+  "passed": true,
+  "checks": {
+    "HANDOVER.md written": true,
+    "no other file changed": true,
+    "bot never run": true,
+    "no placeholders left": true,
+    "13 sections in order": true,
+    "used subagents": true,
+    "every status listed": true,
+    "catalogue: 4+ complete rows": true,
+    "F1-F12 all accounted for": true,
+    "no code refs in ops sections": true,
+    "fix-before-handover has file refs": true,
+    "no secrets or personal data": true,
+    "where-to-look respects ops access": true,
+    "asks escalation": true,
+    "asks ops access": true,
+    "known incidents from history": true,
+    "misleading status flagged": true,
+    "stuck Processing item blocks the queue": true,
+    "20 MB limit": true
+  },
+  "cost_usd": 1.3510176,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-full-oh8t63qd\\project",
+  "reply": "`HANDOVER.md` ready, repo root-la irukku. Bot-a run pannala, vera entha file-um change pannala.\n\n**Summary:**\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 8 (E01\u2013E08) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot entha window-um drive pannala). F12-oda \"shared resources rewritten on start\" part-um not applicable |\n| Fix before handover | 20 items |\n\n**Mukkiyamaana findings:**\n- Moonu \"fix\" commits-um code-ah maathala, comment mattum add pannirukku. So moonu incidents-um innum open.\n  - Stuck Processing item vandha ella run-um block aagum.\n  - Encrypted PDF \"Done\"-nu kaattum, aana copy aagaathu.\n  - Mailbox password expire aana, adhu log-la varaathu.\n- `.env` (credentials) and `logs/intake.log` git-la commit aagirukku. Log-la oru sender email address irukku. Mailbox password-a rotate pannanum.\n- Ops ungalukku new mail-a mailbox-la open panna, adhu read-nu mark aagidum. Appuram bot andha referral-a skip pannidum.\n\n**Fix before handover (20):**\n1. Stuck Processing item blocks every later run\n2. A damaged PDF or missing temp file crashes the run\n3. Encrypted PDF shows Done without being copied\n4. The final mailbox failure is never logged\n5. Crash tracebacks never reach the log\n6. A crash while mail is being fetched loses referrals\n7. Mail with no attachment, or mail someone opened first, leaves no record\n8. Attachments with the same name overwrite each other; file names are not sanitised\n9. Failed and Quarantined items are never retried, and re-queueing needs a database edit\n10. `queue_viewer.xlsx` is missing from the repo\n11. No version string\n12. No run start/end log line\n13. Credentials and the log are committed to git\n14. No timeouts on the mailbox connection or the share copy\n15. No lock against overlapping runs\n16. No setup step for folders and the queue table\n17. Signature images clutter the queue as Quarantined\n18. `data/tmp/` is never cleaned\n19. Hard-coded fallback share path\n20. Ops access to Task Scheduler not confirmed\n\n**Checks:**\n- Ellaa status values-um doc-la irukku.\n- Code refs (file:line) section 13-la mattum dhaan irukku.\n- PHI, IP, credentials doc-la illa.\n\n**Gaps:**\n- `queue_viewer.xlsx` repo-la illa. Adhanaala on-screen colours, viewer columns verify panna mudiyala.\n- Ops-ukku Task Scheduler access irukka-nu therila. Bot-a stop panradhu (section 4) and E06 rendum adha depend pannudhu (item 20).\n\nQUESTIONS: Who does ops call for a dev issue (team or role), and how (ticket, chat channel)? | Which of the bot's places can ops open - the app's screens, the output folder, the log folder, the database? | Are there any statuses or exceptions whose meaning the code doesn't make clear?",
+  "stderr": ""
+}