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-r5.json

@@ -0,0 +1,31 @@
+{
+  "case": "h-mail-intake/full",
+  "rep": 5,
+  "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": false,
+    "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": false,
+    "stuck Processing item blocks the queue": true,
+    "20 MB limit": true
+  },
+  "cost_usd": 0.8563970000000002,
+  "subagents": 0,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-full-e8dj8tc6\\project",
+  "reply": "`HANDOVER.md` ready, repo root-la irukku. Bot-a run pannala, code-um change pannala. Repo-la oru script, 4 commits mattum dhaan irundhudhu, so subagents spawn pannaama naane direct-aa padichen.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template sections ellaam irukku) |\n| Exceptions | 11 (E01\u2013E11) |\n| Statuses | 6 (code ezhudhura ella status-um irukku) |\n| Failure classes | 11 covered, F2 not applicable (bot endha window-um drive pannala) |\n| Fix before handover | 15 items |\n\nOps-ku mukkiyamaana findings:\n- **Moonu \"fix\" commit-um code-la oru comment mattum dhaan add pannirukku.** Bot behaviour maaridala. Ella incidents-um innum nadakka mudiyum.\n- **Oru item \"Processing\"-la stuck aanaa, adhukku appuram ella run-um eppavume abort aagum** (E03). Ops-ku database access illa, so dev dhaan clear pannanum.\n- **Password potta PDF \"Done\"-nu kaattum, aanaa intake folder-ku copy aagaadhu** (E06).\n- **\"Failed\" items-a bot eppavume retry pannaadhu.**\n- **Log-la item number mattum dhaan varum.** Sender, file name rendum varaadhu, so ops edhuvum panna mudiyaadhu.\n- **Rendu attachment-ku ore file name irundhaa, onnu innonna overwrite pannidum** (E08).\n- **README sollra `queue_viewer.xlsx` repo-la illa**, so ops statuses-a log-la mattum dhaan paakka mudiyum.\n\nUnclear-aa irundha statuses-ku code padi en best reading use pannen. \"encrypted\" Done-a \"needs follow-up\"-nu mark pannirukken. Check pannadhu: doc-la PHI, emails, server path, credentials edhuvum illa. Log-la oru pazhaya line-la sender email address irukku; adha doc-ku copy pannala, Fix #15-la flag pannirukken.\n\nQUESTIONS: Escalation: who does ops call for a dev issue (team or role), and how (ticket, chat channel)? | Ops access: which of the bot's places can ops open - the app's screens, the output folder, the log folder, the database? | Unknowns: what do the statuses or exceptions whose meaning the code doesn't make clear mean?",
+  "stderr": ""
+}