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

@@ -0,0 +1,31 @@
+{
+  "case": "h-mail-intake/full",
+  "rep": 3,
+  "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.5101666000000002,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-full-jnbdhnw2\\project",
+  "reply": "`HANDOVER.md` ready, repo root la: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-full-jnbdhnw2\\project\\HANDOVER.md`. Bot ah run pannala, code change um illa. Code, log, git history mattum padichen.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template order same) |\n| Exceptions | 8 (E01\u2013E08) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot entha window um drive pannala) |\n| Fix before handover | 14 items |\n\n**Fix list la mukkiyamaanavai:**\n- **Password-protected PDF:** status \"Done\" nu kaattum, aana share folder ku copy aagala.\n- **Processing la stuck aana item:** adhukku apram ella run um block aagum, bot thaane clear pannaadhu. DB access illaama ops ah clear panna mudiyaadhu.\n- **Final mailbox failure and crashes:** log la varaadhu, ops ku onnum theriyaadhu.\n- **Failed item:** bot thirumba try pannaadhu.\n- **Mail lost:** crash aanaa read-mark aana mail poidum.\n- **Same file name:** rendu file overwrite aagum.\n- **`.env` (mailbox password) git la commit aagirukku** (`bc90067`). Password ah rotate pannunga.\n- **Missing viewer + no version:** `queue_viewer.xlsx` repo la illa, version number um illa.\n\n**Also noticed:**\n- Moonu \"fix\" commit um comment line mattum add pannirukku. Code la change illa.\n- `data/` folder ah code create pannaadhu. Doc la adhu prerequisite ah pottirukken.\n- Incident dates record aagala. Log la 2026-09-04 lockout mattum dhaan theriyudhu.\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": ""
+}