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-web-portal-screens-r3.json

@@ -0,0 +1,32 @@
+{
+  "case": "h-web-portal/screens",
+  "rep": 3,
+  "passed": false,
+  "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": false,
+    "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,
+    "no-history case says so": true,
+    "misleading status flagged": true,
+    "session re-login limit": true,
+    "screenshots folder": true,
+    "daily schedule": true
+  },
+  "cost_usd": 1.2818285999999999,
+  "subagents": 2,
+  "work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-w1v4yfhg\\project",
+  "reply": "`HANDOVER.md` ready \u2014 repo root la irukku: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-w1v4yfhg\\project\\HANDOVER.md`. Code mattum padichen, bot-a run pannala, code edhuvum maathala.\n\n**Scan la kandupidichadhu:**\n- Idhu single Python script. Task Scheduler daily 07:00 ku start pannum, Chrome open panni payer portal la irundhu ovvoru provider-oda remittance report-um CSV-a download pannum.\n- Result file: `data/output/Download_Report_<date>.xlsx` (Status + Remarks). Database illa, screen illa, watchdog illa.\n- History romba kammi: log la 2026-09-02 oru run mattum dhaan irukku (session expire aagi oru provider Error).\n- Repo la `data/` folders illa, code-um adha create pannadhu. `data/output` illana andha naal result file full-a pogum.\n\n**Doc summary:**\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 11 (E01\u2013E11) |\n| Failure classes | 11 cover aachu, 1 N/A (F10: batch gate illa) |\n| Fix before handover | 13 items |\n\n**Fix before handover \u2014 mukkiyamaana items:**\n- Maintenance banner vandha kooda status green \"Downloaded\" nu varudhu, aana file illa.\n- Edhaavadhu pudhu CSV vandhaale success nu edukkudhu, so oru provider file next provider-ku credit aagalaam.\n- Run crash aana meedhi providers result file la silent-a missing. Crash reason endha file-layum record aagaradhilla.\n- Login Failed rows ku colour-um illa, log line-um illa.\n- Folders auto-create aagaradhilla.\n- Retry info log la mattum dhaan irukku, ops adha open panna mudiyaadhu.\n- Version string illa. Watchdog-um illa.\n- Run-a correct-a stop panna vazhi illa (stop panna andha run-oda result file save aagaadhu).\n- Security: password input Excel la irukku, use aagaadha API token config la plain text-a irukku, provider names log la poguthu.\n\n**Neenga confirm pannanum:**\n- \"No logs folder\" nu sonnadha \"ops ku logs folder access illa\" nu eduthukitten, yen-na repo la `logs/bot.log` irukku. Log la mattum irukkura info ellam dev kitta ticket la ketka sollirukken.\n- `data/screens` screenshots-um, `data/downloads` CSVs-um ops paarkalaam nu assume pannen.\n- Ops ku Task Scheduler access irukkaa nu theriyala, so stop/re-run-ku \"illana RPA Support ticket podunga\" nu ezhudhirukken.\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 whose meaning the code doesn't make clear (e.g. \"Downloaded - portal maintenance - no file\", uncoloured \"Login Failed\")?",
+  "stderr": ""
+}