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>
34 lines
3.1 KiB
JSON
34 lines
3.1 KiB
JSON
{
|
|
"case": "h-desktop-poster/full",
|
|
"rep": 4,
|
|
"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,
|
|
"comma rule before a run": true,
|
|
"how to stop": true,
|
|
"not-confirmed row: check ClaimDesk first": true,
|
|
"hidden tech comments flagged": true,
|
|
"Pending batch blocks a new upload": true
|
|
},
|
|
"cost_usd": 1.9490990000000001,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-full-5atujyru\\project",
|
|
"reply": "I wrote `HANDOVER.md` in the repo root. Bot-a run pannala, code change edhuvum illa, verum read-only scan mattum dhaan.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 19 (E01\u2013E19) |\n| Failure classes | 12/12 covered, not-applicable 0 |\n| Fix before handover | 20 items |\n\n**Fix before handover \u2014 mukkiyamanavai:**\n- Oru red Error row irundhaale andha batch Pending-laye nikkum. Pending batch iruntha next upload-um refuse aagum. Release panna ops-ku screen illa; ovvoru thadavaiyum dev dhaan venum.\n- \"Rejected by app\" and \"Skipped\" rows green Completed-aa kaattudhu, aana avai post aagala.\n- Watchdog (5 min la stop pannum timer) payment-ku mattum dhaan reset aagudhu. Normal-aa slow sign-in or retry nadakkumbodhu kooda run-a stop pannidum. Appo ClaimDesk open-aave irukkum, batch Pending aagum.\n- Wrong-window bug (\"fix\" commit d9a2483) and update bug (d84ff92): rendu commit-um oru comment line mattum dhaan add pannirukku, code change illa. Rendum innum open.\n- Bot ella ClaimDesk window-um force-close pannudhu, user-oda sondha session-um serthu.\n- Clinic name-la comma or semicolon irundha andha name-a split pannidum. README-la \"one clinic per row\" nu sonnalum andha split nadakkum.\n- `&` name ulla clinic-um fail aagudhu.\n- Cutoff date-a text-aa compare pannudhu, adhanaala date order thappa varalaam.\n- `.env`-um, oru patient name ulla run log-um git-la commit aagi irukku. Andha log-a history-la irundhu purge pannanum.\n\nUnga answers-a use pannen:\n- **Escalation:** RPA dev team, #rpa-support channel.\n- **Ops access:** Report screen and logs folder mattum. DB-la mattum irukka causes ellam Fix list-ku pochu.\n- **Unclear statuses:** code padi ezhudhinen. \"Pending\" file status-a current code ezhudhaadhu.\n\nQUESTIONS: Escalation: who does ops call for a dev issue, 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?",
|
|
"stderr": ""
|
|
} |