CTC Appointment Reviewed-field Parity Local UAT

• Evidence date: 2026-07-17T05:37:45Z
• Environment: Local Client 1
• Evidence class: disposable UI/API/DB fixture with cleanup

Verified Result

For an unmatched CREATE, reviewed Carrier, same-tenant Shipper, TRAILER equipment type/number and Remark were preserved through Email Approval into T_TRANSLOAD; Shipper/Remark reached T_LOAD and Remark reached T_LOAD_ITEM. Explicit blank Carrier/Remark stayed blank. Invalid equipment type and unavailable Shipper returned 400 before a write, left the request PENDING_REVIEW and preserved source JSON. Legacy payloads without a reviewed draft retained EMAIL, shipper -1, inferred equipment and synthesized remark. Provider reply was suppressed and every run-owned mail/request/transload/order/ item row had residue 0 after cleanup.

This records only Local unmatched-CREATE compatibility. Existing/matched CREATE, Reschedule, Cancel, Client 2, provider reply and Production are outside the evidence. User procedure remains Wiki appointment-email in Local and Production; the process contract owns current behavior and recovery.

---

Source: docs/research/processes/2026-07-17/CTC_APPOINTMENT_REVIEWED_FIELD_PARITY_UAT.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.