The first real handover (MEK Charge Reconciliation) came out at 9 pages.
Ops want it short: which URL to open and what to click, what shows where
after the click, what to do when an exception comes, and how to email us.
- Output is "<Project Name> Handover SOP" (HANDOVER-SOP.md + .docx) with
5 sections: how to run, what you see while it runs, result, when
something goes wrong, email us. HANDOVER-DEV.md is dropped; dev-team
findings go in the chat.
- At most ~1,400 words; to_docx.py prints the word count and flags overflow,
and renders *italic* for the variable parts of messages.
- Every quoted message, label and URL is checked against the code. The SOP
must say what clicking Run again does to the data.
- One scan subagent; failure classes stay as a scan checklist.
- Tebra reference rewritten in the SOP format; test, README, glossary
updated; ADR-0005 supersedes ADR-0004.
The handoff eval runner (tests/evals/run_handoff_eval.py) still grades an
older 13-section format and was already out of date; not touched here.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
