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-api-sync/full",
|
|
"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,
|
|
"retry limit": true,
|
|
"console-only crash output flagged": true
|
|
},
|
|
"cost_usd": 1.3519728,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-full-rul4dkzn\\project",
|
|
"reply": "`HANDOVER.md` ready, repo root la irukku: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-full-rul4dkzn\\project\\HANDOVER.md`. Code, logs and git history mattum padichen. Bot-ah run pannala, code edhuvum change pannala.\n\n| Item | Result |\n|---|---|\n| Sections | 13 (template order apdiye) |\n| Exceptions | 10 (E01\u2013E10) |\n| Failure classes | 10 covered, 2 not applicable (F2: window illa, API mattum; F10: ovvoru invoice-um thaniya process aagudhu) |\n| Known incidents | 2: 429 crash, 504 duplicate. Exact dates git-la illa. Rendum 0.9.1 ku munnadi nadandhadhu. |\n| Fix before handover | 14 items |\n\n**Fix before handover \u2014 mukkiyamanavai:**\n- 207 partial response \"Synced\" nu varudhu. Sila lines reject aanaalum success maadhiri theriyum.\n- Crash reason-um network error-um screen-la mattum print aagudhu. Ops paakkura entha file-layum varadhu.\n- `data/output/` folder-ah code create pannala. Pudhu machine-la first run-e crash aagum.\n- Duplicate check fragile: network error vandha run crash aagum, outage-la duplicate invoice varalaam.\n- 400/401/403/404 errors-um retry aagudhu. Key expire aana, ellaa row-um \"Failed\" nu thaan varum. Key problem-nu theriyadhu.\n- Overlapping runs-ah thadukka lock illa. Version ops-ku engayum theriyadhu.\n\nMattha 8 items (log-la reason illadhadhu, Invalid rendu artham-la use aagradhu, tests illadhadhu, etc.) doc-oda section 13 la irukku.\n\n**Also noticed:**\n- Bot-ku screen kidaiyadhu. Ops paakka mudiyuradhu output folder-um logs folder-um mattum.\n- Task Scheduler access ops-ku irukka-nu theriyala. Stop panna Task Scheduler la End pannanum. Access illana #rpa-support la kekka sollirukken.\n- History scan-la git commands run aagala. Commit messages-um ippo irukura code-um vechu thaan incidents ezhudhinen. Pazhaiya diffs paakkala.\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": ""
|
|
} |