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
2.7 KiB
JSON
31 lines
2.7 KiB
JSON
{
|
|
"case": "h-mail-intake/screens",
|
|
"rep": 3,
|
|
"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.2259993999999999,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-mail-intake-screens-57a6wls8\\project",
|
|
"reply": "`HANDOVER.md` ready, repo root-la irukku. Bot-a run pannala; code-um change pannala.\n\n| Item | Result |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 7 (E01\u2013E07) |\n| Failure classes | 11 covered, 1 not applicable (F2: bot entha app window-um drive pannadhu) |\n| Statuses | 5 status-um, ovvoru note variant-um section 6-la irukku |\n| Fix before handover | 15 items |\n\n**Mukkiyamana Fix before handover items:**\n- Oru damaged PDF vandha, adhoda row \"Processing\"-la stuck aagidum. Adhukku apram ovvoru run-um start-laye stop aagum, full intake nikkum (`intake.py:81`, `:74-76`).\n- Mailbox login fail aana last error enga-yum record aagaradhu illa. Silent-a outage nadakkum (`:34-37`, `:77`).\n- Password-protected PDF share-ku copy aagaradhu illa, aana \"Done\"-nu mark aagudhu (`:62-63`).\n- Failed rows-a bot thirumba retry pannadhu (`:78`).\n- Crash aana, read-nu mark aana mails thirumba edukkapadaadhu, referrals lose aagum (`:44`, `:54`).\n- Same peru attachments onnu innonna overwrite pannum (`:50`, `:65`).\n- Mailbox credentials irukkura `.env` git-la commit aagirukku. Password rotate pannanum.\n\n**Also noticed:**\n- Moonu \"fix:\" commits-um comment line mattum dhaan add pannirukku. Section 9-la irukura moonu incidents-um code-la innum fix aagala.\n- Ops-oda ore screen `queue_viewer.xlsx`, adhu repo-la illa. Adhanala status colours confirm panna mudiyala; doc-la \"plain text\"-nu dhaan potturukken.\n- Bot-ku version number illa. Version line-la \"no version number (commit 6a62717)\"-nu potturukken.\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: any statuses or exceptions whose meaning the code doesn't make clear?",
|
|
"stderr": ""
|
|
} |