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

@@ -0,0 +1,34 @@
+{
+  "case": "h-desktop-poster/screens",
+  "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,
+    "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.5256686000000002,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-screens-nnl0sb1u\\project",
+  "reply": "**HANDOVER.md** ready aachu, repo root-la irukku: `HANDOVER.md`. Bot-a naan run pannala, code-um maathala.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 18 (E01\u2013E18) |\n| Failure classes | 12/12 covered, not-applicable onnum illa |\n| Fix before handover items | 20 |\n\nNee kuduthha answers ippadi use pannen:\n- **Escalation:** RPA Support queue-la ticket.\n- **Ops access:** Report screen mattum dhaan ops paakka mudiyum. Log-la mattum irukkura causes ellam *Fix before handover*-ku poyiduchu.\n- **Unclear statuses:** code-oda best reading vechu fill pannen.\n\n**Mukkiyamaana Fix before handover items:**\n- Remittance Errors-la reject aana rows, non-ACH skip aana rows rendum green \"Completed\"-aa dhaan kaattudhu. Unmaiyila rendum post aagala.\n- \"Payment not confirmed after Save\" row red-aa kaattum, aana payment post aagiyirukkalaam. Thirumba post panna double posting risk.\n- Window grab bug (commit 6c4ca09) code-la innum fix aagala. Matching innum plain \"title-la ClaimDesk irukkaa\" check dhaan. Mel, bot ClaimDesk-a mudikkum bodhu machine-la irukkura ellaa ClaimDesk window-um force close aagum.\n- Batch Pending-la maatikittaa adutha upload-a block pannum. Adha clear panna tool illa, refusal message-um screen-la varaadhu.\n- 5-minute watchdog, clinic retry pannum bodhu kooda full run-a kill pannidum.\n- Comma irukkura clinic names split aagudhu. README \"split and skipped\"-nu sollum, aana unmaiyila 3 thadava retry aagi Pending-la nikkum.\n- Launcher, updater, Stop button code indha repo-la illa. Ops-ku safe-aa stop panna vazhi illa.\n\n**Also noticed:**\n- `logs/run_20260901_101500.log:3`-la oru patient name irukku (pazhaya build ezhudhinadhu). Doc-la adha copy pannala.\n- History agent-ku shell access kidaikkala. Git diffs paakka mudiyala, commit messages mattum dhaan paathuchu. Ippo code-la paatha, fix commits ellam file kadaisila comment line mattum add pannina maadhiri theriyudhu. `git show 6c4ca09 d93c7fb 9d39f25 2794ede` run panni confirm pannu.\n\nQUESTIONS: Escalation: who does ops call for a dev issue (team or role, not a personal phone number), 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": ""
+}