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

@@ -0,0 +1,34 @@
+{
+  "case": "h-desktop-poster/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,
+    "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.7118525999999998,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-screens-5m9n9yvo\\project",
+  "reply": "I wrote `HANDOVER.md` in the repo root, the only file I changed. I never ran the bot, and I did not read the `.env` values.\n\n| Item | Result |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 19 (E01\u2013E19) |\n| Failure classes | All 12 covered, none marked not applicable |\n| Fix before handover | 22 items |\n\n**Ops-ku periya risk items (Fix before handover-la top):**\n- \"Rejected by app\" and \"Skipped\" rows are shown green as Completed, aana payment post aagala.\n- Oru clinic 3 attempts-um fail aana, Report screen-la row-e varaathu. Log mattum thaan record, adhu ops-ku access illa.\n- Oru red row, illa oru failed clinic irundhaale batch Pending-la nikkum. Adhu next upload-a block pannum. Clear panna function illa, so ovvoru time-um dev venum.\n- Rendu \"fix:\" commits code-la comment mattum thaan add pannirukku: wrong-window grab (7d468fa) and the 1.3.0 update issue (d840396). Window grab code innum maaralai, so that incident can happen again.\n- `.env` (password key irukku) and patient data irukura oru run log rendum git-la committed.\n\n**Also noticed:** the history scan couldn't open the git diffs, so it judged those \"fix:\" commits only from the current code. Dev `git show` panni confirm pannanum. Launcher and update code repo-la illa, so section 10 is partly from the commit note only.\n\nQUESTIONS: Escalation: who ops calls for a dev issue, and how (ticket, chat channel) | Ops access: which of the bot's places ops can open (app screens, output folder, log folder, database) | Unknowns: any statuses or exceptions whose meaning the code doesn't make clear",
+  "stderr": ""
+}