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
3.3 KiB
JSON
32 lines
3.3 KiB
JSON
{
|
|
"case": "h-packaged-desktop/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,
|
|
"display scaling rule": true,
|
|
"version check": true,
|
|
"shortcut prerequisite": true,
|
|
"silent update failure flagged": true
|
|
},
|
|
"cost_usd": 1.4724382,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-full-xzlont2s\\project",
|
|
"reply": "`HANDOVER.md` ready, repo root-la irukku: `C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-full-xzlont2s\\project\\HANDOVER.md`. Code change edhuvum pannala, bot-um run pannala.\n\n| Item | Result |\n|---|---|\n| Sections | 13 |\n| Exceptions catalogued | 10 (E01\u2013E10) |\n| Failure classes | 10 covered, 2 not applicable (F8: re-run loop or watchdog illa; F10: queue or lock illa) |\n| Fix before handover | 15 items |\n| Checks | ella status-um doc-la irukku; file:line section 13-la mattum; PHI, client names, IPs, `.env` values edhuvum illa |\n\nOps-ku main points:\n- **Run nadula stop aanaa result Excel varaadhu.** Andha nerathula post aana entries log-la mattum dhaan irukkum (E07).\n- **Correctly post aana line-kum Result \"Missing\"-nu dhaan varum.** Note column-la \"Posted\" irukkum. Save click-ku apram LedgerPro-la save aachaa-nu bot check pannaadhu (E05).\n- **Pazhaya LedgerPro export file-a bot silent-a padikkalaam.** Appo re-run panna same entries rendu dhadava post aagum (E08).\n- **Version screen-la enga-yum theriyaadhu.**\n\nFix before handover-la top items:\n- Moonu \"fix\" commits-la oru comment line mattum dhaan add aagirukku. Launcher innum ella update error-aiyum maraikkudhu, spec file muzhusum comment, `assets/` images 16-byte placeholders.\n- Run nadula stop aanaa result file illa.\n- Save confirmation illa.\n- Pazhaya export file check illa.\n- Version check `!=` use pannudhu, adhanaala server-la pazhaya build irundhaa ella machine-um downgrade aagum.\n- Version display illa.\n- `.env` git-la commit aagirukku.\n- 2026-09-05 log-la oru party name irukku, adhu current code ezhudhuradhu illa. So deploy aana build indha source-la irundhu vandhadhu illa-nu thonudhu.\n\nNeenga munnaadiye sonna answers-a use pannen: escalation #rpa-support-ku, ops-ku screens, output folder, logs folder access mattum (database illa), theliva illaadha statuses-ku code-a vachu enga best reading. Indha bot database-ae use pannala, adhanaala DB point-ae doc-la varala.\n\nQUESTIONS: Escalation: who does ops call 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 can ops open - the app's screens, the output folder, the log folder, the database? | Unknowns: what do the statuses or exceptions mean whose meaning the code doesn't make clear?",
|
|
"stderr": ""
|
|
} |