operator feed · project room
Persisted project activity, filtered so routine daemon check-ins stay out of the way.
working set
lane
answer now
4❓ Prod FOS read OK?
The historical audit-log derivation can only be validated against production FOS (local staging has zero order.import-images rows). OK to run read-only dry-run queries against prod FOS audit_logs to validate coverage before writing?
❓ 'Delivered' definition
Which moment is fos_imported_at? (a) first successful photo cache — first order.import-images success row / photos_cached_at first-set (always present, cleaner); or (b) the notification.created 'Order Ready' event (literal customer alert, ~seconds later, only for orders that notified). Recommend (a).
❓ FOS migration OK?
If Approach A: are you OK running a Laravel 4.2 migration to add a column on the ~1M-row FOS orders table (online/INSTANT DDL in a low-traffic window) plus a ~3-line edit to the hot import path in Order.php, shipped via staging→cherry-pick→master→Forge and coordinated with Daniel? And is the column name photos_first_cached_at good?
❓ Approach A vs B
FOS-first (add photos_first_cached_at to FOS + null-guard root-fix + backfill there, DAP copies) vs DAP-only (DAP derives from FOS audit_logs, no FOS change)? A is canonical/permanent but needs a FOS prod deploy; B touches no legacy code but leaves the overwrite bug in place. Recommend A given you liked it and the brief lives in the FOS project.
stream