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-desktop-poster-screens-r5.json

@@ -0,0 +1,34 @@
+{
+  "case": "h-desktop-poster/screens",
+  "rep": 5,
+  "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,
+    "comma rule before a run": true,
+    "how to stop": true,
+    "not-confirmed row: check ClaimDesk first": true,
+    "hidden tech comments flagged": true,
+    "Pending batch blocks a new upload": true
+  },
+  "cost_usd": 1.8868500000000001,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-screens-tyvh8gj0\\project",
+  "reply": "`HANDOVER.md` ready, repo root la irukku. Bot-a run pannala, code + git history + log mattum padichu ezhudhinen. Code change edhuvum illa.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 13 (E01\u2013E13) |\n| Failure classes | 12/12 covered, 0 not applicable |\n| Fix before handover | 20 items |\n\n**Fix before handover la mukkiyamanavai:**\n- Neenga sonna \"output folder\" ku indha bot edhuvum ezhudhuradhu illa. Ops paakka mudinja ore idam launcher la irukkura Report screen dhaan.\n- ClaimDesk reject panna payment-um green \"Completed\" nu dhaan kaattum.\n- Ore oru red row irundha kooda batch Pending la nikkum, adutha ella run-um block aagum. Clear panna DB edit dhaan vazhi, adhanaala dev ticket venum.\n- Window-match fix (8fa51ac) git la commit irukku, aana code la apdiye dhaan irukku.\n- `.env` (plaintext password oda) and patient name irukkura log file rendum git la commit aagirukku. Password-a rotate pannunga.\n- Log la irukkura lines indha code ezhudhave mudiyaadhu. Adhanaala deploy aana build indha repo illa pola.\n\n**Assumption:** \"Ops access\" answer bot screens pathi mattum dhaan sonnuchu. Adhanaala ops ClaimDesk-a normal user-aa open pannuvaanga nu eduthukitten. E01/E02/E03 la \"ClaimDesk la check pannunga\" step adha nambi dhaan irukku. Ops ku ClaimDesk access illana sollunga, andha rows-a Dev ku maathidren.\n\nQUESTIONS: Escalation: who does ops call for a dev issue, and how (ticket, chat channel)? | Ops access: which of the bot's places can ops open \u2014 the app's screens, the output folder, the log folder, the database? | Unknowns: what do the statuses or exceptions mean where the code doesn't make it clear?",
+  "stderr": ""
+}