Trust the receipt, then check the release.

This saved inspector reduces a JSON array of local event records. It expects five exact event types: order created, payment detected, escrow locked, seller accepted and buyer confirmed. The sample lists those types at indexes zero through four. With no unknown events or conflicting nonblank amount strings, that sample receives the local label release ready. The source explicitly records chain verified as false. No wallet, chain, escrow service or payment account is queried, and the label never releases actual funds. Required type count and event count are different. The source sample has five events. Append a second buyer confirmed record at the end and there are six events. The first occurrence of every required type is still at the expected index, so the source can still label it release ready while recording the final check as duplicate. These bars share eighty pixels per event: four hundred pixels for five events and four hundred eighty for six. A duplicate flag alone is not added to the source contradictions list. The order rule compares each required type first occurrence with its exact expected index, rather than merely checking relative order. Unknown records are retained in raw input and add a contradiction. Payment values are trimmed strings, so one twenty five and one twenty five point zero zero can disagree even though they could represent the same numeric amount. Empty payment amounts can display missing without creating an amount contradiction. Invalid JSON keeps the older active result and export. Reset clears the saved result and hides output but preserves trace text. Reload uses sample trace text while rendering any saved prior result. Export keeps every original event and extra field, checks, assumptions and limitations.