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

@@ -0,0 +1,31 @@
+{
+  "case": "h-api-sync/full",
+  "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,
+    "misleading status flagged": true,
+    "retry limit": true,
+    "console-only crash output flagged": true
+  },
+  "cost_usd": 1.401677,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-full-k38td_tl\\project",
+  "reply": "`HANDOVER.md` ready, repo root-la irukku. Bot-a run pannala, code-um maathala. Neenga sonna answers-a apdiye use pannen: escalation #rpa-support, ops-ku DB access illa, clear illatha statuses-ku code-oda best reading.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template order apdiye) |\n| Exceptions catalogued | 13 (E01\u2013E13) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot entha window-um drive pannala, API mattum dhaan) |\n| Fix before handover | 21 items |\n\n**Fix-before-handover-la mukkiyamaanavai:**\n- Crash reason, network errors console-ku mattum dhaan pogudhu, log-ku illa. **Failed** aana invoice-ku reason engayum record aagala.\n- `data/output` folder repo-la illa, code-um create pannala. Fresh deploy-la first run-ae stop aagidum.\n- Oru bad row (or existence check timeout) full run-a stop pannidum. Andha row input-la irundha, ovvoru mani run-um adhae row-la stop aagum.\n- 2 \"fix\" commits-um oru comment line mattum dhaan add pannirukku. Retry code initial import-laye irundhadhu.\n- 207 (sila lines reject aanadhu) **Synced**-nu kaattudhu. Ellaa invoice-um Failed aanaalum exit code 0, so Task Scheduler success-nu kaattum.\n- Version README-la mattum dhaan irukku, ops-ku theriyaadhu. Report file-la customer names irukku.\n\n**Also noticed:** `data/output` repo-la illa, adhanaala verify step-la \"path exists or the code creates it\" check adhukku fail aagudhu. Adhai doc-la prerequisite-aa podirukken (section 3, fix item 8). Ops-ku Task Scheduler access irukka-nu neenga sollala, so stop procedure-la \"ops-ku access illana #rpa-support-la kelunga\"-nu potten.\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: any statuses or exceptions whose meaning the code doesn't make clear?",
+  "stderr": ""
+}