Record t1.20 task evidence

pm/tasks.org

@@ -1021,7 +1021,7 @@ refresh review state from the current normalized universe so missing or broken l
 
 ** notes
 - `review_products.py` now rebuilds its queue from the current normalized files and order files instead of trusting stale `purchases.csv` state.
-- Missing catalog rows and incomplete catalog rows now re-enter review explicitly as `orphaned_catalog_link` or `incomplete_catalog_link`, and excluded rows no longer inflate unresolved-not-in-review accounting.
+- Missing catalog rows and incomplete catalog rows now re-enter review explicitly as `orphaned_catalog_link` or `incomplete_catalog_link`, and excluded rows no longer inflate unresolved-not-in-review accounting.
 * [x] t1.20: add visit-level fields and outputs for spend analysis (2-4 commits)
 ensure purchases retains enough visit/order context to support spend-by-visit and store-level analysis
 
@@ -1042,11 +1042,13 @@ ensure purchases retains enough visit/order context to support spend-by-visit an
 3. documentation or task notes make clear that `purchases.csv` is the primary analysis artifact for both item-level and visit-level reporting
 - pm note: do not build dash/plotly here; this task is only about carrying the right data through
 
-** evidence
-- commit:
-- tests:
+** evidence
+- commit: `6940f16` `Document visit-level purchase analysis`
+- tests: `./venv/bin/python -m unittest tests.test_purchases`; `./venv/bin/python build_purchases.py`
 - datetime: 2026-03-24 08:29:13 EDT
 
+** notes
+- The needed visit fields were already flowing through `build_purchases.py`; this task locked them in with explicit tests and documentation instead of adding a new visit layer.
 - `data/review/purchases.csv` is now documented as the primary analysis artifact for both item-level and visit-level work.
 
 * [ ] t1.21: add lightweight charting/analysis surface on top of purchases.csv (2-4 commits)