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

@@ -0,0 +1,34 @@
+{
+  "case": "h-desktop-poster/full",
+  "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": 2.0747394,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-full-nuvq4d1l\\project",
+  "reply": "`HANDOVER.md` ready in the repo root. Bot-a run pannala, code-um git history-um mattum padichen. Code edhuvum maathala.\n\n| Item | Count |\n|---|---|\n| Sections | 13 (template order) |\n| Exceptions catalogued | 20 (E01\u2013E20) |\n| Failure classes | 12/12 covered, 0 \"not applicable\" |\n| Fix before handover | 17 items |\n\n**Mukkiyamaana findings:**\n- **\"Fix\"-nu label panna 4 commits-um comment mattum add pannudhu.** Window grab, save wait, comma split, 1.3.0 update: naalum innum open. Save wait import-la irundhe 20s dhaan.\n- **Green \u2260 posted.** \"Rejected by app\" and \"Skipped\" rows-um green Completed-aa dhaan kaatum.\n- **Oru red row, illa watchdog kill aana oru run, next upload-a block pannidum.** Ops-ku DB access illa, so ovvoru dhadavaiyum dev dhaan batch-a clear pannanum.\n- **Watchdog 5 min.** Login, retries edhuvum progress-aa count aagadhu, so normal retries-um run-a kill pannidum.\n- **Repo-la PHI irukku.** `.env` file-um, oru patient name irukura oru run log-um git-la tracked. Adhu Fix item 16-la irukku; doc-la copy pannala.\n- **Launcher code repo-la illa.** Adhanala \"launcher-a close panna bot stop aagumaa\" and update steps unknown-nu mark panni irukken.\n\n**Fix before handover (17):**\n1. Status map rejected/skipped rows-a green-aa kaatudhu\n2. Save-confirm ClaimDesk-la re-check pannala\n3. Title substring-la window match aagudhu\n4. taskkill ella ClaimDesk-ayum kill pannudhu\n5. Comma/semicolon split\n6. Cutoff date text-aa compare aagudhu\n7. Watchdog heartbeat payment-ku mattum\n8. Zero rows irundhaalum clinic Success; sign-in check illa\n9. DB/schema-va code create pannala\n10. Start-up errors log-la varala; unused .env keys\n11. Stop button illa\n12. Open batch upload-a block pannudhu, resume illa\n13. Hidden columns, clinic/batch status kaatala\n14. Row-la timestamp illa, \"[ERROR] [ERROR]\", RUN SUMMARY misleading, retry-la duplicate rows\n15. Launcher/update code repo-la illa\n16. .env and PHI log git-la; password plain-text Excel-la\n17. Rendu runs ore nerathula start aaga lock illa\n\nUngal answers apply panniten: escalation #rpa-support, \"Where to look\" Report screen + logs mattum, DB items \"Fix before handover\"-la. Andha moonu questions-ku neenga munnadiye answer koduthadhaala, ask step-a skip panniten.\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: what do the statuses or exceptions whose meaning the code doesn't make clear actually mean?",
+  "stderr": ""
+}