Deletes and restores the database to backup point 209608347, then runs the whole
pipeline on untouched production data with the corrected split: deactivate the
duplicate client per location, give every order its own payment record,
client-scope refunds, payouts and cash-drawer shifts, import live from Square,
and recompute ninety days at each stage.
production today 1,280 days off, 85.34% clean, $75,228.78
+ deduplication 1,087 days off, 87.55% clean, $63,764.92
+ refunded tips 800 days off, 90.84% clean, $60,619.21
+ service charges 108 days off, 98.76% clean, $1,995.36
1,172 client-days brought into balance, 0 knocked out. Neither arithmetic fix
altered a single figure on a day that already balanced. Excluding the ten
deactivated duplicates: 1,217 days and $69,995.61 down to 105 days and $852.38.
The split does what it was missing before: 189,167 payments re-keyed, 77,599
copied so each order owns one, and payments with two parent orders went 11,469
to 0 — holding at 0 after a live import across 48,362 orders. That closes the
component-cascade risk in remove-voided-orders.
Report rewritten for both audiences: what each fault meant for the books, then
the mechanism for engineers, with worked line-level examples, the verification
checks, the residual, and the open decisions. Includes the double-scoping bug
this work introduced and how measurement caught it.
23 tests, 55 assertions.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Bryce
011d515033