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-packaged-desktop-full-r5.json

@@ -0,0 +1,32 @@
+{
+  "case": "h-packaged-desktop/full",
+  "rep": 5,
+  "passed": false,
+  "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,
+    "display scaling rule": true,
+    "version check": false,
+    "shortcut prerequisite": true,
+    "silent update failure flagged": true
+  },
+  "cost_usd": 1.5265358,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-full-8nf_6t9w\\project",
+  "reply": "`HANDOVER.md` ready, repo root la iruku. Bot-a run pannala, code-um maathala; output idhu oru file mattum dhaan.\n\n| Check | Result |\n|---|---|\n| Sections | 13 (template order maathama) |\n| Exceptions | 17 (E01\u2013E17). Every Dev row-um enna send pannanum nu sollum. |\n| Failure classes | 12/12 map aagiruchu. 10 full-ah covered. F8 partly not applicable (auto-rerun, watchdog rendum illa). F10 queue-ah not applicable (batch illa; adhoda blocking case E06-la cover aagudhu). |\n| Statuses | 6 Result/Note combos + \"no Reconcile file\" case. Bot write panra ellaa string-um irukku. |\n| PHI / secrets | Log-la irundha transaction ID-um payee name-um copy pannala. `.env` open pannave illa. |\n| Fix before handover | 18 items |\n\n**Ops-ku mukkiyamaana gaps:**\n- \"Posted\" na bot Save click pannuchu nu mattum dhaan artham, save aachaa nu check pannala. Successful post aana row-um Result \"Missing\"-nu dhaan kaattum.\n- Save button kidaikkalana, half-filled form LedgerPro-la open-ave irukkum; next rows adhu mela type aagalaam.\n- Crash aana Reconcile file illa; record log-la mattum dhaan irukkum. Run-level errors (shortcut illa, Export fail, bad amount) enga-um log aagadhu.\n- Bot version enga-um theriyaadhu. Launcher update error-um silent-ah hide pannidum.\n- Build spec full-ah comment-out aagi iruku. Ennoda reading: \"assets\" fix repo-la illa.\n- Code-la illadha payee name ondru 2026-09-05 log-la iruku. Adhanaala running exe indha repo-voda match aagaama irukkalaam.\n\n**Path check:** `data\\output` folder repo-la illa, code-um create pannala. Adhanaala doc \"Before a run\"-la ops-a create panna sollirukku.\n\n**Assumptions:** Ops-ku bot-a illama LedgerPro access irukkaa nu theriyala, adhanaala E06, E07, E11 \"LedgerPro check pannunga, illana #rpa-support\". Bot-ku own screen illa, so \"Where to look\" output folder-um logs folder-um mattum point pannum.\n\nQUESTIONS: Who does ops call for a dev issue (team or role), and how (ticket, chat channel)? | Which of the bot's places can ops open: the app's screens, the output folder, the log folder, the database? | Are there any statuses or exceptions whose meaning the code doesn't make clear?",
+  "stderr": ""
+}