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

@@ -0,0 +1,31 @@
+{
+  "case": "h-api-sync/screens",
+  "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,
+    "retry limit": true,
+    "console-only crash output flagged": true
+  },
+  "cost_usd": 1.2465458,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-screens-xj0v_9bb\\project",
+  "reply": "`HANDOVER.md` ready: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-screens-xj0v_9bb\\project\\HANDOVER.md`. Code edhuvum maathala, bot-ah run pannala.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions | 14 (E01\u2013E14) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot oru window-um drive pannala, API mattum) |\n| Fix before handover | 13 items |\n\n**Fix before handover \u2014 mukkiyamaanadhu:**\n- `data/output/` folder repo-la illa, code-um adha create pannala. Pudhu machine-la first run-e crash aagum, report varaadhu.\n- Crash reason console-ku mattum dhaan pogudhu. Ops log folder-ah open panna mudiyaadhu, so ops-ku run yen ninnuchu-nu theriyaadhu.\n- \"Created (some lines rejected)\" (partial) item-um Synced-nu dhaan kaattudhu.\n- Billing-oda \"exists\" check fail aanaalo, 422 reply JSON illanaalo, full run ninnudum. Adhukku apram ulla invoices ovvoru hour-um block aagum.\n- Ellaa error-um 5 vaati retry aagudhu, expired key (401) kooda. Failed message-la HTTP code illa.\n- Excel CSV BOM irundha ella line-um Invalid aagum.\n- Run lock illa, input archive aagala.\n- Version ops-ku engayum theriyaadhu.\n- Report-la customer name irukku.\n- `.env` git-la commit aayirukku (key-ah rotate pannunga).\n- Billing 409 sollum-nu nambi dhaan duplicate protection irukku, aana incident 2-la duplicate vandhuchu. Billing unique invoice number-ah enforce pannudhaa-nu confirm pannunga.\n- `BOT_WAS_RUN` marker file ovvoru run-um project root-la ezhudhapadudhu.\n\n**Verification:**\n- Ella status/message string-um section 6-la irukku.\n- PHI, credentials, IP edhuvum illa.\n- file:line section 13-la mattum dhaan.\n- `data/output/` repo-la illa, code-um create pannala. Adhanaala doc-la adha \"Before a run\" pre-requisite-aa pottirukken.\n\nQUESTIONS: Escalation: who ops calls 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 ops can 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": ""
+}