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-web-portal-screens-r1.json

@@ -0,0 +1,32 @@
+{
+  "case": "h-web-portal/screens",
+  "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,
+    "no-history case says so": true,
+    "misleading status flagged": true,
+    "session re-login limit": true,
+    "screenshots folder": true,
+    "daily schedule": true
+  },
+  "cost_usd": 1.1106014,
+  "subagents": 1,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-_682nhjg\\project",
+  "reply": "`HANDOVER.md` ready, bot repo root-la irukku. Bot-a run pannala, code-um change pannala. Bot code, README, config and log mattum read panniten.\n\n| Item | Count |\n|---|---|\n| Sections | 13, template order-la |\n| Exceptions catalogued | 11 (E01\u2013E11) |\n| Statuses | 8. Code ezhudhura ella status + remark combination-um irukku |\n| Failure classes | 11 covered, 1 not applicable (F10: batch, queue, lock edhuvum illa) |\n| Fix before handover | 16 items |\n\n**Top Fix before handover items:**\n- Portal maintenance-la file download aagala, aana row green \"Downloaded\"-nu kaatudhu.\n- Folder-la pudhusa vara endha CSV-yum current provider-oda download-nu count aagudhu. Late-aa vandha file adutha provider-ku credit aagidum.\n- \"Login Failed\" rows-ku colour illa, log-layum varadhu.\n- Bot crash aana, meedhi providers report-la missing. Reason report-layum log-layum illa.\n- Bot-ku version number illa, watchdog illa, Stop button illa.\n- Folders-a bot create pannadhu. `data/output` illana report save aagadhu, `logs` illana bot start-e aagadhu.\n\n**Unga answers-a naan eppadi eduthukitten:**\n- \"No logs folder\"-a, ops-ku logs folder open panna access illa-nu eduthukitten. Repo-la `logs/bot.log` irukku, so log-a \"Where to look\"-la podala, Fix item-aa pottirukken.\n- Bot-ku sondha screen illa, Chrome mattum dhaan drive pannudhu. So \"bot's own screens\"-a `data/screens/` screenshots-nu eduthukitten.\n\n**Code mattum padichu ezhudhinadhu, test pannala:**\n- Bot-a stop panna, adhu open panna Chrome window-a close pannanum. Appo idhuvarai mudincha providers-oda partial report save aagum.\n- History illa: git, changelog edhuvum illa. Known incidents-la log-la irukkura 2026-09-02 run mattum dhaan irukku.\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": ""
+}