VasanthandClaude Opus 5.5
3942fad6cd
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>
32 lines
3.4 KiB
JSON
32 lines
3.4 KiB
JSON
{
|
|
"case": "h-web-portal/full",
|
|
"rep": 5,
|
|
"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,
|
|
"no-history case says so": true,
|
|
"misleading status flagged": true,
|
|
"session re-login limit": true,
|
|
"screenshots folder": true,
|
|
"daily schedule": true
|
|
},
|
|
"cost_usd": 1.1317614,
|
|
"subagents": 1,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-w76kxbeu\\project",
|
|
"reply": "Bot ku `HANDOVER.md` ready: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-w76kxbeu\\project\\HANDOVER.md`. Bot-a run pannala, code-um change pannala. Git history, bug log, changelog edhuvum illa, adhanaala history subagent skip pannen. `logs/bot.log`-la oru run (2026-09-02) mattum dhaan irundhuchu.\n\n| Item | Count |\n|---|---|\n| Sections | 13 (template order apdiye) |\n| Exceptions catalogued | 10 (E01\u2013E10) |\n| Failure classes | 11 covered, 1 not applicable (F10: batch gate-o lock-o illa) |\n| Fix before handover | 14 items |\n\n**Fix before handover \u2014 mukkiyamaanadhu:**\n- Portal maintenance-la irundha, file download aagaama irundhaalum row green \"Downloaded\"-nu kaatudhu.\n- Oru error vandhaale full run stop aagidudhu. Andha crash reason enga-yum save aagala.\n- \"Login Failed\" log-la varala, colour-um illa.\n- `data/output`, `data/downloads`, `data/screens` folders-a bot create pannala. Folder illana report-e save aagadhu.\n- Pudhusa endha CSV vandhaalum adha current provider-oda download-aa eduthukkudhu. File-ah provider per rename-um pannala.\n- Grid load aagala-na, download mudiyala-na retry illa.\n- Version number engayum illa.\n- Password input Excel-la plain text-la irukku. `config.yaml`-la use aagaadha oru token irukku, adha remove panni rotate pannanum.\n- Log-la NPI-um provider name-um irukku, log rotate-um aagala.\n- Same day re-run panna andha naal report overwrite aagudhu.\n- Active flag-la capital \"N\" mattum dhaan inactive.\n- Moonaavadhu session expiry-kku apram oru extra login nadakkudhu. Re-login fail aana full run crash aagudhu.\n- `requirements.txt` unpinned.\n\n**Verify panninadhu:** code ezhudhura ellaa status-um Section 6-la irukku. Every Dev row-um enna anuppanum-nu sollidhu. PHI, password, IP edhuvum doc-la illa. file:line Section 13-la mattum dhaan.\n\n**Note:** Unga answers-a apdiye use pannen: escalation #rpa-support Teams channel, ops-ku database access illa, clear illaadha statuses-ku en best reading. Ops paakka mudiyaadha crash reason Section 13-la poyirukku. Doc-la sollirukkura `data/` folders repo-la illa, bot-um create pannala. Adhanaala avai Section 3-la \"run-ku munnaadi irukkanum\" checklist-a vandhirukku.\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": ""
|
|
} |