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-screens-r4.json

@@ -0,0 +1,31 @@
+{
+  "case": "h-mail-intake/screens",
+  "rep": 4,
+  "passed": false,
+  "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": false,
+    "misleading status flagged": true,
+    "stuck Processing item blocks the queue": false,
+    "20 MB limit": true
+  },
+  "cost_usd": 1.2779054,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-screens-p589__0w\\project",
+  "reply": "Na `HANDOVER.md` ezhudhi repo root la vechiten. Bot-a run pannala, code ethuvum maathala.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 7 (E01\u2013E07) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot entha window-um drive pannala) |\n| Fix before handover | 19 items |\n\n**Mukkiyamaana vishayangal:**\n- **3 \"fix\" commits-um oru comment line mattum add pannirukku.** Code maarave illa, so moonu incident-um innum fix aagala. Doc-la \"not fixed\" nu thaan pottiruken.\n- Password-protected PDF-a **Done**-nu mark pannudhu, aana share folder-ku copy aagala. Ithu Statuses-la \"needs follow-up\" nu irukku (E02), Fix list-la #3.\n- Oru row **Processing**-la stuck aanaa, ella intake-um nindrum. Ops-ku DB access illa, so idha Dev mattum thaan clear panna mudiyum (E04).\n- Mailbox login fail aanaa (E05), ops paakkura entha idathilayum theriyaadhu. Log-la mattum thaan irukku.\n\n**Assumption, nee check pannu:** Bot-ku sondha screen edhuvum illa. README-la ops use pannra `queue_viewer.xlsx`-a thaan \"bot's own screen\"-nu eduthukitten. Output folder-na shared intake folder. Log, database rendum ops-ku open panna mudiyaathu, so andha info ellam Dev-ku pogudhu, illa Fix list-la irukku.\n\n**Verification:**\n- Ella status/note string-um Statuses table-la irukku.\n- PHI, email, server path, `.env` value edhuvum doc-la illa. Sample log-la oru sender email irundhuchu, adha copy pannala. Adhu Fix #16-la irukku.\n- file:line refs Fix section-la mattum.\n\n**Also noticed:** `queue_viewer.xlsx` repo-la illa. So viewer-la status colours enna nu verify panna mudiyala. Doc-la \"bot sets no colours\"-nu thaan pottiruken.\n\nQUESTIONS: Escalation: who ops calls for a dev issue (team or role, not a personal phone number), and how (ticket, chat channel). | Ops access: which of the bot's places ops can open - the app's screens, the output folder, the log folder, the database. | Unknowns: any statuses or exceptions whose meaning the code doesn't make clear.",
+  "stderr": ""
+}