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

@@ -0,0 +1,31 @@
+{
+  "case": "h-mail-intake/screens",
+  "rep": 2,
+  "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": true,
+    "stuck Processing item blocks the queue": true,
+    "20 MB limit": true
+  },
+  "cost_usd": 0.7964053999999999,
+  "subagents": 0,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-screens-k8d75ic5\\project",
+  "reply": "`HANDOVER.md` ready \u2014 repo root-la irukku: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-screens-k8d75ic5\\project\\HANDOVER.md`. Bot-a run pannala, code-um maathala.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template order apdiye) |\n| Exceptions | 10 (E01\u2013E10) |\n| Failure classes | 11 covered, 1 not applicable (F2 \u2014 bot entha window-um drive pannala, mailbox + share mattum) |\n| Fix before handover | 12 items |\n\n**Mukkiyamana findings:**\n- Ops-ku intake folder mattum dhaan theriyum. Statuses, notes, log ellame dev-ku mattum. README sollura `queue_viewer.xlsx` repo-la illa. Adhanaala \"Where to look\" table-la perumbaalum \"ticket podunga\" nu dhaan irukku.\n- Moonu \"fix\" commits-um comment line mattum dhaan add pannirukku. \"Processing\" stuck block (E01) code-la innum fix aagala.\n- Password-protected PDF-a status **Done** nu podudhu, aana intake folder-ku copy aagadhu.\n- `.env` (credentials) and oru sender email address irukura log, rendum git-la commit aagirukku.\n- `data/` folder kaali \u2014 queue table illa, so first run-e crash aagum.\n\n**Process notes:**\n- Repo-la oru Python file dhaan, so 2 subagents anuppama naane neraa padichen.\n- Unga answers munnadiye irundhadhaala questions kekkala.\n- Statuses-ku entha screen-um illa, so colour column-la \"none (not shown)\" nu pottiruken.\n\nQUESTIONS: Escalation: who ops calls 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: any statuses or exceptions whose meaning the code doesn't make clear?",
+  "stderr": ""
+}