integration-runbook-builderlisted

# Integration Runbook Builder Produces the runbook that takes an enterprise integration from kickoff to go-live: connection setup, document flows, test plan, cutover checklist, and failure escalation paths. One runbook per protocol, from a shared skeleton. ## Inputs - Protocol: EDI, cXML, REST API, SFTP, or email/CSV - Direction and documents: e.g., outbound PO (EDI 850), inbound PO acknowledgment (855), ASN (856), invoice (810) - Buyer platform and supplier system names - Environments available (sandbox, staging, production) ## Workflow 1. Read the protocol module in `references/` (one file per protocol: `edi.md`, `cxml.md`, `api.md`, `sftp.md`, `csv.md`). Each module carries the protocol's connection prerequisites, document mapping table skeleton, and known failure modes. 2. Run `scripts/scaffold_runbook.py --protocol <p>` to emit the skeleton with the correct sections. 3. Fill the mapping table: every field the buyer sends, the field it lands in, transformation rule, and the owner of each mapping decision. 4. Build the test plan as paired assertions: for each document flow, the triggering action, the expected artifact, and the exact location to verify it. 5. Append the cutover checklist and the escalation matrix (first responder, platform owner, supplier owner, and the evidence each needs). ## Output format Single markdown runbook: `## Connection`, `## Document Flows`, `## Field Mapping`, `## Test Plan`, `## Cutover`, `## Escalation`. ## Guardrails - Every test pl