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.0 KiB
JSON
32 lines
3.0 KiB
JSON
{
|
|
"case": "h-web-portal/screens",
|
|
"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.0813546,
|
|
"subagents": 1,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-syegby90\\project",
|
|
"reply": "`HANDOVER.md` ready \u2014 project root la irukku (`C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-screens-syegby90\\project\\HANDOVER.md`). Bot-ah run pannala, code edit pannala; code, config, README, log mattum read pannen.\n\n| Check | Result |\n|---|---|\n| Sections | 13 (template-la irukka ella section-um, same order) |\n| Exceptions catalogued | 11 (E01\u2013E11) |\n| Failure classes | 11 covered, 1 not applicable (F10: batch/lock illa) |\n| Statuses | Code ezhudhura 8 status/remark combinations-um irukku, plus \"row-e illa\" case |\n| Fix before handover | 14 items |\n\n**Doc ezhudhumbodhu naan eduththa decisions:**\n- Unga \"No logs folder\" answer-ah, `logs/bot.log` ops-ku open panna mudiyadhu-nu eduthukitten. Bot actually andha file ezhudhudhu. Adhanaala *Where to look* table report, `data/screens/` and `data/downloads/` mattum point pannudhu.\n- Code-la theliva illadha ore status: \"Downloaded \u2013 portal maintenance - no file\". Idhu green-ah show aagum, aana file download aagala. Adhanaala \"needs follow-up\"-nu document panniten (E07), fix list-la #1 ah pottiruken.\n\n**Fix before handover \u2014 mukkiyamanavai:**\n- #1 Maintenance banner vandhaalum status \"Downloaded\" (green) nu varum, file illama.\n- #2 Edhir paakkadha error vandha run nikkum. Meedhi providers-ku report-la row-e varadhu, cause-um log aagadhu.\n- #4 Same day re-run panna andha naal report overwrite aagum.\n- #5 CSV files provider per rename aagadhu, so endha file endha provider-nu theriyaadhu.\n- #8 Watchdog illa, clean-ah stop panna vazhi illa.\n- #14 \"Login Failed\" rows colour illama varum, red illa.\n\n**Also noticed:** `config.yaml`-la oru `api_token` plain text-la irukku, code adha use pannala (fix #11). Value-ah doc-la copy pannala. Andha token-ah rotate pannidunga.\n\nQUESTIONS: Escalation: who does ops call for a dev issue (team or role), 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": ""
|
|
} |