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-api-sync-screens-r4.json

@@ -0,0 +1,31 @@
+{
+  "case": "h-api-sync/screens",
+  "rep": 4,
+  "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,
+    "retry limit": true,
+    "console-only crash output flagged": true
+  },
+  "cost_usd": 1.3588046,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-screens-s_dvo5sy\\project",
+  "reply": "I wrote `HANDOVER.md` in the repo root. Bot-a run pannala; code, config, git history and the log mattum dhaan padichen. Code-ah change pannala. Unga 3 answers apdiye use pannen: escalation-ku RPA Support ticket, ops-ku output folder mattum dhaan access, and unclear statuses-ku code-oda best reading.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template-oda ella sections-um) |\n| Exceptions catalogued | 11 (E01\u2013E11) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot entha window-um drive pannadhu, API calls mattum dhaan) |\n| Fix before handover | 19 items |\n\nFix before handover-la top items:\n- **Billing API key `.env`-la git-ku commit aagiruku.** Key-ah rotate pannanum, file-ah history-la irundhu remove pannanum.\n- Duplicate check-ku error handling illa. Billing slow-aa irundha full run-um nindhurum. Ops paakra report-la reason record aagaadhu.\n- Billing \"partly created\" nu sonnaalum report-la **Synced**-nu dhaan varudhu. Follow-up venum, aana success maadhiri theriyum.\n- Wrong or expired key-ah bot temporary error maadhiri treat pannudhu. Ovvoru invoice-um 5 tries pannitu Failed aagum.\n- `data/output` folder-ah code create pannadhu. Fresh machine-la first run-e crash aagum.\n- Overlapping runs-ku lock illa. Ovvoru hour-um full file-ah thirumba anupudhu.\n- Version README-la mattum dhaan iruku, ops-ku theriyaadhu.\n- Rendu \"fix\" commits-um oru comment line mattum dhaan add pannudhu. Real code changes git-la record aagala.\n\nOps-ku logs access illa, so oru run complete aachaa nu ops-aala uruthiya solla mudiyaadhu. Idhu doc-la Fix item 9-aa iruku.\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 unclear statuses and exceptions mean?",
+  "stderr": ""
+}