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.2 KiB
JSON
31 lines
3.2 KiB
JSON
{
|
|
"case": "h-api-sync/screens",
|
|
"rep": 5,
|
|
"passed": false,
|
|
"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": false,
|
|
"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": 0.721561,
|
|
"subagents": 0,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-screens-0b_hw7xu\\project",
|
|
"reply": "I've written `HANDOVER.md` at the repo root (Thanglish summary). Code edhuvum maathala, bot-ah run pannala \u2014 code, git history, logs mattum padichen. Repo-la oru script (`sync.py`) mattum dhaan irundhudhu, so skill sonna rendu subagents anuppama naane direct-ah padichen.\n\n| Item | Count |\n|---|---|\n| Sections | 13 (template order-la) |\n| Exceptions | 10 (E01\u2013E10) |\n| Failure classes | 12-la 10 cover aachu; F2 (windows drive pannala), F5 (billing confirm pannina apram dhaan Synced) not applicable |\n| Fix before handover | 11 items |\n\n**Fix before handover \u2014 mukkiyamaanavai:**\n- Billing \"partly accepted\" (207) invoice-um **Synced**-nu kaattudhu, but sila lines reject aagirukkum, yaarum follow-up panna maattaanga.\n- Network error, crash reason ellam console-ku mattum print aagudhu; log-la status mattum dhaan irukku, so cause kaanaama poidudhu.\n- Excel \"CSV UTF-8\"-ah save pannina, ella row-um Invalid \"missing invoice_no\"-nu varum.\n- Oru network blip vandhaa run naduvula nikkum; report-la \"run mudinjudhu\"-nu oru line-um illa.\n- `data/output` folder-ah code create pannaadhu, so folder illaati report-e varaadhu.\n- `.env` (billing API key) git-la commit aagirukku. Key-ah rotate pannanum, history-la irundhu remove pannanum. Doc-la value podala.\n- Matha items: 401/403 error billing outage maadhiri retry aagudhu, rendu hourly run overlap aagalaam, version ops-ku theriyaadhu, last try-ku apram veena 32 s wait.\n\nVerify pannadhu: ella status string-um Section 6-la irukku. File:line references Section 13-la mattum. PHI, credentials, IP edhuvum illa. Doc-la sonna ella path-um repo-la irukku illa code create pannum \u2014 `data/output` mattum illa, adhu Fix #9-la irukku.\n\nUnga answers apply pannadhu: escalation-ku RPA Support queue ticket. Ops-ku output folder mattum dhaan access, so log-la mattum theriyura causes ellam Fix list-ku poyiduchu. Status meaning code-la irundhu naane decide panninen.\n\nQUESTIONS: Escalation: who ops calls for a dev issue (team or role, not a personal phone number), and how (ticket, chat channel)? | Ops access: which of the bot's places ops can 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": ""
|
|
} |