CTC Appointment To Inbound Handoff Local UAT

• Evidence date: 2026-07-17T05:09:22Z
• Environment: Local Client 1; Client 2 negative-isolation check only
• Evidence class: disposable browser/API/DB fixture with cleanup

Verified Result

An authorized Email Approval UI session approved one run-owned unmatched CREATE with SUPPRESS_REPLY=true, reread the item, scheduled transload, same-tenant order/item mirror and selected-date Planning row, then deleted only captured IDs after a downstream-effect preflight. The item was APPROVED; the transload was SCHEDULED; the mirror order/item were Client-1 OPEN; Planner, Yard queue, Scale, lot and allocation counts were zero; Client 2 matching rows were zero; duplicate retry returned 400; no reply IDs existed; cleanup residue was zero.

The test reproduced and locally corrected a missing approval-draft JSON decoder and a raw-transload-state-to-OMS-item mapping defect. It changed no schema, route, permission, provider, queue policy or external-effect contract. The original field-fidelity conflict remains historical: this run observed carrier EMAIL, shipper -1, inferred container type and synthesized remark rather than exact reviewed values; the later reviewed-field UAT owns that correction.

This is automated Local evidence, not user/business acceptance or Production evidence. The procedure is Wiki appointment-email in Local and Production; the appointment process contract owns current recovery behavior.

---

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