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

@@ -0,0 +1,32 @@
+{
+  "case": "h-web-portal/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,
+    "no-history case says so": true,
+    "misleading status flagged": true,
+    "session re-login limit": true,
+    "screenshots folder": true,
+    "daily schedule": true
+  },
+  "cost_usd": 1.2585940000000002,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-mm0v52p2\\project",
+  "reply": "`HANDOVER.md` ready, repo root-la irukku: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-mm0v52p2\\project\\HANDOVER.md`. Bot-a naan run pannala; code, config, README and log mattum padichen.\n\n| Item | Result |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 10 (E01\u2013E10) |\n| Failure classes | 11 cover aachu, 1 not applicable (F10: batches illa, ovvoru run-um fresh-a start aagum) |\n| Fix before handover | 15 items |\n| Checks | Ellaa status string-um section 6-la irukku. file:line section 13-la mattum dhaan. URL, IP, token, password, PHI ethuvum illa. |\n\n**Fix before handover \u2014 mukkiyamaanavai:**\n1. Portal maintenance-la file download aagalainnaalum \"Downloaded\" (green)-nu kaattudhu.\n2. Edhaavadhu oru pudhu CSV vandhaale success-nu edukkudhu. Files provider vaariya rename aagaradhilla.\n3. Remark log-la varala. Run crash aana cause engeyum record aagaradhilla.\n4. Login fail log-la varala. Andha rows-ukku colour-um illa.\n5. Page-load timeout-um illa, watchdog-um illa. Run forever hang aagalaam.\n6. `logs` and `data/*` folders-a bot create pannaadhu.\n7. Version number illa.\n8. Same day re-run panna morning report overwrite aagidum.\n9. Inactive flag-a exact-a capital \"N\"-a irundha mattum dhaan skip pannum.\n10. `config.yaml`-la use aagaadha API token plaintext-la irukku; portal password input Excel-la irukku.\n11. Clean stop illa.\n12. README-la sonna maadhiri ellaa failure-kkum screenshot edukkaradhilla.\n13. \"No Data\" portal-oda default date range-a nambiyirukku.\n14. Log-la provider name-um NPI-yum ovvoru line-layum varudhu.\n\n**Note:**\n- Incident history: 2026-09-02 log-la oru run mattum dhaan irukku. Andha naal oru Error vandhuchu, adhu partly ops handle panna koodiyadhu.\n- Nee \"output folder\" mattum sonna. Naan `data/downloads` and `data/screens`-um ops open pannalaam-nu assume pannen.\n- Bot-ah stop panna doc enna solludhu-na: bot open panna Chrome window-a close pannunga. Task Scheduler-la task-a end panna report ezhudhaadhu. Idhu code-a padichu naan purinjukittadhu; test pannala.\n- Unga instruction padi, statuses-ku code-oda best reading-a dhaan use pannen.\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 any statuses or exceptions mean whose meaning the code doesn't make clear?",
+  "stderr": ""
+}