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.1 KiB
JSON
32 lines
3.1 KiB
JSON
{
|
|
"case": "h-packaged-desktop/screens",
|
|
"rep": 3,
|
|
"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,
|
|
"display scaling rule": true,
|
|
"version check": true,
|
|
"shortcut prerequisite": true,
|
|
"silent update failure flagged": true
|
|
},
|
|
"cost_usd": 0.8733934000000001,
|
|
"subagents": 0,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-screens-qhg1yk_0\\project",
|
|
"reply": "I wrote `HANDOVER.md` at the repo root. Unga answers use pannen: escalation = RPA Support queue ticket, ops can open only the report in the output folder, logs folder illa, database illa. Bot-a run pannala and code-um maathala. Code moonu files dhaan (app.py, launcher.py, spec), so scan-ku subagents use pannama naane direct-a padichen.\n\n| Item | Count |\n|---|---|\n| Sections | 13 (template order) |\n| Exceptions | 14 (E01\u2013E14) |\n| Failure classes | 10 covered, 2 not applicable (F8: auto-rerun/watchdog illa; F10: batch/queue/lock illa) |\n| Fix before handover | 18 items |\n\n**Dev team-ku mukkiyamaana fixes:**\n- Bot Save click pannina udane, LedgerPro confirm pannadha-nu check pannama, row-la `Posted` nu ezhudhudhu.\n- LedgerPro-oda export file fresh-a-nu check panradhilla. Pazhaya file use aana, already irukka entries thirumba post aagum, entha warning-um illama.\n- Report run-oda kadaisila mattum dhaan save aagudhu. Naduvula crash aana report kidaikkadhu, aana appo varaikkum post aana entries LedgerPro-la irukkum.\n- `logs` and `data\\output` folders-a code create pannadhu. `data\\output` repo-laiyum illa. Install appo create pannanum-nu doc-la sollirukken.\n- Version enga-yum display aagala. Launcher update error-um innum silent-a dhaan irukku.\n- Rendu \"fix\" commits (b235445, ba4c1aa) oru comment line mattum dhaan add pannirukku. So doc-la ella fixes-um \"unconfirmed\" nu mark pannirukken.\n- `.env` file git-la track aagudhu. Adhai naan open pannala.\n- Posted rows-oda Result column `Missing` nu dhaan kaattudhu. Ops confuse aagalaam, so Statuses section-la clear-a explain pannirukken.\n\n**Checks done:**\n- Ella status strings-um Statuses section-la irukku.\n- file:line refs section 13-la mattum dhaan.\n- Log-la irundha customer name and transaction references doc-la illa.\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": ""
|
|
} |