Vegetable stall buying day - the three-stage checklist: before leaving, at the market, back at the stall - drop one thing and the day's profit is gone

You are a checklist designer for a vegetable stall's buying trips. I will tell you what my
stall regularly stocks and how I buy (I drive a cart to the wholesale market myself / the
market delivers to my stall). Generate a three-stage buying-day checklist.

The three stages (fixed - no fourth stage):
1. Before leaving - is everything packed
2. At the market - do the goods and the money agree
3. Back at the stall - has everything landed safely

Coverage required per stage:
- Before leaving: the item list from yesterday's buying notes checked for omissions (yes,
  including the bag of rice I promised to pick up for family); cart tires, tie-down rope,
  padding cloth, foam crates, ice packs; cash for buying packed separately from pocket
  money; phone fully charged (photos, QR payments and price entries all happen at market)
- At the market: watch the scale zeroed before weighing and the tare for crates and padding
  deducted; open full cases and look at the bottom layer - the damaged goods are always
  pressed underneath; check leafy greens for darkened cut ends; don't buy everything from
  one stall, split greens and roots across stalls on price; screenshot every payment or
  keep the receipt; photograph the whole load before leaving - "paid but never loaded"
  happens
- Back at the stall: count every item against the buying list; photograph transit damage
  (tomorrow's evidence with the vendor); shelve by overnight-decay speed - fast-decaying
  into foam crates on ice packs first, slow into stacked baskets; pin the buying list up,
  month-end reconciliation needs it

Format (for a groggy person at 4 a.m. - short beats complete):
- Each item = a checkbox + one line of action + (one line of why, naming how this trap
  actually traps)
- Actions may not contain empty verbs like "check" or "verify" - they must read
  "look at X's Y", something a hand and an eye can do right now
- Traps specific to categories I mention (say I buy tofu and bean sprouts - that's an
  insulation trap) must be woven in; do not invent traps for categories I never mentioned

Constraints:
- Maximum 8 items per stage; if over, cut the painless ones first
- Nothing that requires buying equipment (I will not purchase a cold chain for a checklist)
- No "stay safe" filler - that is not an action

Why it is written this way

Buying-day traps are all low-frequency, high-severity: losing a crate twice a year or paying for goods once and driving off without them wipes out the day. Memory cannot defend against this class of mistake - a 4 a.m. brain is unreliable, a routine is. The three stages map to the natural pauses of a buying trip, each completable as a unit before moving on; interrupt me halfway and I still know where to resume.

The ban on "check" and "verify" as verbs is the watershed between a usable and a decorative checklist. "Check the tires" cannot be executed; "look at whether the front and back tires are soft" can. Left alone, checklist-writing models produce precisely the former - correct, un actionable filler - so the prompt outlaws it and forces every line down to what is looked at, and where.

One line of why per item, rather than bare checkboxes, lets the checklist correct itself in use: where a trap never fires for my stall, seeing the why tells me I can strike that line; when I step in a trap the list missed, the same format shows me how to add one back. And the category-specific traps (tofu needs insulation, delicate herbs crush easily) are generated only from categories I name - the constraint exists because an unwatched model happily invents produce problems for goods you don't stock, padding the list with fiction.

Variables