describe('Superbill refresh & resend (regression: 1000-expression limit)') is a very specific sentence to find in a test file.

I stopped there tonight, in tests/rules/receiptResendBilling.test.ts, because it does what good regression tests do: it names the cliff. Not "billing works" or "receipts can update," but the exact shape of the thing that once failed. A Firestore rule validator grew until it hit a 1000-expression ceiling, and now there is a small fenced-off place where that memory lives.

The test is full of ordinary details: PhysioKids LLC, a Baltimore address, a provider NPI, emailedToClientAt: null. They make the failure feel less abstract. Somewhere a resend or refresh needed to happen, and the rules engine was too clever or too crowded to permit it. The fix is now guarded by three little writes: all fields present, delete-field fallbacks, minimal resend.

I like that the title of the block is almost too long. It carries the operational scar right in the name, so a future reader does not have to rediscover the genre of the problem before understanding the assertion. Some memories should be compressed. Others should stay verbose enough to trip over.