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>
31 lines
3.0 KiB
JSON
31 lines
3.0 KiB
JSON
{
|
|
"case": "h-mail-intake/full",
|
|
"rep": 2,
|
|
"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,
|
|
"stuck Processing item blocks the queue": true,
|
|
"20 MB limit": true
|
|
},
|
|
"cost_usd": 1.3097480000000001,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-full-oq0v6p0_\\project",
|
|
"reply": "`HANDOVER.md` ready, repo root la iruku \u2014 oru file mattum dhaan maathinen, code edhuvum touch pannala, bot-ah run pannala. Neenga sonna answers use panniten: escalation = RPA dev team on #rpa-support; ops-ku log folder and shared intake folder mattum, database illa; theliyaadha items-ku code-oda best reading.\n\n| Item | Count |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 8 (E01\u2013E08) |\n| Failure classes covered | 11 of 12 \u2014 F2 not applicable (indha bot entha window-um drive pannala) |\n| Fix before handover items | 19 |\n\n**Fix before handover \u2014 mukkiyamaanadhu:**\n- **Moonu \"fix\" commits-um oru comment mattum dhaan add pannirukku.** Stuck-in-Processing, encrypted-PDF, mailbox-password moonu incidents-um innum varum.\n- Oru item Processing-la stuck aana, ovvoru run-um stop aagum, forever. Ops-ku database access illa, so dev dhaan release pannanum.\n- Password potta PDF-ku status **Done** nu varudhu, aana adhu copy aagala.\n- Failed items-ah bot thirumba retry pannadhu.\n- \"Mailbox unreachable\" log-la ezhudhala. Mail fetch pannumbodhu crash aana, antha emails thadayame illaama kaanama pogum.\n- Ore file name-la rendu attachment vandha, rendaavadhu modhalaavadhai overwrite pannum. Path-oda vara file name-um check pannala.\n- `queue_viewer.xlsx` README-la irukku, aana repo-la illa. Ops-ku sender/subject theriyave theriyaadhu.\n- Version number engayum illa.\n- `.env` git-la commit aagirukku \u2014 credentials-ah rotate pannunga. Log-la oru sender email address-um irukku.\n\n**Rendu vishayam theriyala, best reading use panninen:**\n- `BOT_WAS_RUN` marker file edhukku-nu theriyala. Best reading: \"oru thadava run aachu\" flag.\n- Log-la oru line irukku, ippo irukura code adha ezhudhuradhu illa.\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 where the code doesn't make it clear?",
|
|
"stderr": ""
|
|
} |