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
2.9 KiB
JSON
31 lines
2.9 KiB
JSON
{
|
|
"case": "h-api-sync/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,
|
|
"known incidents from history": true,
|
|
"misleading status flagged": true,
|
|
"retry limit": true,
|
|
"console-only crash output flagged": true
|
|
},
|
|
"cost_usd": 1.4335914,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-api-sync-full-hx49oaht\\project",
|
|
"reply": "I wrote `HANDOVER.md` in the repo root. I didn't run the bot, and no code was changed. The skill's questions were answered from your message, so I didn't stop to ask.\n\n| Item | Result |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 11 (E01\u2013E11) |\n| Failure classes | 11 covered, 1 not applicable (F2: the bot has no window and drives no app) |\n| Fix before handover | 18 items |\n\nFix before handover-la mukkiyamaanavai:\n- **The `data/output/` folder doesn't exist and the code never creates it.** Fresh machine-la ovvoru run-um first row-ku munnadiye stop aagum.\n- **Crash, network error ellaam console-ku mattum dhaan pogudhu**, log-ku illa. Failed row-la reason (expired key, billing down, rate limit) record aagala.\n- **Billing sila lines reject panna invoice-um \"Synced\"-nu dhaan kaattudhu.** \"Created (confirmed after retry)\" create aagadha invoice-kum varalaam.\n- **Billing-la irundhu oru unreadable reject vandha, illa duplicate check-la network fail aanaa, whole run crash aagum.** Andha invoice input file-la irukkira varai ovvoru hour-um ippadi dhaan.\n- **Bot version-a engeyum kaattala.** Andha 2 \"fix\" commits-la oru comment line mattum dhaan add aagirukku, so andha fixes git history-la trace panna mudiyala.\n- **Report-la customer names copy aagudhu.** Adhanaala section 11-la \"file name and invoice numbers mattum anuppunga\" nu ezhudhiyirukken.\n- Meedhi: missing key/URL silent-a pogudhu, retries pointless-a nadakkudhu, runs overlap aagalaam, BOM issue, `nan` amount validation-a pass aagudhu, Task Scheduler access, tests illa.\n\nStopping and run history-ku Task Scheduler venum. Ops-ku adhu access irukka-nu confirm aagala, so andha part fix list-la potturukken (#13).\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 whose meaning the code doesn't make clear actually mean?",
|
|
"stderr": ""
|
|
} |