Files
Rpa_Skills/tests/evals/results/handoff/h-web-portal-screens-r2.json
VasanthandClaude Opus 5.5 3942fad6cd 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>
2026-10-28 15:01:42 +05:30

32 lines
2.8 KiB
JSON

{
"case": "h-web-portal/screens",
"rep": 2,
"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": false,
"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,
"no-history case says so": true,
"misleading status flagged": true,
"session re-login limit": true,
"screenshots folder": true,
"daily schedule": true
},
"cost_usd": 0.7157622,
"subagents": 0,
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-j_6fk6py\\project",
"reply": "**UNVERIFIED** (doc mattum ezhuthinen. Rule padi bot-a run pannala; ellaame code padichu ezhuthinathu.)\n\n`HANDOVER.md` repo root-la ready: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-j_6fk6py\\project\\HANDOVER.md`\n\n| Check | Result |\n|---|---|\n| Sections | 13, template padi |\n| Exceptions | 9 (E01\u2013E09) |\n| Failure classes | 12/12 covered. F10 partly not applicable (queue illa; mid-run stop-a E07-la cover pannirukken) |\n| Statuses | 8 status/remark combos + \"row missing\" + \"file missing\", ellaam section 6-la iruku |\n| Secrets scan | Token, provider names, log-la irundha NPIs, IPs: doc-la onnum illa. file:line refs section 13-la mattum |\n\n**Fix before handover (14 items), mukkiyamaanavai:**\n1. Portal maintenance-ah irundha \"Downloaded\" green-nu kaattum, aana file download aagaathu (`bot.py:54`)\n2. Late-aa vara CSV adutha provider-oda download-aa count aagidum (`bot.py:63-70`)\n3. Re-login fail aanaa run silent-aa stop aagum; meedhi providers report-la varave varaadhu (`bot.py:96-102`)\n4. `config.yaml`-la commit aana API token iruku (value-a copy pannala)\n5. Version string, watchdog rendum illa. Same day re-run pannaa morning report overwrite aagidum\n\nNotes:\n- Repo-la `bot.py` oru file mattum thaan, git history-um illa. Adhanaala subagents launch pannala, naane direct-aa padichen. Incidents section-la `logs/bot.log`-la irundha oru event mattum thaan iruku.\n- `data/screens` and `data/downloads` folders-ai ops open panna mudiyura \"output files\"-aa eduthukitten. Ops-ku access illana, section 5-a maathanum.\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": ""
}