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.3 KiB
JSON
34 lines
3.3 KiB
JSON
{
|
|
"case": "h-desktop-poster/full",
|
|
"rep": 1,
|
|
"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": 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": false,
|
|
"Pending batch blocks a new upload": true
|
|
},
|
|
"cost_usd": 1.7011209999999997,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-desktop-poster-full-qgejgjlt\\project",
|
|
"reply": "`HANDOVER.md` ready, repo root-la irukku. Code onnum maathala, bot-a run pannala. Ungaloda answers-a (#rpa-support, ops access, unclear statuses) apdiye use pannen, adhanaala unga kitta question ethuvum ketkala.\n\n| Check | Result |\n|---|---|\n| Sections | 13 (template-la irukka order-laye) |\n| Exceptions | 18 (E01 to E18) |\n| Failure classes | 12/12 covered, \"not applicable\" onnum illa |\n| Statuses | Code ezhudhura ella status-um comment-um Section 6-la irukku |\n| PHI / credentials | Doc-la edhuvum illa; file:line refs section 13-la mattum |\n\n**Fix before handover:** dev team-ku 18 items. Mukkiyamanavai:\n1. **Oru red row (or failed/killed run) vandha batch eppavum open-a irukkum, next upload block aagum.** Database-a kaila edit pannaa dhaan clear aagum. Ops-ku database access illa, so ovvoru failure-kum dev-a wait pannanum.\n2. \"Rejected by app\", \"Skipped\" rows-um green Completed-a dhaan kaatum. Post aagaadha remittance kooda done maadhiri theriyum.\n3. Window-a title-la \"ClaimDesk\" irukka-nu mattum paarthu edukkudhu. \"Fixed\"-nu commit irundhaalum code maaralai, matching apdiye dhaan irukku. Launcher window-um idhula match aagum.\n4. Bot oru remittance-um process pannaama 5 min aanaa, watchdog full run-aiyum kill pannidum; slow-a irukkra healthy run-um kill aagidum.\n5. `logs/run_20260901_101500.log` line 3-la patient name irukku, ops-ku andha folder access irukku. Delete pannalaam-a-nu decide pannunga.\n6. Bot-a safe-a stop panna vazhi illa. Launcher code repo-la illa, adhanaala update fix-um check panna mudiyala.\n\nDoc-la sila points code-a padichu naan purinjukittadhu mattum dhaan, adhai confirm pannala:\n- Wrong password vandha ella clinic-um \"not found in list\"-nu fail aagum.\n- Launcher close panna bot stop aagumaa-nu theriyala.\n\nRepo-la bug fix commits nalu irukku. Adhula save wait 10s-la irundhu 20s aanadhu mattum dhaan current code-la theriyudhu.\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 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": ""
|
|
} |