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

@@ -0,0 +1,32 @@
+{
+  "case": "h-packaged-desktop/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,
+    "display scaling rule": true,
+    "version check": true,
+    "shortcut prerequisite": true,
+    "silent update failure flagged": true
+  },
+  "cost_usd": 1.5397530000000001,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-screens-u9wl16io\\project",
+  "reply": "`HANDOVER.md` ready, repo root la irukku: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-screens-u9wl16io\\project\\HANDOVER.md`. Code edhuvum change pannala, bot-a run pannala.\n\n| Check | Result |\n|---|---|\n| Sections | 13 (template order maari) |\n| Exceptions catalogued | 13 (E01\u2013E13) |\n| Failure classes | 12/12 covered, \"not applicable\" onnum illa |\n| Fix before handover | 17 items |\n| Leak scan | PHI, URL, IP, key edhuvum illa; file:line section 13 la mattum |\n\n**Ops-ku mukkiyamaana vishayangal:**\n- Bot-ku sondha screen illa: window illa, Stop button illa, version kaatra edamum illa. Adhanaala ops paakka mudinjadhu output folder la irukkura `Reconcile_*.xlsx` file mattum dhaan.\n- Save click aana odane bot `Posted` nu ezhudhidum, save aachaannu check pannaadhu. Adhanaala re-run pannradhukku munnaadi LedgerPro la check pannanum (E04, E05, E07).\n- Run crash aana output file varaadhu. Adhukku munnaadi post aanadhu ellaam LedgerPro la appadiye irukkum.\n- History la 3 \"fix\" commits irukku. Adhula 2 code la illa, comment mattum dhaan add aagirukku: launcher innum update error-a maraikkudhu, build spec la assets line innum commented out. Section 9 and 13 la idha open-aa dhaan pottirukken.\n\n**Fix before handover (17), short-aa:**\n1. `Posted` save confirm pannaama ezhudhapadudhu\n2. Fixed 15 s / 10 s waits; export file pazhasaannu check illa\n3. Crash aana output-um illa, reason-um illa; watchdog-um illa\n4. Oru vagai error mattum dhaan catch aagudhu\n5. Save fail aana form open-aave irukku, adutha rows-um fail aagum\n6. Display scaling / resolution check illa\n7. Post aana rows-um `Missing` nu dhaan kaattudhu; colours illa\n8. Log, screenshots ops-ku edukka mudiyaadhu; screenshots overwrite aagudhu\n9. `logs\\`, `data\\output\\` folders munnaadiye irukkanum\n10. Statement input validation illa\n11. Build spec la assets bundle aagala\n12. Launcher update errors-a maraikkudhu\n13. Launcher version compare (`!=`), checksum illa\n14. Version kaatra edam illa\n15. Double-post guard illa\n16. `requirements.txt` la versions pin pannala\n17. `BOT_WAS_RUN` marker ezhudhapadudhu, aana yaarum padikkala\n\nUnga answers-a apdiye use pannen: escalation = RPA Support queue ticket, ops-ku output folder mattum. Logs ops-ku edukka mudiyaadhadhaala \"Where to look\" la vekkala, Fix list la pottirukken (#8).\n\nQUESTIONS: Escalation: who does ops call for a dev issue (team or role), 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 mean where the code doesn't make it clear?",
+  "stderr": ""
+}