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

@@ -0,0 +1,34 @@
+{
+  "case": "h-desktop-poster/screens",
+  "rep": 2,
+  "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.5344808,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-screens-qbv9h8s2\\project",
+  "reply": "I've written `HANDOVER.md` in the repo root. Itha la, ops-ku code theriyama oru check fail aana: enna nadanthuchu, enga record aagum, bot retry pannucha, ops fix pannanuma illa dev-a koopidanuma - ellam irukku. Bot-a naan run pannala, code-um maathala.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template order) |\n| Exceptions catalogued | 18 (E01\u2013E18) |\n| Failure classes | 12/12 covered, 0 not applicable |\n| Statuses | 7 on the Report screen + 4 clinic/batch statuses that ops can't see |\n| Fix before handover | 20 items for dev, each with file:line |\n\n**Ops-ku romba mukkiyamana dev fixes:**\n- Oru red row irundha kooda, antha machine la next run start aagadhu. Dev database-a edit pannura varaikkum ippadiye nikkum. Clear pannura tool illa.\n- \"Remittance Errors on posting\" rows green-a theriyum, aana avanga post aagave illa.\n- 5 nimisham pudhu check row varalanna watchdog run-a kill pannidum. Login, retry, empty clinic ithellam progress-a count aagadhu.\n- Oru clinic full-a fail aana Report screen la row-e varadhu. Logs, database ops-ku access illa, adhanala ops-ku antha reason theriyave theriyadhu.\n- Commit 34cae4a \"fixed\"-nu sollum, aana bot innum title la \"ClaimDesk\" irukka mudhal window-a eduthukkum. Athu Poster launcher window-avum irukkalam.\n- Stop button illa. Launcher code repo la illa, adhanala Poster window-a close panna bot nikkuma-nu confirm panna mudiyala.\n- Sample log `logs/run_20260901_101500.log` la oru patient name irukku. Scrub pannanum.\n\n**Also noticed:** Git commands-a denied aachu, adhanala history `.git/logs/HEAD` file-ayum code la irukka commit comments-ayum vachu thaan padichen. Commit diffs-a naan paakkala.\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 ops can 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": ""
+}