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.7 KiB
JSON
32 lines
2.7 KiB
JSON
{
|
|
"case": "h-web-portal/full",
|
|
"rep": 4,
|
|
"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.0619698000000002,
|
|
"subagents": 1,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-_jnxboxu\\project",
|
|
"reply": "`HANDOVER.md` ready in the repo root: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-web-portal-full-_jnxboxu\\project\\HANDOVER.md`. Bot-ah run pannala, code-um change pannala, only intha oru file dhaan ezhudhinen.\n\n| Item | Result |\n|---|---|\n| Sections | 13 |\n| Statuses | 8 (bot ezhudhra 7 status + \"Login Failed\" + \"no row\" case), ellam vandhiruku |\n| Exceptions | 10 (E01\u2013E10). Dev rows-la enna anuppanum-nu sollirukku |\n| Failure classes | 12/12 covered. F2, F8, F10, F12 la oru part mattum not applicable (reason doc-la irukku) |\n| Fix before handover | 15 items |\n\n**Mukkiyamana fixes:**\n1. Portal maintenance page vandha \"Downloaded\" (green)-nu podudhu, aana file download aagala.\n2. Edhavadhu unexpected error vandha run full-ah stop aagudhu. Log-la edhuvum record aagala.\n3. Late-ah vandha CSV adutha provider-ku count aagidum. File name-la NPI illa.\n4. Folders bot create pannadhu. `data/output` illana andha naal report full-ah poyidum. Repo-la `data/` folders eppovum illa, adhanaala doc ops-ah create panna solludhu.\n5. Portal password input Excel-la plain text-la irukku. Unused `api_token` `config.yaml`-la irukku (value-ah doc-la copy pannala).\n\n**Gaps:**\n- Git history illa, oru log run (2026-09-02) mattum dhaan irukku. Adhanaala Known incidents-la oru row dhaan.\n- Ops access-ku database illa, aana indha bot-ku DB-ve illa.\n- Unclear statuses-ku code padichu best reading use pannen.\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": ""
|
|
} |