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
2.8 KiB
JSON
32 lines
2.8 KiB
JSON
{
|
|
"case": "h-web-portal/full",
|
|
"rep": 1,
|
|
"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.2729888,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-0_3xhfnx\\project",
|
|
"reply": "HANDOVER.md ready \u2014 `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-0_3xhfnx\\project\\HANDOVER.md`. Bot-ah run pannala, code-um maathala. Scan, doc writing, final check \u2014 ellaame code, config, log padichu thaan.\n\n| Item | Count |\n|---|---|\n| Sections | 13 (template order same) |\n| Exceptions catalogued | 11 (E01\u2013E11). Ella Dev rows-layum \"enna anuppanum\" irukku |\n| Failure classes | 11 covered, 1 not applicable (F10: batch/queue gate illa) |\n| Fix before handover | 18 items |\n\n**Fix before handover \u2014 mukkiyamaanavai:**\n- Portal maintenance vandha `Downloaded` nu green-la kaattudhu, aana file download aagala.\n- Folder-la endha pudhu CSV vandhaalum success-nu edukkudhu. Late-aa vandha file next provider-ku count aagidum.\n- Re-login fail aanaa run crash aagudhu. Meedhi providers report-la silent-aa missing.\n- Crash, run start/end log-la varadhu. Log-la remark-um illa.\n- `Login Failed` run-um Task Scheduler-la success-nu kaattum.\n- Stop button, watchdog, version number edhuvum illa.\n- `config.yaml`-la use aagaadha plaintext token irukku. Adha rotate panni remove pannanum.\n\n**Ops access:** \"Where to look\" table-la report file, `data/screens/`, `data/downloads/`, `logs/bot.log` mattum thaan point pannirukken. Task Scheduler-um database-um ops-ku access illa, adhanaala andha gaps \"Fix before handover\"-la irukku.\n\n**Also noticed:** `logs/bot.log`-la oru run (2026-09-02) mattum thaan irukku. Adhanaala \"Known incidents\"-la oru incident thaan. Dev team kitta pazhaya logs, reports, Task Scheduler history kekkanum.\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: what do the statuses or exceptions mean where the code doesn't make it clear?",
|
|
"stderr": ""
|
|
} |